public inbox for ecos-cvs@sourceware.org
help / color / mirror / Atom feed
From: sergeig@sourceware.org
To: ecos-cvs@ecos.sourceware.org
Subject: ecos/packages/io/can/current ChangeLog cdl/io_ ...
Date: Thu, 09 Feb 2012 21:16:00 -0000 [thread overview]
Message-ID: <20120209211649.23692.qmail@sourceware.org> (raw)
CVSROOT: /cvs/ecos
Module name: ecos
Changes by: sergeig@sourceware.org 2012-02-09 21:16:49
Modified files:
packages/io/can/current: ChangeLog
packages/io/can/current/cdl: io_can.cdl
packages/io/can/current/doc: can.sgml can_driver_doc.html
packages/io/can/current/include: can.h canio.h
packages/io/can/current/src: can.c
Log message:
* cdl/io_can.cdl: support for add/remove compiler flags
* doc/can.sgml, doc/can_driver_doc.html: updated doc reflecting API
changes (range/mask filtering, listen-only mode, return values for
xmt_msg/rcv_event, new flags).
* include/can.h: given in a match the types of function pointers for
can_callbacks_t according to the changes made in can.c.
* include/canio.h: flags field in event enlarged to 32 bits to fit
new events 'CYGNUM_CAN_EVENT_ERR_ACTIVE' and
'CYGNUM_CAN_EVENT_OVERRUN_RX_HW'. Made a 'flag' typedef.
cyg_can_event fields reordered so flags size change keeps events the
same size. Defined new filtering capabilities (range/mask). New
convenience macro CYGNUM_CAN_EVENT_ALL. New listen-only mode.
* src/can.c: can_rcv_event() and can_xmt_msg() now returns cyg_bool
(were 'void'). flags using cyg_can_event_flags_t type.
[ Bugzilla 1001453 ]
next reply other threads:[~2012-02-09 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 21:16 sergeig [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-13 7:36 asl
2007-03-26 10:43 asl
2006-08-25 11:56 gthomas
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=20120209211649.23692.qmail@sourceware.org \
--to=sergeig@sourceware.org \
--cc=ecos-cvs@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).