Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / ipmbbridge / 35e1485f76a1562d0782a3a0dc003d0a7ac76ed9
commit35e1485f76a1562d0782a3a0dc003d0a7ac76ed9[log] [tgz]
authorEd Tanous <etanous@nvidia.com>Tue Apr 22 06:54:57 2025 -0700
committerEd Tanous <ed@tanous.net>Tue Apr 22 06:55:47 2025 -0700
treec7929eefb95c3378e4557a3351242a7f5e5c50d1
parentb922c2d564cdb7c961d5e2596060005b7d35766e [diff]
Add dependency on boost::context

Boost 1.87 now seems to require this.

Change-Id: I439b9d0bb66a989ce6acb43fbc058cc29324e511
Signed-off-by: Ed Tanous <etanous@nvidia.com>
1 file changed
tree: c7929eefb95c3378e4557a3351242a7f5e5c50d1
  1. subprojects/
  2. .clang-format
  3. ipmb-channels.json
  4. ipmb.service
  5. ipmbbridged.cpp
  6. ipmbbridged.hpp
  7. ipmbdefines.hpp
  8. ipmbutils.cpp
  9. ipmbutils.hpp
  10. LICENSE
  11. meson.build
  12. OWNERS
  13. README.md
README.md

Sample config options available to configure :

  1. Single channel with one me and ipmb :
{
  "channels": [
    {
      "type": "me",
      "slave-path": "/dev/ipmb-4",
      "bmc-addr": 32,
      "remote-addr": 44
    },
    {
      "type": "ipmb",
      "slave-path": "/dev/ipmb-9",
      "bmc-addr": 32,
      "remote-addr": 96
    }
  ]
}
  1. Multiple sub channels with me and ipmb :
{
  "channels": [
    {
      "type": "me",
      "slave-path": "/dev/ipmb-1",
      "bmc-addr": 32,
      "remote-addr": 64,
      "devIndex": 0
    },
    {
      "type": "ipmb",
      "slave-path": "/dev/ipmb-3",
      "bmc-addr": 32,
      "remote-addr": 64,
      "devIndex": 0
    },
    {
      "type": "me",
      "slave-path": "/dev/ipmb-5",
      "bmc-addr": 32,
      "remote-addr": 64,
      "devIndex": 1
    },
    {
      "type": "ipmb",
      "slave-path": "/dev/ipmb-7",
      "bmc-addr": 32,
      "remote-addr": 64,
      "devIndex": 1
    }
  ]
}

Config fields :

type          : This points to the ChannelType. It can be ME or ipmb channel.
slave-path    : The ipmb device path.
bmc-addr      : This is BMC target address to communicate between BMC and device.
remote-addr   : This is Remote/requester target address to communicate between BMC and device.
devIndex      : This devIndex used to identify the particular device/host.