Exactly. As a compromise, how about moving the code for those ugly
if-statements into a separate subroutine inside the autoconf.c file
(renamed from epautoconf.c)? That routine could return the "controller
type" number (0 if the controller isn't recognized), and the gadget driver could call it when setting bcdDevice.
I didn't notice a followup to my post of yesterday talking about needing better bcdDevice conventions. The current one only allocates 9 numbers for controller numbers ... almost kaput.
There are other parts of autoconfig that don't relate to endpoints, and the "epautoconf.h" you saw should vanish ... the two declarations belong in <linux/usb_gadget.h>, nothing else is endpoint-specific.
So unless I hear a better naming suggestion, I'll put the gadget_is_X() macros into "gadget_chips.h" file and use the current scheme. That can then be improved on, by contributing patches.
- Dave
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
