This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001024] STM32 USB driver and proposed USB API change
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Mon, 18 Oct 2010 10:35:53 +0100
- Subject: [Bug 1001024] STM32 USB driver and proposed USB API change
- Auto-submitted: auto-generated
- References: <bug-1001024-13@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001024
--- Comment #28 from John Dallaway <john@dallaway.org.uk> 2010-10-18 10:35:47 BST ---
Created an attachment (id=1002)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1002)
usbs_serial-101018.patch
I have USB serial working on STM32 now. This provisional patch adds support for
the dynamic configuration of I/O endpoint structures to the USB serial function
driver in line with Chris Holgate's USB API change proposal.
I'm concerned that usbs_serial_start() will now block until a connection has
been established and endpoints have been configured. How will this affect the
implementation multiple function devices over a single USB port where multiple
usbs_*_start() functions may need to be called? I'm thinking that it should be
possible to present both a mass storage device and a serial device (for
example) over a single physical interface. While it's desirable to minimise
code changes, we should not restrict the capabilities of the USB slave support
in the process.
Chris, I would value your comments on the above.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.