History log of /openbmc/libmctp/README.md (Results 1 – 14 of 14)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# fa3bc56a 24-Feb-2025 Jeremy Kerr <jk@codeconstruct.com.au>

README: add 'Target usage' section

I get a few queries from people who are attempting to use libmctp as
their MCTP communication interface, and trying to get it to talk to an
AF_MCTP socket.

libmct

README: add 'Target usage' section

I get a few queries from people who are attempting to use libmctp as
their MCTP communication interface, and trying to get it to talk to an
AF_MCTP socket.

libmctp is unnecessary in this scenario, so add a usage note.

Change-Id: I4d46905f19054af3c0e4e3fde2815befc7f4752a
Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>

show more ...


# fbb6f40e 04-Aug-2024 George Liu <liuxiwei@ieisystem.com>

README.md: Fix MD030 warnings

The following warnings are generated by using markdownlint analysis:
```
README.md:101:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
READ

README.md: Fix MD030 warnings

The following warnings are generated by using markdownlint analysis:
```
README.md:101:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
README.md:104:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
```
Refer to markdown-lint [1] to fix MD030
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/030-list-marker-space.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I3cbcd5500404651ce7c98efa25504ad6dbe6284b

show more ...


# fecb358b 04-Aug-2024 George Liu <liuxiwei@ieisystem.com>

README.md: Fix MD034 warnings

The following warnings are generated by using markdownlint analysis:
```
MD034/no-bare-urls Bare URL used [Context: "openbmc@lists.ozlabs.org"]
MD034/no-bare-urls Bare

README.md: Fix MD034 warnings

The following warnings are generated by using markdownlint analysis:
```
MD034/no-bare-urls Bare URL used [Context: "openbmc@lists.ozlabs.org"]
MD034/no-bare-urls Bare URL used [Context: "https://discord.gg/69Km47zH98"]
```
Refer to markdown-lint [1] to fix MD034
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/034-no-bare-urls.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: Id5398d4ddf6e2e157e91e40b69ce1dcaa8aaf7d6

show more ...


# a68185c4 08-Dec-2022 Patrick Williams <patrick@stwcx.xyz>

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

Change-Id: Ibcba1d4dcfc062988d71ea12912b53512fa644ff
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...


Revision tags: v0.11
# 56886e7f 07-Jan-2022 Patrick Williams <patrick@stwcx.xyz>

README: fix libmctp spelling

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I288770d88c2c8ccf1ade4f9537d80c1801637ca2


# e3206690 17-Nov-2021 Jeremy Kerr <jk@codeconstruct.com.au>

README: OWNERS is the new MAINTAINERS

Change 0f22eaa000 removed the MAINTAINERS file, as it has been replaced
by OWNERS. However, we still have a reference to the former in the
README doc.

This cha

README: OWNERS is the new MAINTAINERS

Change 0f22eaa000 removed the MAINTAINERS file, as it has been replaced
by OWNERS. However, we still have a reference to the former in the
README doc.

This change updates that to refer to OWNERS instead.

Fixes: 0f22eaa ("libmctp: Remove MAINTAINERS in favour of OWNERS file")
Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
Change-Id: I57e918bac37269dc94b2a1e4625566d866c1b446

show more ...


# 52f4cb29 25-Nov-2020 Andrew Jeffery <andrew@aj.id.au>

README: Prominently address API/ABI stability

Make a header out of it to help catch people's eyes. Also add a contact
section beforehand so people know where to send feedback.

Signed-off-by: Andrew

README: Prominently address API/ABI stability

Make a header out of it to help catch people's eyes. Also add a contact
section beforehand so people know where to send feedback.

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

show more ...


Revision tags: v0.10
# 3b36d17c 03-Sep-2019 Jeremy Kerr <jk@ozlabs.org>

API: Add binding accessors to generic struct mctp_binding

Rather than have every binding include their own wrappers around
binding<->core functions, introduce an accessor to retrieve the struct
mctp

API: Add binding accessors to generic struct mctp_binding

Rather than have every binding include their own wrappers around
binding<->core functions, introduce an accessor to retrieve the struct
mctp_binding from each.

This means we no longer need the binding-specific registration
callbacks. However, we do now need a ->start callback, to allow bindings
to perform post-registration init.

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

show more ...


# 1a4ec3cd 02-Sep-2019 Jeremy Kerr <jk@ozlabs.org>

core,API: Add bridge support

This change introduces a facility to bridge messages between two
bindings.

This is implemented through a new mctp_bridge_busses() API, which
applies a new routing polic

core,API: Add bridge support

This change introduces a facility to bridge messages between two
bindings.

This is implemented through a new mctp_bridge_busses() API, which
applies a new routing policy, sending packets from one binding to the
other. This is in contrast to the current policy of dropping all
non-local packets.

To do this, the message context code needs to know both source and
destination EIDs, so add them to the mctp_msg_ctx_lookup() criteria.

Also, add a small test for bridge mode.

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

show more ...


# 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 ...


# 3cb4eee4 05-Mar-2019 Jeremy Kerr <jk@ozlabs.org>

API: Add MCTP_NO_DEFAULT_ALLOC facility

For platforms that don't have malloc/alloc/free available, we do not
want to use them as defaults.

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


# 2f7e05bd 07-Feb-2019 Jeremy Kerr <jk@ozlabs.org>

README: Add notes on integration

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


# 24db71fb 07-Feb-2019 Jeremy Kerr <jk@ozlabs.org>

core: implement packetisation and reassembly

Add a naive implementation of packetisation and reassembly of MCTP
messages. We use a (unbounded!) message buffer for reception, and a
queue of messages

core: implement packetisation and reassembly

Add a naive implementation of packetisation and reassembly of MCTP
messages. We use a (unbounded!) message buffer for reception, and a
queue of messages for transmission.

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

show more ...


# 4cdc200f 07-Feb-2019 Jeremy Kerr <jk@ozlabs.org>

Initial MCTP core code

Just a skeleton of the MCTP library at present.

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