From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001861] New: Patch for TWR-K60FN120 board
Date: Sat, 08 Jun 2013 23:34:00 -0000 [thread overview]
Message-ID: <bug-1001861-104@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001861
Bug ID: 1001861
Summary: Patch for TWR-K60FN120 board
Product: eCos
Version: unknown
Target: freescale_twr_k60n512 (Freescale Kinetis TWR-K60N512)
Architecture/Host Cortex-M
OS:
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: Patches and contributions
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: mjones@linear.com
CC: ecos-patches@ecos.sourceware.org
Created attachment 2251
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2251&action=edit
HAL patch
This patch was tested with: Ethernet/LwIP, UART5/Terminal, and I2C0. It is very
similar to the K70 HAL but the DDRAM was removed, and IO pins were changed to
match the board. Compilation with and without Floating Point and Cache was
tested. It is simple to tree diff this against the K70 to see there are few
chances of mistakes, but someone that knows K70 well may want to diff it to
check.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-06-08 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 23:34 bugzilla-daemon [this message]
2013-06-08 23:35 ` [Bug 1001861] " bugzilla-daemon
2013-06-09 7:36 ` bugzilla-daemon
2013-06-09 22:34 ` bugzilla-daemon
2013-06-26 16:58 ` bugzilla-daemon
2013-06-26 16:59 ` bugzilla-daemon
2013-07-01 8:26 ` bugzilla-daemon
2013-07-01 15:20 ` bugzilla-daemon
2013-07-01 15:25 ` bugzilla-daemon
2013-07-03 10:47 ` bugzilla-daemon
2017-02-15 7:26 ` 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-1001861-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).