From: Andrew Lunn <andrew@lunn.ch>
To: Frank Pagliughi <fpagliughi@mindspring.com>
Cc: eCos Devel <ecos-devel@ecos.sourceware.org>
Subject: Re: "usbhid-ups" programing problem...
Date: Thu, 01 May 2008 15:52:00 -0000 [thread overview]
Message-ID: <20080501155138.GA14773@lunn.ch> (raw)
In-Reply-To: <4819DEFF.2040007@mindspring.com>
On Thu, May 01, 2008 at 11:17:19AM -0400, Frank Pagliughi wrote:
> Andrew Lunn wrote:
>> eCos is rather lacking in USB examples. Nobody contributes back there
>> USB class drivers.
>>
>>
> I'm actually going to be using eCos again pretty soon, and have been
> digging through some of my old stuff, including a nearly finished driver
> for the Philips/NXP ISP1181 chip, which I promised to submit two years
> ago.
It is probably worth looking at the assignments stuff. You will need
an FSF assignment before we can accept these contributions.
> Maybe I can start with a few simple examples, like usb serial or a
> usb printer. Where would they go?
A CDC serial driver would be good. I would put it in
packages/io/usb/serial/slave/
> For that matter, the usb subsystem could use a bit of an upgrade to make
> drivers easier to write.
Others have said that as well. But it needs somebody to actually do
it. A lot depends on the complexity of the driver. I recently wrote a
simple driver and a Linux kernel counterpart without too much effort.
Andrew
next prev parent reply other threads:[~2008-05-01 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 12:16 Michelle Konzack
2008-05-01 10:04 ` Andrew Lunn
2008-05-01 15:38 ` Frank Pagliughi
2008-05-09 12:36 ` Michelle Konzack
[not found] ` <4819DEFF.2040007@mindspring.com>
2008-05-01 15:52 ` Andrew Lunn [this message]
2008-05-01 15:57 ` Gary Thomas
2008-05-01 16:01 ` Andrew Lunn
2008-05-01 17:22 ` Frank Pagliughi
2008-05-01 18:24 ` 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=20080501155138.GA14773@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-devel@ecos.sourceware.org \
--cc=fpagliughi@mindspring.com \
/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).