From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001463] New: LPC17XX supplementary code/option patch
Date: Wed, 25 Jan 2012 16:17:00 -0000 [thread overview]
Message-ID: <bug-1001463-104@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001463
Summary: LPC17XX supplementary code/option patch
Product: eCos
Version: CVS
Platform: All
OS/Version: Cortex-M
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: Patches and contributions
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: bernard.fouche@kuantic.com
CC: ecos-patches@ecos.sourceware.org
Class: Advice Request
Hello.
This patch:
- allows configuration of all peripheral clocks.
- use the fractional baud rate divider for all UART, for all possible clocks
>300bps.
- using PLL0 is an option.
- using USB clock is an option.
- consider all LPC MCU known to have CAN bus support
- fixes some erroneous peripheral definitions and adds new ones
- brings the bit band macro in the LPC17XX code. Debate about where to define
these macros is not closed yet but I need to move on so better defining them
here at the moment ;-)
--
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 reply other threads:[~2012-01-25 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 16:17 bugzilla-daemon [this message]
2012-01-25 16:18 ` [Bug 1001463] " bugzilla-daemon
2012-01-25 21:42 ` bugzilla-daemon
2012-01-26 9:05 ` bugzilla-daemon
2012-01-26 10:18 ` 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=bug-1001463-104@http.bugs.ecos.sourceware.org/ \
--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).