This is the mail archive of the
ecos-patches@sourceware.org
mailing list for the eCos project.
Re: USB mass storage package (slave side).
- From: John Dallaway <john at dallaway dot org dot uk>
- To: Christophe Coutand <ccoutand at stmi dot com>
- Cc: ecos-patches at ecos dot sourceware dot org, Chris Holgate <chris at zynaptic dot com>, Ilija Stanislevik <ilijas at siva dot com dot mk>
- Date: Mon, 18 Oct 2010 15:07:46 +0100
- Subject: Re: USB mass storage package (slave side).
- References: <D6050C555CC56940A7AF32652283027602FFE45F@mail2.STMIRV01.COM> <4CBC437F.8080708@dallaway.org.uk> <D6050C555CC56940A7AF32652283027603538FBA@mail2.STMIRV01.COM>
Hi Christophe
Christophe Coutand wrote:
> 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.
The new API is intended to provide more flexibility for modern USB slave
hardware (dynamic endpoint configuration).
> 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?
If you have time to remove the dependency on endpoint devtab entries,
that would be great. Also, could you raise a new bugzilla report at
http://bugs.ecos.sourceware.org for your contribution? It's much easier
to track patches and the discussion about them in Bugzilla.
To be clear, the new USB API presented at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001024
is not yet formalised, but any future changes required to use the new
API should be independent of work to remove the dependency on endpoint
devtab entries within your MSD function driver package.
Thank you
John Dallaway
eCos maintainer