From: Chris Holgate <chris@zynaptic.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>, ecos-devel@sourceware.org
Subject: STM32 USB support
Date: Tue, 19 May 2009 11:47:00 -0000 [thread overview]
Message-ID: <4A129C34.9090606@zynaptic.com> (raw)
In-Reply-To: <4A11E5DF.2000403@intefo.ch>
Simon Kallweit wrote:
> Chris Holgate schrieb:
>>
>> It's stable in my application using my own Linux kernel driver (several
>> million bulk and interrupt transactions and counting!).
>>
> That sound's pretty stable to me :)
OK - I've now done a bit of tidying up which I hope won't have broken
it! The latest version of the package is here:
http://www.zynaptic.com/ecos/packages/stm32-usb-20090519.epk
There are a couple of minor TODO's which I need to revisit before a
proper release, but nothing significant.
>> However, I've not had much luck getting it working with the standard
>> eCos test framework - although I now suspect thats a Linux usbfs issue
>> rather than my driver. I also need to sort out some proper
>> documentation!
>
> Well, I could do some testing too and see where I get.
That would be very helpful, although I think that the standard host-side
tests have only ever been run on a pretty old version of Linux. I'd
have more confidence in testing against some standard drivers like a
virtual serial port or a 'memory stick' device.
>> There is a significant difference from the other USB drivers which I
>> should probably flag up (and document). The endpoint configuration is
>> generated dynamically from the USB descriptors. This gives a lot of
>> flexibility and potentially allows support for multiple configurations
>> (untested!). However, the downside is that I had to leave out devtab
>> support since the devtab entries need to be set statically.
>>
> Don't you think it's possible to have both options? I haven't looked at
> the USB subsystem or any drivers, but I think a public driver should
> behave as the subsystem intends. Maybe the subsystem could be extended
> for more dynamic usage though.
The official docs say "To support this the device driver can provide a
devtab entry for each endpoint". I took that to mean that devtab
support was optional - and the dynamic endpoint configuration is a much
more useful feature IMHO.
Previously supported hardware has had fixed endpoint configurations
which makes the static devtab entries easy to implement. However, with
dynamic endpoint configuration, the low-level driver doesn't know
a-priori what endpoints to generate devtab entries for - and nor should it!
Copied to the list, since I'm sure there are other people who would like
to comment...
Chris.
next parent reply other threads:[~2009-05-19 11:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A11CAAA.8040900@intefo.ch>
[not found] ` <4A11D861.8090206@zynaptic.com>
[not found] ` <4A11E5DF.2000403@intefo.ch>
2009-05-19 11:47 ` Chris Holgate [this message]
2009-05-19 12:00 ` Andrew Lunn
2009-05-19 15:17 ` Simon Kallweit
2009-05-19 16:28 ` Chris Holgate
2009-05-20 8:20 ` Simon Kallweit
2009-05-19 15:44 ` Chris Holgate
2009-05-20 3:09 ` Frank Pagliughi
2009-05-20 10:19 ` Chris Holgate
2009-05-20 14:54 ` Frank Pagliughi
2009-05-20 16:06 ` Chris Holgate
2009-05-20 22:31 ` Frank Pagliughi
2009-05-19 13:33 ` John Dallaway
2009-05-20 21:22 ` Chris Holgate
2009-05-21 7:27 ` John Dallaway
2009-05-31 15:01 ` Chris Holgate
2009-05-31 15:46 ` John Dallaway
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=4A129C34.9090606@zynaptic.com \
--to=chris@zynaptic.com \
--cc=ecos-devel@sourceware.org \
--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).