From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11668 invoked by alias); 4 May 2006 23:12:33 -0000 Received: (qmail 11658 invoked by uid 22791); 4 May 2006 23:12:33 -0000 X-Spam-Check-By: sourceware.org Received: from smtpauth08.mail.atl.earthlink.net (HELO smtpauth08.mail.atl.earthlink.net) (209.86.89.68) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 04 May 2006 23:12:30 +0000 Received: from user-112umh6.biz.mindspring.com ([66.47.90.38] helo=[127.0.0.1]) by smtpauth08.mail.atl.earthlink.net with asmtp (Exim 4.34) id 1Fbmzi-0004XW-9z; Thu, 04 May 2006 19:12:26 -0400 Message-ID: <445A8A7F.2080306@mindspring.com> Date: Thu, 04 May 2006 23:12:00 -0000 From: Frank Pagliughi User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: "Doyle, Patrick" CC: 'Andrew Lunn' , "'ecos-discuss@ecos.sourceware.org'" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 4d82f965df0f6dd9e3f977c6d1ea408f0a9da525759e2654e2f28c0f0e912bfecfd433eb29febd1c29ca3e42375bd564350badd9bab72f9c350badd9bab72f9c 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/msg00035.txt.bz2 Doyle, Patrick wrote: >>From: Andrew Lunn [mailto:andrew@lunn.ch] >> >>What you might be able to do is not set a device class. You then need >>to tell M$ windows that when it sees vendor XYZ it should load both >>the HID driver and the MSD driver. The HID driver will grab the >>interupt end point and the MSD driver will grab the bulk in and out >>endpoints. A lot will depend on what level M$ does its resource >>allocations. If it does the allocation at interface level, it will not >>work, the first loaded driver will win. If it does it at endpoint >>level you have a chance. Handling control transfers is going to be >>interesting. >> >>Or you could just write a HID and MSD driver for M$. Well, you don't >>need full drivers, just an intermediate driver which has two >>interfaces on top and one on the bottom. Does M$ have USB intermediate >>drivers? I know they exist for the networking stack.... >> >> Andrew >> >> > >Hmmm... we are hoping to avoid writing any host drivers (or even .ini files, >if possible). But we may learn that that is not possible. > >Thanks again for your thoughts... > >--wpd > > > If you can get away without writing a Windows driver, I reccomend it. It's at least one less variable when debugging. You may need or want to write your own INF file if you've got multiple interfaces. On most device chips I've seen, interrupt transfers work in a similar manner to bulk transfers. It's up to the host to guarantee bandwidth to the interrupt transfers and deal with the complexities. So it should be no problem doing the device side of the HID in eCos. For USB questions, the discussion board on usb.org is excelent. The person who wrote your USB book may be the one to answer your question. The discussion board is at: http://www.usb.org/phpbb/ Frank -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss