On Thu, Oct 21, 2004 at 09:51:14AM +0100, Mikolaj Zuberek wrote:
> >On Wed, Oct 20, 2004 at 09:20:51AM +0100, Mikolaj Zuberek wrote:
> >>>You, as a developer of usb-skeleton driver, would probably be in the
> >>>best position to shed some light on my problem.
> >
> >And you, as modifier of the usb
On Wed, Oct 20, 2004 at 09:20:51AM +0100, Mikolaj Zuberek wrote:
Hi Greg,
You, as a developer of usb-skeleton driver, would probably be in the
best position to shed some light on my problem.
And you, as modifier of the usb-skeleton driver, and possessor of the
device in question, are in t
On Wed, Oct 20, 2004 at 09:20:51AM +0100, Mikolaj Zuberek wrote:
> Hi Greg,
>
> You, as a developer of usb-skeleton driver, would probably be in the
> best position to shed some light on my problem.
And you, as modifier of the usb-skeleton driver, and possessor of the
device in question, are in
Mikolaj Zuberek wrote:
| best position to shed some light on my problem. Any ideas why the
| usb-skeleton's probe function is called for some devices and not for
| others even if I have correct Vendor/Product ids hardcoded?
Is there another loaded driver that claims the device? If your hotplug
syst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mikolaj Zuberek wrote:
| best position to shed some light on my problem. Any ideas why the
| usb-skeleton's probe function is called for some devices and not for
| others even if I have correct Vendor/Product ids hardcoded?
Is there another loaded drive
Hi Greg,
You, as a developer of usb-skeleton driver, would probably be in the
best position to shed some light on my problem. Any ideas why the
usb-skeleton's probe function is called for some devices and not for
others even if I have correct Vendor/Product ids hardcoded?
Thanks in advance for
