From: Frank Pagliughi <fpagliughi@mindspring.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>,
Andrew Lunn <andrew@lunn.ch>
Cc: Chris Holgate <chris@zynaptic.com>,
Gaurang <gtamakuwala@intriguetechsolutions.com>,
ecos-devel@sourceware.org
Subject: Re: USB testing - any more class drivers out there?
Date: Tue, 26 May 2009 19:04:00 -0000 [thread overview]
Message-ID: <4A1C3D31.1070704@mindspring.com> (raw)
In-Reply-To: <4A1BB74A.2080108@intefo.ch>
Simon Kallweit wrote:
> Chris Holgate wrote:
>> I don't know is Simon has had any luck getting it working, but if not
>> I'll try and put together a patch.
>
> Sorry, I didn't get it working. But this is more about lack of time
> and priority than anything else. After you have started the discussion
> about how to improve the USB slave framework I thought it may be good
> to wait until we have a better picture and eventually change the USB
> slave API before we adapt the serial driver. But I guess I'm not the
> only one short on time :)
>
>> As far as HID support is concerned, eCos is currently a bit lacking in
>> USB class driver implementations. You'll need to dig into the
>> documentation and roll your own. I'm sure that any standard USB class
>> drivers you do develop would be more than welcome as contributions!
>
> Agreed! If time permits I would like to dig into a standard compliant
> ethernet over USB driver.
>
> Simon
>
I had submit a USB printer package last summer which doesn't seem to
have made it into CVS. I'm pretty sure it was working.
Andrew: Do you remember why this wasn't accepted?
I also started a mass storage driver, and have it near the top of my
list for when I get back working on eCos this summer.
I personally never found much use for HID's - unless you're actually
making a mouse, keyboard, or joystick. I know that most introductory USB
articles and tutorials show how to implement HID's, but it seems such a
shame, because others classes, like the serial one, are actually simpler
and much more useful. So, I probably won't look to implement a HID
driver myself.
Nor do I think I would start on ethernet over USB myself.
Frank Pagliughi
next prev parent reply other threads:[~2009-05-26 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DD9BA4A07313441D93DE1AF867FCE3BB@Intrigue63>
2009-05-26 9:15 ` Chris Holgate
2009-05-26 9:32 ` Simon Kallweit
2009-05-26 19:04 ` Frank Pagliughi [this message]
2009-05-26 19:27 ` Eval board for testing STM32 USB Frank Pagliughi
2009-05-26 19:35 ` Simon Kallweit
2009-05-26 21:06 ` Chris Holgate
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=4A1C3D31.1070704@mindspring.com \
--to=fpagliughi@mindspring.com \
--cc=andrew@lunn.ch \
--cc=chris@zynaptic.com \
--cc=ecos-devel@sourceware.org \
--cc=gtamakuwala@intriguetechsolutions.com \
--cc=simon.kallweit@intefo.ch \
/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).