Hi, I had a look on some extracts of your book I think I will buy it because it seems to correspond to what I am looking for. Thanks for the link! However, it has been done on a 2.6.34 kernel, but I am at the moment working on a uClinux 2.6.19. The registration function platform_driver_probe() seems to be what I need, but unfortunately don't exist on my kernel version.. I have seen in UDC drivers (in /drivers/usb/gadget) that platform_driver_register() is used instead of platform_driver_probe(). What is the equivalent for the kernel 2.6.19? Because the USB controller (hardware) embedded in my final system will be unique, so I don't need to probe at all. My driver must be registrered at boot time, and my hardware controller configured once. Thanks in advance for your help. 2013/1/15 Rajaram R <rajaram.officemail@xxxxxxxxx>: > Hi > > Did you had a chance to look at my book > > http://www.amazon.com/Bootstrap-Yourself-Linux-USB-Stack-Validate/dp/1435457862 > > I hope that helps.. > > Rajaram > > On Tue, Jan 15, 2013 at 8:48 PM, stl <st.lambert02@xxxxxxxxx> wrote: >> >> Hello all, >> I need some clarifications concerning the terms used in the linux usb >> documentation >> for usb driver: >> >> Firstly, what is the difference between: >> - device driver >> - chipset driver >> - interface driver >> - gadget driver >> ? >> >> If I well understood, device driver is the same that gadget driver. >> >> Secondly, I am writing a "device-side" usb driver for uClinux for our >> own specific >> USB controller. >> >> Should I use usb_register() or platform_driver_register() to register >> the driver during >> boot? >> What is the difference between these two functions? >> >> Thanks in advance for your help. >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-usb" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
