From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9259 invoked by alias); 4 May 2006 14:00:38 -0000 Received: (qmail 9245 invoked by uid 22791); 4 May 2006 14:00:37 -0000 X-Spam-Check-By: sourceware.org Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 04 May 2006 14:00:35 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1FbeNc-0005bg-00; Thu, 04 May 2006 16:00:32 +0200 Date: Thu, 04 May 2006 14:00:00 -0000 To: "Doyle, Patrick" Cc: "'ecos-discuss@ecos.sourceware.org'" Message-ID: <20060504140032.GK3797@lunn.ch> Mail-Followup-To: "Doyle, Patrick" , "'ecos-discuss@ecos.sourceware.org'" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11+cvs20060403 From: Andrew Lunn X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] USB MSD stack X-SW-Source: 2006-05/txt/msg00024.txt.bz2 > 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