Hi all,
I'm porting the atmel 2.1.2.2 wireless device driver [http://atmelwlandriver.sourceforge.net] to the 2.5.x series kernels, and have run into a block. Currently, in the function VnetUsbReset, from vnet_kernel.c, the kernel function usb_driver_release_interface is called. The atmel driver gets the second argument for this function, struct usb_interface, from usb_config_descriptor->interface[0].
That was always a bad solution. As a rule:
[1] If you're just using one interface, you should be
(a) return non-null when that interface is probe()d
(b) cleaning up in disconnect(), letting usbcore release(). [2] If you're using more than one interface, treat the first as
in [1] above, and for the others:
(a) usb_claim_interface() as you probe() the first one,
(b) usb_release_interface() as you disconnect() it.Or perhaps for 2b, just make sure your disconnect() routine will handle that correctly.
- Dave
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
