public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Christophe Coutand <ccoutand@stmi.com>
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 12:54:00 -0000	[thread overview]
Message-ID: <4CBC437F.8080708@dallaway.org.uk> (raw)
In-Reply-To: <D6050C555CC56940A7AF32652283027602FFE45F@mail2.STMIRV01.COM>

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

  reply	other threads:[~2010-10-18 12:54 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 [this message]
2010-10-18 13:50   ` Christophe Coutand
2010-10-18 14:08     ` John Dallaway
2010-10-18 14:13       ` Christophe Coutand

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=4CBC437F.8080708@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ccoutand@stmi.com \
    --cc=chris@zynaptic.com \
    --cc=ecos-patches@ecos.sourceware.org \
    --cc=ilijas@siva.com.mk \
    /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).