| commit | 73d8bc801d7470da3674456d0b7c97f7ff82ec60 | [log] [tgz] |
|---|---|---|
| author | Jeremy Kerr <jk@ozlabs.org> | Fri Feb 08 09:34:20 2019 +0800 |
| committer | Jeremy Kerr <jk@ozlabs.org> | Fri Feb 08 10:02:38 2019 +0800 |
| tree | cc24325763d339c3d5803b3e9ea3b604debe607e | |
| parent | e16eaabe94e24ccdc9604163d418ca1b652810ce [diff] |
tests/mctp-pipe: Use SOCK_STREAM for internal serial link Currently, we have no way to determine when the MCTP session should be closed, when using SOCK_DGRAM. While this will be the case for a "real" serial link, we want the test program to be able to terminate. This change uses SOCK_STREAM instead, which means that we can terminate the MCTP session on EOF on stdin. This allows the pipe to exit. Additionally, this means that the read() boundaries may not correspond to the write() boundaries, which gives more testing to the serial state mechanism. Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
This library is intended to be a portable implementation of the Management Component Transport Protocol (MCTP), as defined by DMTF standard "DSP0236", plus transport binding specifications.
Currently, the library is is only at prototyping stage. Interfaces will likely change, and are missing lots of components of the standard.
To initialise the MCTP stack with a single hardware bus:
mctp = mctp_init(): Initialise the MCTP corebinding = mctp_<binding>_init(): Initialise a hardware bindingmctp_register_bus(mctp, binding, eid): Register the hardware binding with the core, using a predefined EIDThen, register a function call to be invoked when a message is received:
mctp_set_rx_all(mctp, function): Provide a callback to be invoked when a MCTP message is receivedOr transmit a message:
mctp_message_tx(mctp, message, len): Transmit a MCTP messageThe binding may require you to notify it to receive packets. For example, for the serial binding, the mctp_serial_read() function should be invoked when the file-descriptor for the serial device has data available.
This library is intended to be portable to be used in a range of environments, but the main targets are:
For the latter, we need to support customisation of the functions that libmctp uses (for example, POSIX file IO is not available).
In order to support these, we have a couple of compile-time definitions:
MCTP_FILEIO: define if POSIX file io is available, allowing the serial hardware binding to access char devices for IO.
MCTP_LOG_: allows selection of a logging backend. Currently available are:
MCTP_LOG_STDERR: use fprintf(stderr, ...) for log output
MCTP_LOG_SYSLOG: use syslog() for log output
MCTP_LOG_CUSTOM: provide your own macro for logging, of the format: #define mctp_prlog(level, fmt, ...) (....)