This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: USB MSD stack
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Doyle, Patrick" <Patrick_Doyle at dtccom dot com>
- Cc: "'ecos-discuss at ecos dot sourceware dot org'" <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 4 May 2006 16:00:32 +0200
- Subject: Re: [ECOS] USB MSD stack
- References: <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