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 1001901] Add CAN support for Olimex olpcl2294 board Date: Wed, 11 Sep 2013 17:42:00 -0000 [thread overview] Message-ID: <bug-1001901-777-OqqRbLDwHw@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001901-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=1001901 --- Comment #2 from Sergei Gavrikov <sergei.gavrikov@gmail.com> --- Hi Uwe, I tried to compile CAN driver for LPC-L2294-1M (with patches applied): % ecosconfig new olpcl2294 % ecosconfig add can ... In file included from devs/can/arm/lpc2xxx/current/src/can_lpc2xxx.c:723:0: devs/can/arm/lpc2xxx/current/src/can_accfilt_lpc2xxx.c: In function 'lpc2xxx_can_accfilt_simple_rx_all': devs/can/arm/lpc2xxx/current/src/can_accfilt_lpc2xxx.c:774:68: error: 'lpc2xxx_global_can_info_t' has no member named 'init_cnt' ... make[1]: *** [src/can_lpc2xxx.o.d] Error 1 make: *** [build] Error 2 It looks like that with CYGINT_IO_CAN_CHANNELS == 1, can_lpc2xxx.c cannot be compiled. FYI: I get the same error for LPC-E2294 with such a configuration # Force CYGINT_IO_CAN_CHANNELS be 1 cdl_configuration eCos { template default ; package CYGPKG_IO_CAN current ; }; cdl_component CYGPKG_DEVS_CAN_LPC2XXX_CAN1 { user_value 0 }; cdl_component CYGPKG_DEVS_CAN_LPC2XXX_CAN2 { user_value 0 }; cdl_component CYGPKG_DEVS_CAN_LPC2XXX_CAN3 { user_value 0 }; Therefore, the error was not entered with the patch. Could you, please, look on the LPC2XXX CAN code? Thank you. Sergei -- You are receiving this mail because: You are the assignee for the bug.
next prev parent reply other threads:[~2013-09-11 17:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-11 6:31 [Bug 1001901] New: " bugzilla-daemon 2013-09-11 6:33 ` [Bug 1001901] " bugzilla-daemon 2013-09-11 17:42 ` bugzilla-daemon [this message] 2013-09-11 19:28 ` bugzilla-daemon 2013-09-11 21:12 ` 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-1001901-777-OqqRbLDwHw@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).