I'm trying to understand ether.c in order to better integrate pxa27x_udc with it. My goal is to make MCCI, Belcarra, and Jungo Windows CDC Subset/SAFE/MDLM drivers talk with a Linux PXA270 embedded device with TCP/IP.
Reading thru several versions of ether.c from the Linux kernel (as early as 2.6.10 and as late ast 2.6.21.5) tree and from what Grahame Jordan did (a version enable a PXA255 do MDLM/SAFE) I see a consistent weirdness: The arrays hs_eth_function and fs_eth_function seemingly do not get pointed at by ether.c. In a few kernel versions I even searched all routines in the /drivers/gadget/drivers directory and could not find them used. These are static arrays and so I would expect them to get referenced in ether.c. Not so. So why are these arrays in ether.c? Also, the usb_endpoint_descriptors that each array has pointers to do not get referenced anywhere else. So there's this mystery: How are all these endpoints getting used? Maybe I'm being dumb and missing something obvious... Randall Parker Vetronix Santa Barbara CA, USA 805-966-2000 x3141 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
