public inbox for ecos-cvs@sourceware.org help / color / mirror / Atom feed
From: asl@sourceware.org To: ecos-cvs@ecos.sourceware.org Subject: ecos/packages/io/can/current ChangeLog cdl/io_ ... Date: Mon, 26 Mar 2007 10:43:00 -0000 [thread overview] Message-ID: <20070326104336.8791.qmail@sourceware.org> (raw) CVSROOT: /cvs/ecos Module name: ecos Changes by: asl@sourceware.org 2007-03-26 11:43:36 Modified files: packages/io/can/current: ChangeLog packages/io/can/current/cdl: io_can.cdl packages/io/can/current/doc: can_driver_doc.html packages/io/can/current/include: can.h canio.h packages/io/can/current/src: can.c Added files: packages/io/can/current/tests: can_filter.c can_hdi.c can_load.c can_remote.c can_test_aux.inl can_tx.c Log message: * cdl/io_can.cdl: Added several interfaces for implementation by device drivers. Moved several configuration options from device drivers to the generic CAN driver. With this design a device driver does not need to provide all configuration options in its CDL file - it simply needs to implement the provided interfaces. The drawback of this decicsion is, that it is not possible to control these options independently for several CAN devices. (But most platforms will have only 1 channel) Added configuration option CYGBLD_IO_CAN_EXTRA_TESTS. This option enables the build of the interactive CAN tests. * test/can_filter: Added interactive message filtering test * test/can_hdi: Added interactive hardware description interface test * test/can_load: Added interactive message handling (reception, transmission) test. * test/can_remote: Added interactive remote response buffer test * test/can_tx: Added interactive basic TX test. All tests are not part of the eCos test framework because they are interactive. That means, they require interaction with another user controlled CAN node. * include/can.h: Added identifier masks for standard and extended identifiers. Added the line #include CYGDAT_IO_CAN_DEVICE_INL. This enables a device driver to provide an own device inline file. In this inline file the driver may define own data types for CAN messages (for internal storage of CAN messages (see AT91SAM7 CAN driver)) * include/canio.h: Added baudrate CYGNUM_CAN_KBAUD_AUTO - support of automatic baudrate detection if a driver supports such a feature. Added state CYGNUM_CAN_STATE_CONFIG and mode CYGNUM_CAN_MODE_CONFIG. The application may use these identifiers to set the CAN device into a state where it is safe to add/remove/configure message buffers. Added union data type cyg_can_msg_data. With this data type a 4 byte alignment of message data is guaranteed, an byte, word and dword access to the data is possible and an assignment of two CAN datas are possible now. cyg_can_message now uses cyg_can_msg_data union for CAN data. Replaced SW-Filt flag by autobaud flag in HDI. Added CAN message access macros for read/write acces of CAN message structures. These macros hide implementation of CAN message from application. * src/can.c: Added support for device driver defined CAN message data types
next reply other threads:[~2007-03-26 10:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-26 10:43 asl [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-02-09 21:16 sergeig 2007-08-13 7:36 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=20070326104336.8791.qmail@sourceware.org \ --to=asl@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: 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).