public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001900] New: Baudrate table for CAN clock of 14.7456 MHz
Date: Wed, 11 Sep 2013 06:17:00 -0000	[thread overview]
Message-ID: <bug-1001900-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=1001900

            Bug ID: 1001900
           Summary: Baudrate table for CAN clock of 14.7456 MHz
           Product: eCos
           Version: CVS
            Target: All
  Architecture/Host Other
                OS:
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: low
         Component: Patches and contributions
          Assignee: unassigned@bugs.ecos.sourceware.org
          Reporter: uwe_kindler@web.de
                CC: ecos-patches@ecos.sourceware.org

Created attachment 2358
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2358&action=edit
Baudrate table for CAN clock of 14.7456 MHz

The following patch adds baudrate table for CAN clock of 14.7456 MHz. This
clock is not very well suited for CAN communication but the table enables the
build of some targets (like the Olimex LPC2294 boards) that ship with this
clock. CAN communication at lower baudrates should be possible with this CAN
clock.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2013-09-11  6:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11  6:17 bugzilla-daemon [this message]
2013-09-11 17:58 ` [Bug 1001900] " bugzilla-daemon
2013-09-11 18:05 ` bugzilla-daemon
2013-09-11 21:09 ` bugzilla-daemon
2013-09-11 21:17 ` 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-1001900-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).