public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001869] New: Add support for reading CAN hardware error counters Date: Mon, 24 Jun 2013 14:07:00 -0000 [thread overview] Message-ID: <bug-1001869-777@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=1001869 Bug ID: 1001869 Summary: Add support for reading CAN hardware error counters Product: eCos Version: CVS Target: All Architecture/Host HostOS: Win XP/7 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 2267 --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2267&action=edit CAN error counter reading patch The attached patch adds support for reading the CAN hardware RX and TX error counters. All CAN nodes support these hardware error counters and therefore this features is a common CAN feature for all CAN device drivers. Support for reading error counters has been implemented for LPC2xxx CAN device driver. -- You are receiving this mail because: You are the assignee for the bug.
next reply other threads:[~2013-06-24 14:07 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-24 14:07 bugzilla-daemon [this message] 2013-08-27 10:41 ` [Bug 1001869] " bugzilla-daemon 2013-08-27 12:46 ` bugzilla-daemon 2013-08-27 18:46 ` bugzilla-daemon 2013-08-28 8:12 ` bugzilla-daemon 2013-08-28 9:39 ` bugzilla-daemon 2013-08-28 16:37 ` bugzilla-daemon 2013-08-29 9:28 ` 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-1001869-777@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@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).