This is the mail archive of the
ecos-patches@sourceware.org
mailing list for the eCos project.
Re: USB serial package
- From: Frank Pagliughi <fpagliughi at mindspring dot com>
- To: Andrew Lunn <andrew at lunn dot ch>
- Cc: ecos-patches at sourceware dot org
- Date: Wed, 18 Jun 2008 16:00:20 -0400
- Subject: Re: USB serial package
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=t6J1Gqa+sBZs9hq8U29AsI1DY5dTkphUiU+rTX3JvT68O4feOE0xkiDAcAGTqhku; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
- References: <48489207.1090301@mindspring.com> <20080615105619.GA4883@lunn.ch> <48568D26.2050604@mindspring.com> <20080618192852.GC6399@lunn.ch>
I also couldn't figure out any way to add class-specific descriptors
(which would make the ACM configuration usable with a Linux host). Any
help here would be appreciated.
Sorry, no idea. I would have to take a look at my USB book to first
figure out the encoding.
I actually hadn't seen class-specific descriptors before doing this
package. Apparently you just jam them into the response to the request
for the configuration descriptor along with the interface and endpoint
descriptors, etc. Most of the USB device libraries I've used (or
written) just place the entire response into contiguous memory in ROM or
RAM without worrying too much about the contents.
The eCos library uses the 'usbs_enumeration_data' structure which calls
out the different descriptor types, but makes no provision for class
descriptors that I could find. Maybe we could add something to the
structure? Like a catch-all void/byte pointer and length? Could it be
done without breaking the existing code?
I ask because I have the start of several other classes that could be
submitted (Printer, Mass Storage, & HID), and would undoubtedly be
modeled after this one.
Such class drivers would be great. However do you need to get the
class specific descriptors working first?
Definitely not for printer classes; I already have that working. I
don't think for HID classes, either. I don't remember for mass storage
devices.