From: "Christophe Coutand" <ccoutand@stmi.com>
To: "John Dallaway" <john@dallaway.org.uk>
Cc: <ecos-patches@ecos.sourceware.org>,
"Chris Holgate" <chris@zynaptic.com>,
"Ilija Stanislevik" <ilijas@siva.com.mk>
Subject: RE: USB mass storage package (slave side).
Date: Mon, 18 Oct 2010 14:13:00 -0000 [thread overview]
Message-ID: <D6050C555CC56940A7AF32652283027603538FC6@mail2.STMIRV01.COM> (raw)
In-Reply-To: <4CBC54B2.3020906@dallaway.org.uk>
Hi John,
Bugzilla report was previously created:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000987
I will upload an updated patch.
Christophe
-----Original Message-----
From: John Dallaway [mailto:john@dallaway.org.uk]
Sent: 18. oktober 2010 16:08
To: Christophe Coutand
Cc: ecos-patches@ecos.sourceware.org; Chris Holgate; Ilija Stanislevik
Subject: Re: USB mass storage package (slave side).
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
prev parent reply other threads:[~2010-10-18 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 18:59 Christophe Coutand
2010-10-18 12:54 ` John Dallaway
2010-10-18 13:50 ` Christophe Coutand
2010-10-18 14:08 ` John Dallaway
2010-10-18 14:13 ` Christophe Coutand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D6050C555CC56940A7AF32652283027603538FC6@mail2.STMIRV01.COM \
--to=ccoutand@stmi.com \
--cc=chris@zynaptic.com \
--cc=ecos-patches@ecos.sourceware.org \
--cc=ilijas@siva.com.mk \
--cc=john@dallaway.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).