public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001024] STM32 USB driver and proposed USB API change Date: Sat, 16 Oct 2010 19:30:00 -0000 [thread overview] Message-ID: <20101016193001.2F4C72F7800E@mail.ecoscentric.com> (raw) In-Reply-To: <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 Chris Holgate <chris@zynaptic.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #994 is|0 |1 obsolete| | --- Comment #22 from Chris Holgate <chris@zynaptic.com> 2010-10-16 20:29:58 BST --- Created an attachment (id=1000) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1000) STM32 USB driver package fixing double buffering configuration bug. The bug which was causing alternate bulk transfer packets to fail was due to misconfiguration of the receive bulk transfer endpoint. My own class driver masked the bug because of the particular order in which it configured the endpoints. The updated USB driver package should fix this problem for the serial port class driver. A couple of points to note: 1) When using the serial port class driver, the variable length bulk transfer option must be deselected. This option may benefit from another descriptive name in order to avoid confusion. 2) To avoid buffer overflow conditions on large transfers, all calls to the serial port receive functions should specify a buffer which is a multiple of the bulk transfer message size for the bulk transfer endpoint (usually 64 bytes). -- 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.
next prev parent reply other threads:[~2010-10-16 19:30 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-25 20:36 [Bug 1001024] New: " bugzilla-daemon 2010-08-26 9:14 ` [Bug 1001024] " bugzilla-daemon 2010-08-26 11:00 ` bugzilla-daemon 2010-09-03 14:00 ` bugzilla-daemon 2010-09-13 19:31 ` bugzilla-daemon 2010-09-13 19:32 ` bugzilla-daemon 2010-09-13 19:51 ` bugzilla-daemon 2010-09-17 13:11 ` bugzilla-daemon 2010-09-17 18:03 ` bugzilla-daemon 2010-10-07 10:13 ` bugzilla-daemon 2010-10-07 19:23 ` bugzilla-daemon 2010-10-09 14:38 ` bugzilla-daemon 2010-10-15 13:51 ` bugzilla-daemon 2010-10-15 16:13 ` bugzilla-daemon 2010-10-15 17:07 ` bugzilla-daemon 2010-10-15 20:52 ` bugzilla-daemon 2010-10-16 7:41 ` bugzilla-daemon 2010-10-16 10:12 ` bugzilla-daemon 2010-10-16 10:55 ` bugzilla-daemon 2010-10-16 12:18 ` bugzilla-daemon 2010-10-16 13:53 ` bugzilla-daemon 2010-10-16 14:34 ` bugzilla-daemon 2010-10-16 19:30 ` bugzilla-daemon [this message] 2010-10-17 14:21 ` bugzilla-daemon 2010-10-17 15:06 ` bugzilla-daemon 2010-10-17 15:29 ` bugzilla-daemon 2010-10-17 18:08 ` bugzilla-daemon 2010-10-17 18:34 ` bugzilla-daemon 2010-10-18 9:36 ` bugzilla-daemon 2010-10-20 18:27 ` bugzilla-daemon 2010-10-21 8:57 ` bugzilla-daemon 2010-10-21 15:40 ` bugzilla-daemon 2010-10-21 18:32 ` bugzilla-daemon 2010-10-21 18:47 ` bugzilla-daemon 2010-10-21 21:20 ` bugzilla-daemon 2010-10-25 8:48 ` bugzilla-daemon 2010-10-26 10:50 ` bugzilla-daemon 2010-10-26 19:15 ` bugzilla-daemon 2010-10-27 10:25 ` bugzilla-daemon 2010-10-27 13:04 ` bugzilla-daemon 2010-08-25 20:36 [Bug 1001024] New: " bugzilla-daemon 2010-08-26 9:14 ` [Bug 1001024] " bugzilla-daemon 2010-08-26 11:00 ` bugzilla-daemon 2010-09-03 14:00 ` bugzilla-daemon 2010-09-13 19:31 ` bugzilla-daemon 2010-09-13 19:32 ` bugzilla-daemon 2010-09-13 19:51 ` bugzilla-daemon 2010-09-17 13:11 ` bugzilla-daemon 2010-09-17 18:03 ` bugzilla-daemon 2010-10-07 10:13 ` bugzilla-daemon 2010-10-07 19:23 ` bugzilla-daemon 2010-10-09 14:38 ` bugzilla-daemon 2010-10-15 13:51 ` bugzilla-daemon
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=20101016193001.2F4C72F7800E@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /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: linkBe 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).