From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001550] STM32 F2 and STM3220G-EVAL / STM3240G-EVAL contribution from eCosCentric
Date: Tue, 03 Apr 2012 18:46:00 -0000 [thread overview]
Message-ID: <20120403184611.D6DB32F78006@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001550-104@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=1001550
--- Comment #19 from Jonathan Larmour <jifl@ecoscentric.com> 2012-04-03 19:46:08 BST ---
(In reply to comment #18)
> Hi Jonathan,
>
> Could you check STM32 USB driver -> CYGHWR_HAL_STM32_RCC_APB1ENR_CAN
Hoho, I wouldn't have expected to find a CAN-related define in the USB driver!
Trivially fixed with CYGHWR_HAL_STM32_RCC_APB1ENR_CAN ->
CYGHWR_HAL_STM32_RCC_APB1ENR_CAN1 which I'll commit now.
Arguably, someone with a better ability to test USB may want to consider using
the clock descriptors and CYGHWR_HAL_STM32_CLOCK_ENABLE/DISABLE macros,
possibly as well as the new superior GPIO pin interface (even though the old
interface remains).
Although on the other hand, it looks like this form of USB device is a dead-end
- as far as I can tell, ST have moved towards a completely different OTG
peripheral instead with totally different interface, not just on F2/F4, but
also on F1 connectivity line parts.
Jifl
--
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:[~2012-04-03 18:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 1:45 [Bug 1001550] New: " bugzilla-daemon
2012-04-01 1:45 ` [Bug 1001550] " bugzilla-daemon
2012-04-01 1:46 ` bugzilla-daemon
2012-04-01 1:47 ` bugzilla-daemon
2012-04-01 1:48 ` bugzilla-daemon
2012-04-01 1:49 ` bugzilla-daemon
2012-04-01 1:49 ` bugzilla-daemon
2012-04-01 1:50 ` bugzilla-daemon
2012-04-01 1:51 ` bugzilla-daemon
2012-04-01 1:51 ` bugzilla-daemon
2012-04-01 19:41 ` bugzilla-daemon
2012-04-02 7:22 ` bugzilla-daemon
2012-04-02 11:43 ` bugzilla-daemon
2012-04-02 15:08 ` bugzilla-daemon
2012-04-02 15:56 ` bugzilla-daemon
2012-04-03 11:45 ` bugzilla-daemon
2012-04-03 12:54 ` bugzilla-daemon
2012-04-03 13:32 ` bugzilla-daemon
2012-04-03 17:17 ` bugzilla-daemon
2012-04-03 18:07 ` bugzilla-daemon
2012-04-03 18:46 ` bugzilla-daemon [this message]
2012-04-03 18:59 ` Christophe Coutand
2012-04-05 8:36 ` bugzilla-daemon
2012-04-05 15:42 ` bugzilla-daemon
2012-04-13 17:50 ` bugzilla-daemon
2012-04-13 17:51 ` bugzilla-daemon
2012-04-13 17:51 ` bugzilla-daemon
2012-04-13 17:57 ` bugzilla-daemon
2012-04-13 17:57 ` bugzilla-daemon
2012-04-13 17:58 ` bugzilla-daemon
2012-04-13 17:58 ` bugzilla-daemon
2012-04-13 18:01 ` bugzilla-daemon
2012-04-15 19:27 ` bugzilla-daemon
2012-04-16 14:28 ` bugzilla-daemon
2012-04-16 14:42 ` 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=20120403184611.D6DB32F78006@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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: 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).