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 1001845] Add CAN support for Olimex olpce2294 board Date: Tue, 14 May 2013 12:29:00 -0000 [thread overview] Message-ID: <bug-1001845-777-p4wdyJUEOI@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001845-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001845 --- Comment #2 from Sergei Gavrikov <sergei.gavrikov@gmail.com> --- Uwe, thank you for issuing this. I have tried to test your patch and as I could see the macro HAL_LPC2XXX_GET_CAN_BR() is not provided for olpce2294 target: SYNOPSIS ecosconfig new olpce2294 ecosconfig add can ecosconfig tree make -s headers finished ... can_lpc2xxx.c:85:2: error: #error "Macro HAL_LPC2XXX_GET_CAN_BR() missing" ... can_lpc2xxx.c: In function 'lpc2xxx_can_set_baud': Could you, please, also define the missing macro for the target? However, I could miss some configure options, if it so, please, tell me how you configure and build the CAN driver for olpce2294 target? Thank you, Sergei -- You are receiving this mail because: You are the assignee for the bug.
next prev parent reply other threads:[~2013-05-14 12:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-13 19:56 [Bug 1001845] New: " bugzilla-daemon 2013-05-14 12:09 ` [Bug 1001845] " bugzilla-daemon 2013-05-14 12:29 ` bugzilla-daemon [this message] 2013-05-20 11:06 ` bugzilla-daemon 2013-05-20 20:28 ` bugzilla-daemon 2013-05-21 5:24 ` bugzilla-daemon 2013-05-21 19:02 ` bugzilla-daemon 2013-05-21 19:08 ` 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-1001845-777-p4wdyJUEOI@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).