Jan Kiszka wrote:
Roland Tollenaar wrote:
Hi Jan,
Err? What are practical cases for you?
Both modes are _debugging_ features.
Huh? There only seem to be two flavours. Listen_only or loopback. Are
you saying that for normal operation it does not matter at all what the
setting is? I.e. don't even have to bother setting the parameter?
Check the documentation of SIOCSCANCTRLMODE. It should clearly state
that those are modes can be activated additionally and independently.
Also check what happens in the existing rtcanconfig code, it underlines
this.
If you find an even better way to express this in the doc: patches are
welcome.
I'm going to update the doc as follows:
/*!
* @anchor CAN_CTRLMODE @name CAN controller modes
* Special CAN controllers modes, which can be or'ed together.
*
* @note These modes are hardware-dependent. Please consult the hardware
* manual of the CAN controller for more detailed information.
*
* @{ */
/*! Listen-Only mode
*
* In this mode the CAN controller would give no acknowledge to the
* CAN-bus, even if a message is received successfully and messages
* would not be transmitted. This mode might be useful for
* bus-monitoring, hot-plugging or throughput analysis. */
#define CAN_CTRLMODE_LISTENONLY 0x1
/*! Loopback mode
*
* In this mode the CAN controller does an internal loop-back, a message
* is transmitted and simultaneously received. That mode can be used for
* self test operation. */
#define CAN_CTRLMODE_LOOPBACK 0x2
Hope it's clearer now. For the moment, just don't care about special
features.
Wolfgang.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
