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 1001211] New: CAN loopback driver requires CYGPKG_DEVS_CAN_LOOP_CAN[01]
Date: Mon, 02 May 2011 08:43:00 -0000 [thread overview]
Message-ID: <bug-1001211-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=1001211
Summary: CAN loopback driver requires
CYGPKG_DEVS_CAN_LOOP_CAN[01]
Product: eCos
Version: CVS
Platform: All
OS/Version: All
Status: NEW
Severity: minor
Priority: normal
Component: CAN
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: john@dallaway.org.uk
CC: ecos-bugs@ecos.sourceware.org, uwe_kindler@web.de
Class: Advice Request
The alarm_handler() function in the CAN loopback driver requires both
CYGPKG_DEVS_CAN_LOOP_CAN0 and CYGPKG_DEVS_CAN_LOOP_CAN1 to be explicitly
enabled in order to build correctly.
It seems that users who add the CAN loopback driver package to their eCos
configuration will definitely intend to use the CAN loopback devices and the
CDL components should therefore be enabled by default. If there is any value in
being able to disable these components, then the driver should adapt
accordingly.
Uwe, what was your intention regarding the configuration of these CDL
components?
--
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-05-02 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 8:43 bugzilla-daemon [this message]
2013-06-06 9:42 ` [Bug 1001211] " bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2011-05-02 8:42 [Bug 1001211] 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-1001211-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: link
Be 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).