From: Andrew Lunn <andrew@lunn.ch>
To: "Doyle, Patrick" <Patrick_Doyle@dtccom.com>
Cc: "'ecos-discuss@ecos.sourceware.org'" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] USB MSD stack
Date: Thu, 04 May 2006 14:00:00 -0000 [thread overview]
Message-ID: <20060504140032.GK3797@lunn.ch> (raw)
In-Reply-To: <F7F756E5ED50F345959AE893AD2F15660A21F4@dtcsrvr09.dtccom.com>
> So, at that level, I wouldn't have FATFS running locally on eCos (not when
> I'm allowing the host to access the local storage), I will interact directly
> at the block level with the storage device (RAM, flash, SD-Card, etc...).
O.K. That is a simple solution to avoid concurency problems.
> As I look at this, I am becoming more concerned about the HID requirements
> for our product because a) I still don't know what I don't know about it; b)
> I've read that it requires "interrupt" transfers; c) I've read that the eCos
> stack in the CVS tree doesn't include "interrupt" transfers; d) I know more
> about SCSI than I do about HID; and e) I don't know very much at all about
> SCSI :-)
You might also want to add to that list f) find out if USB allows a
device to be both MSD and HID at the same time. g) Find out if eCos
allows a device to be both MSD and HID at the same time. h) If not,
find out if eCos allows the device to dynamically change between HID
and MSD.
> All of that being said, I still need to finish the low level driver... off
> to coding land!
What device is this? It seems USB has become popular recently with
eCos. I know of three other device drivers in development at the
moment.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-05-04 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 13:44 Doyle, Patrick
2006-05-04 14:00 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-04 14:47 Doyle, Patrick
2006-05-04 23:12 ` Frank Pagliughi
2006-05-04 14:25 Doyle, Patrick
2006-05-04 14:38 ` Andrew Lunn
2006-05-04 14:07 Doyle, Patrick
2006-05-04 14:18 ` Andrew Lunn
2006-05-04 13:46 Doyle, Patrick
2006-05-04 13:03 Doyle, Patrick
2006-05-04 13:11 ` Stefan Sommerfeld
2006-05-04 13:26 ` Andrew Lunn
2006-05-04 13:36 ` Andrew Lunn
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=20060504140032.GK3797@lunn.ch \
--to=andrew@lunn.ch \
--cc=Patrick_Doyle@dtccom.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).