From: Andrew Lunn <andrew@lunn.ch>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Devel <ecos-devel@ecos.sourceware.org>
Subject: Re: "usbhid-ups" programing problem...
Date: Thu, 01 May 2008 16:01:00 -0000 [thread overview]
Message-ID: <20080501160047.GB14773@lunn.ch> (raw)
In-Reply-To: <4819E83E.3050701@mlbassoc.com>
>> 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.
>
> Perhaps you could share it as an example?
Unfortunately it was done with my employee hat on, not my hobby hat.
Getting the O.K. to distribute it will not be easy...
Andrew
next prev parent reply other threads:[~2008-05-01 16:01 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
2008-05-01 15:57 ` Gary Thomas
2008-05-01 16:01 ` Andrew Lunn [this message]
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=20080501160047.GB14773@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-devel@ecos.sourceware.org \
--cc=gary@mlbassoc.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).