Hi John, Calling USB endpoint with their devtab entry name ( .e.g. /dev/usbsX ) was meant to be more user friendly but can be easily changed. I guess that is the meaning of the new USB API as well.
Note that the patch is missing a file for some reason ( usbs_msd_scsi.h ). I can generate a new patch, shall I remove the dependency towards the endpoint devtab entry? Regards, Christophe -----Original Message----- From: John Dallaway [mailto:[email protected]] Sent: 18. oktober 2010 14:54 To: Christophe Coutand Cc: [email protected]; Chris Holgate; Ilija Stanislevik Subject: Re: USB mass storage package (slave side). Hi Christophe Christophe Coutand wrote: > There has been some request for a USB mass storage package (slave side). > This was tested on AT91 architecture with the AT91 eCos USB device > driver. Some patches are required to the AT91 USB device driver for this > package to work properly. If anyone has the possibility to test it with > other architecture it would be most welcome. I've been working with Chris Holgate (and Ilija Stanislevik) to get his STM32 USB slave device driver ready for check-in: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001024 Once this is checked-in, I plan to look at your MSD function driver. One immediate issue is that the STM32 USB slave device driver uses dynamic I/O endpoint configuration and does not provide the endpoint devtab entries which are required by your driver. Looking at your code, it seems that the endpoint devtab entries are only used to look up the endpoint structures within usbs_msd_init(): tab = usbs_msd_lookup( tx_ep_dev_name ); msd->tx_ep = (usbs_tx_endpoint *) tab->priv; tab = usbs_msd_lookup( rx_ep_dev_name ); msd->rx_ep = (usbs_rx_endpoint *) tab->priv; So it seems it should be easy to eliminate the requirement for these devtab entries. Have I understood correctly? John Dallaway eCos maintainer
