public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001435] New: CAN documentation (docs-latest) issues Date: Thu, 29 Dec 2011 11:32:00 -0000 [thread overview] Message-ID: <bug-1001435-13@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=1001435 Summary: CAN documentation (docs-latest) issues Product: eCos Version: CVS Platform: All OS/Version: Other Status: UNCONFIRMED Severity: minor Priority: low Component: CAN AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: bernard.fouche@kuantic.com CC: ecos-bugs@ecos.sourceware.org Class: Advice Request While porting an application using CAN bus, I read the latest eCos documentation. I report here the issue I find in the eCos CAN documentation. CAN Messages: cyg_can_message structure now uses specific data type for data field (cyg_can_msg_data vs cyg_uint8) Message box configuration (cyg_can_msgbox_info_st): the two fields (count, free) are described as being cyg_uint8, they are now cyg_uint16. Reading hardware description information: CYGNUM_CAN_HDI_FILT_SW has been replaced by CYGNUM_CAN_HDI_AUTBAUD. -- 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:[~2011-12-29 11:32 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-29 11:32 bugzilla-daemon [this message] 2011-12-31 16:08 ` [Bug 1001435] " bugzilla-daemon 2012-01-10 16:28 ` bugzilla-daemon 2011-12-29 11:32 [Bug 1001435] New: " 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-1001435-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-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).