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 1001453] New: CAN IO package: wider flags field, flag to report return to 'error active' mode Date: Fri, 13 Jan 2012 16:16:00 -0000 [thread overview] Message-ID: <bug-1001453-777@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=1001453 Summary: CAN IO package: wider flags field, flag to report return to 'error active' mode Product: eCos Version: CVS Platform: All OS/Version: Other 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 The CAN IO package reports events when the controller is downgraded to 'error passive' or 'bus off'. It does not report an event when it gets back to 'error active' mode: user code must poll the controller state to know about that status change instead of being able to keep the event callback logic for everything that concerns the CAN bus activity. The patch changes the 'flags' field of 'can_event_t' to 32 bits and add a new event in bit 16. The fields in 'can_event_t' are reordered to continue to provide a 24 bytes CAN event on an ARM MCU even if 'flags' is wider, so the operational cost is nil for such targets. Patch also includes doc fix and an option to add/suppress compiler flags for the package. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next reply other threads:[~2012-01-13 16:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-13 16:16 bugzilla-daemon [this message] 2012-01-13 16:17 ` [Bug 1001453] " bugzilla-daemon 2012-01-14 22:40 ` bugzilla-daemon 2012-01-15 13:56 ` bugzilla-daemon 2012-01-15 22:30 ` bugzilla-daemon 2012-01-16 8:16 ` bugzilla-daemon 2012-01-18 21:48 ` bugzilla-daemon 2012-01-25 11:35 ` bugzilla-daemon 2012-01-26 8:51 ` bugzilla-daemon 2012-02-06 20:30 ` bugzilla-daemon 2012-02-07 6:13 ` bugzilla-daemon 2012-02-10 17:29 ` bugzilla-daemon 2012-02-11 4:16 ` 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-1001453-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).