History log of /openbmc/libmctp/configure.ac (Results 1 – 18 of 18)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 895083b5 06-Oct-2023 Andrew Jeffery <andrew@codeconstruct.com.au>

configure.ac: Run autoupdate

Deal with the following warning:

```
configure.ac:25: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:25: You should run autoupdate.
```

Change-Id: Ia9f5

configure.ac: Run autoupdate

Deal with the following warning:

```
configure.ac:25: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:25: You should run autoupdate.
```

Change-Id: Ia9f5431a9a4d6b5d204c6f6acd8eb71ab944505c
Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>

show more ...


# 400766f9 07-Sep-2023 Konstantin Aladyshev <aladyshev22@gmail.com>

astlpc: Provide KCS device path as a binding argument

Currently astlpc binding expects a '/dev/mctp0' device in the system
for the KCS communication. This device is a symbolic link to the
real '/dev

astlpc: Provide KCS device path as a binding argument

Currently astlpc binding expects a '/dev/mctp0' device in the system
for the KCS communication. This device is a symbolic link to the
real '/dev/raw-kcsX' device, created by the udev rules populated by the
build system.
This approach is not ideal since the build system populates udev rules
for the KCS3 and KCS4 channels simultaneously and for these channels
only. This means that there are some design limitations for the MCTP
communication. It is only possible on KCS3 or KCS4 channel, and if one
of these channels is used, the other one must be disabled.
To make design more flexible get rid of all the udev rules and provide
'/dev/raw-kcsX' device path as an argument to the binding
initialization code.

Change-Id: I505e44280636c83b59669b314f60279b371d0403
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>

show more ...


Revision tags: v0.11
# e750cbce 17-Feb-2022 Andrew Jeffery <andrew@aj.id.au>

libmctp: v0.11

Tagged in preparation for an API change to introduce TO and tag bits
into the Rx/Tx APIs.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: Ief56ddfea481a89b4843a8c19407c66c

libmctp: v0.11

Tagged in preparation for an API change to introduce TO and tag bits
into the Rx/Tx APIs.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: Ief56ddfea481a89b4843a8c19407c66ce19edac8

show more ...


# cad47301 20-Aug-2021 Andrew Jeffery <andrew@aj.id.au>

mctp-demux-daemon: Add packet capture option

Optionally enable libpcap support in mctp-demux-daemon to capture
packets both from the Unix domain socket and binding interfaces.
Providing the two capt

mctp-demux-daemon: Add packet capture option

Optionally enable libpcap support in mctp-demux-daemon to capture
packets both from the Unix domain socket and binding interfaces.
Providing the two capture points allows for tracking down issues with
packets being dropped during binding initialisation.

As there's no formal linktype defined for MCTP or higher-level DMTF
protocols command-line switches provide the ability to specify one of
the private linktype values in the range 147-162.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I593d9e4be80c0198e643758f216e774169668a8c

show more ...


# d4103f8f 16-Jun-2021 Andrew Jeffery <andrew@aj.id.au>

mctp-demux-daemon: Use systemd socket activation

Take advantage of lazy initialisation.

However, this also allows (one) daemon providing services over MCTP
(pldmd) an opportunity to start prior to

mctp-demux-daemon: Use systemd socket activation

Take advantage of lazy initialisation.

However, this also allows (one) daemon providing services over MCTP
(pldmd) an opportunity to start prior to MCTP interfaces coming up. This
is a stunted way to provide capabilities that might be assumed by other
components (the host) without implementing some required messages from
the MCTP standard.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I4b1c21f4fd42f84e2c85a453570a74330fc70ecf

show more ...


# 9f5b47a5 11-May-2021 Andrew Jeffery <andrew@aj.id.au>

configure: Ensure udev rules are installed in rules.d

udevdir is set to the udev root, e.g. /lib/udev, while rules need to
live in the rules.d subdirectory.

Signed-off-by: Andrew Jeffery <andrew@aj

configure: Ensure udev rules are installed in rules.d

udevdir is set to the udev root, e.g. /lib/udev, while rules need to
live in the rules.d subdirectory.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I9416eb7e5a99a4bf8391a4ba135c26f43a79822c

show more ...


# 745b1d15 10-May-2021 Andrew Jeffery <andrew@aj.id.au>

astlpc: Ship udev rules to help with device and driver transition

Currently the OpenBMC kernel has a hacky device driver at
drivers/char/misc/mctp-lpc.c that only works against KCS channel 4 on
Aspe

astlpc: Ship udev rules to help with device and driver transition

Currently the OpenBMC kernel has a hacky device driver at
drivers/char/misc/mctp-lpc.c that only works against KCS channel 4 on
Aspeed BMCs. This hacky driver exposes an `mctp0` device node.

The intent is to replace it with one that is slightly less
hacky at drivers/char/ipmi/kcs_bmc_cdev_raw.c[1], though eventually this
too will be replaced by an in-kernel implementation of the entire LPC
MCTP binding.

kcs_bmc_dev_raw.c works against all KCS devices in both Aspeed and
Nuvoton BMC SoCs.

We need to move away from KCS channel 4 on the Aspeed BMCs as the way
the hardware initialises the status bits conflicts with the protocol
definition for the LPC MCTP binding[2].

Kill two birds with one stone by shipping udev rules that accomodate the
new device node names that come with kcs_bmc_dev_raw.c, and symlink them
upon creation to /dev/mctp0 to emulate the original mctp-lpc.c
interface.

[1] https://lore.kernel.org/openbmc/20210510064955.1704652-1-andrew@aj.id.au/T/#me02d9a0e6ce82c9e0602cd615ccdad66d242af87
[2] https://github.com/openbmc/libmctp/blob/eba19a3b122a39ef2b5dbda49b418a202f78a48d/docs/bindings/vendor-ibm-astlpc.md#kcs-status-register-layout

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I21446936cea6c5e4024ec6536ad5983dd360deb2

show more ...


Revision tags: v0.10
# 8536cfcf 12-Jun-2020 Andrew Jeffery <andrew@aj.id.au>

libmctp: v0.10

Introduce v2 of the astlpc binding protocol.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: Idaba0167f605d51fba30cebdce432ca9c38463d7


# 8d53b1c3 28-May-2020 Andrew Jeffery <andrew@aj.id.au>

configure: Enable valgrind support

I've caught some issues with valgrind that were missed by the compiler
sanitizers (though were interestingly picked up by the cmake build of
the test suites).

Sig

configure: Enable valgrind support

I've caught some issues with valgrind that were missed by the compiler
sanitizers (though were interestingly picked up by the cmake build of
the test suites).

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I96ac0a331c2d7466ee66a7ce2e8d8b2b8d497d5d

show more ...


# 7b08721e 17-Mar-2020 Andrew Jeffery <andrew@aj.id.au>

configure: Expose optional features via AC_ARG_WITH()

This allows us to exercise different potential target environments by
turning features on and off via the build system. With some CI magic we
ca

configure: Expose optional features via AC_ARG_WITH()

This allows us to exercise different potential target environments by
turning features on and off via the build system. With some CI magic we
can help ensure that the code doesn't bitrot for these environments.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I75a8e28f32149e9f78dbe68510b5516f89dc9137

show more ...


# 3286f176 17-Mar-2020 Andrew Jeffery <andrew@aj.id.au>

astlpc: Conditionally include endian.h

endian.h isn't standardised and isn't provided by some target
environments. Conditionally include it to avoid compilation errors,
however the target environmen

astlpc: Conditionally include endian.h

endian.h isn't standardised and isn't provided by some target
environments. Conditionally include it to avoid compilation errors,
however the target environment must provide its own implementation,
possibly via config.h.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: Ic60079204cffe7730f552f2c3c34e88bfce4f515

show more ...


# d09253f0 25-Feb-2020 Andrew Jeffery <andrew@aj.id.au>

configure: Disable portability to cater to code-coverage

Avoid a mass of warnings from automake. We will reassess if portability
ever becomes a necessary property.

Signed-off-by: Andrew Jeffery <an

configure: Disable portability to cater to code-coverage

Avoid a mass of warnings from automake. We will reassess if portability
ever becomes a necessary property.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I2fb620c0471aac4ff6712383880509bbf0ab0d9e

show more ...


# 1e496c8b 16-Jan-2020 Xiaochao Ma <maxiaochao@inspur.com>

Add MCTP service file

Previous service file for this repo are contained
in the corresponding meta layer.
Now move it into the repository that owns them.

Signed-off-by: Xiaochao Ma <maxiaochao@inspu

Add MCTP service file

Previous service file for this repo are contained
in the corresponding meta layer.
Now move it into the repository that owns them.

Signed-off-by: Xiaochao Ma <maxiaochao@inspur.com>
Change-Id: I15d85815483da19b08869225eb50866b49fe5575

show more ...


# 7344ac2a 09-Jan-2020 Andrew Jeffery <andrew@aj.id.au>

configure: Add code coverage magic

Autoconf changed the way code-coverage was handled in the recent past,
so there a slight complication so we work across both implementations.

Signed-off-by: Andre

configure: Add code coverage magic

Autoconf changed the way code-coverage was handled in the recent past,
so there a slight complication so we work across both implementations.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I675c64953d262cd4b26a8ab758290ef4325790c0

show more ...


# 682232ea 12-Jan-2020 Andrew Jeffery <andrew@aj.id.au>

log: Allow disabling of stdio

Some firmwares (e.g. Hostboot) don't provide stdio.h. Make sure we can
compile in these environments.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I3a5f4

log: Allow disabling of stdio

Some firmwares (e.g. Hostboot) don't provide stdio.h. Make sure we can
compile in these environments.

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I3a5f414f12fbf9de70fb41033d610f81094848bf

show more ...


# 80971f84 28-Aug-2019 Jeremy Kerr <jk@ozlabs.org>

Add pkg-config definition for libmctp

Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
Change-Id: I276caf181d398d1b4a217f2ff59e5e7d31b47b6a


# c7e764a2 28-May-2019 Jeremy Kerr <jk@ozlabs.org>

Rework conditional feature usage

Currently, the infrastructure that we have to enable a flexible
compilation environment has a few issues:

- the allocator configuration is performed at run-time, w

Rework conditional feature usage

Currently, the infrastructure that we have to enable a flexible
compilation environment has a few issues:

- the allocator configuration is performed at run-time, while the log
configuration is performed at compile-time

- for a standard compile (ie, standard userspace, using
autoconf+automake to build), we need a few pre-defined configuration
options.

This change adds a bit of runtime selection to the logging
infrastructure, to match the allocator setup. We also unify the
compile-time defines into config.h, using MCTP_-prefixed macro names,
allowing integration into other build systems.

Signed-off-by: Jeremy Kerr <jk@ozlabs.org>

show more ...


# b2ef62ba 27-May-2019 Jeremy Kerr <jk@ozlabs.org>

autoconfiscate

Add autoconf, libtool, automake and bootstrap tools. While this will be
used for the typical "build a shared-library" use-case, we still want to
support other build types that may use

autoconfiscate

Add autoconf, libtool, automake and bootstrap tools. While this will be
used for the typical "build a shared-library" use-case, we still want to
support other build types that may use the libmctp code directly, and
not use autoconf.

Signed-off-by: Jeremy Kerr <jk@ozlabs.org>

show more ...