Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-26 Thread Ivo van Doorn
On Friday 26 October 2007, Roland Dreier wrote: > > The function that is returning ENODEV is the driver probe function. > According > > to Documentation/DocBook/writing_usb_driver/ch03.html when that function > is > > called > > > > "The driver now needs to verify that this device is act

Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-26 Thread Roland Dreier
> The function that is returning ENODEV is the driver probe function. > According > to Documentation/DocBook/writing_usb_driver/ch03.html when that function is > called > > "The driver now needs to verify that this device is actually one that it can > accept. If so, it returns 0. If no

Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-26 Thread Adam Baker
On Friday 26 October 2007 20:10, Roland Dreier wrote: >  > Well it could be something quite simple, in the module loader it is > looping > through all modules to look for a device with the correct USB/PCI > ID. > Currently, after the first occurence it loads the module and doesn't > continue, > it

Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-26 Thread Roland Dreier
> Well it could be something quite simple, in the module loader it is looping > through all modules to look for a device with the correct USB/PCI ID. > Currently, after the first occurence it loads the module and doesn't > continue, > it should perhaps be relatively easy that it checks if the

Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-26 Thread Ivo van Doorn
On Friday 26 October 2007, Parag Warudkar wrote: > > Hi Ivo > > On Thu, 25 Oct 2007, Ivo van Doorn wrote: > > > I awknowledge the problem, but the solution cannot be found in the USB ID's > > listed in the driver. The bug is the manufacturer who changed chipset while > > keeping the USB ID the s

Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-25 Thread Parag Warudkar
Hi Ivo On Thu, 25 Oct 2007, Ivo van Doorn wrote: I awknowledge the problem, but the solution cannot be found in the USB ID's listed in the driver. The bug is the manufacturer who changed chipset while keeping the USB ID the same. There are 2 possible ways around this: hacking the module loader

Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-25 Thread Parag Warudkar
On Thu, 25 Oct 2007, Adam Baker wrote: Unfortunately Belkin have sold both RT73 and RT2500 devices with that USB ID. You don't say what distro you are runing or what version of RT2x00 it ships with but last time I checked with the git version of rt2x00 it tried to load both drivers but the rt

Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-25 Thread Ivo van Doorn
Hi, > I have a Belkin USB Wireless adapter with ID 050d:705a. > Both rt2500usb.c and rt73usb.c claim that they can drive the device with > this ID. > > When using the distro kernel as well as custom 2.4.24-rc1 both rt73usb and > rt2500usb get loaded and fight for the register writes and fail. r

Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}

2007-10-25 Thread Adam Baker
On Thursday 25 October 2007 00:22, Parag Warudkar wrote: > I have a Belkin USB Wireless adapter with ID 050d:705a. > Both rt2500usb.c and rt73usb.c claim that they can drive the device with > this ID. > > When using the distro kernel as well as custom 2.4.24-rc1 both rt73usb and > rt2500usb get loa