Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / obmc-console / 12398cd53e75f3887b0615f00b90f3004d6e736b
commit12398cd53e75f3887b0615f00b90f3004d6e736b[log] [tgz]
authorAndrew Jeffery <andrew@codeconstruct.com.au>Tue Jul 09 14:59:33 2024 +0930
committerAndrew Jeffery <andrew@codeconstruct.com.au>Tue Jul 09 17:57:17 2024 +0930
tree250ab5f57e52fa97875f88272d5a2f0b8a3dbba9
parent7851a396511b623aca735d607382b93494c332a4 [diff]
console-dbus: Connect to the default bus

sd_bus_default() connects to the system bus unless it detects a user
slice, in which case it connects to the bus for the user session.

This should keep the desired behavior in-context e.g. on a BMC, while
making it slightly more ergonomic to run obmc-console-server under
dbus-run-session(1) for testing.

Change-Id: I0b5acfae49dcab9ec4f72159ba51296e118017ae
Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
1 file changed
tree: 250ab5f57e52fa97875f88272d5a2f0b8a3dbba9
  1. conf/
  2. test/
  3. .clang-format
  4. .clang-tidy
  5. .gitignore
  6. .travis.yml
  7. CHANGELOG.md
  8. config.c
  9. console-client.c
  10. console-dbus.c
  11. console-server.c
  12. console-server.h
  13. console-socket.c
  14. LICENSE
  15. log-handler.c
  16. meson.build
  17. meson.options
  18. OWNERS
  19. README.md
  20. ringbuffer.c
  21. socket-handler.c
  22. tty-handler.c
  23. util.c
README.md

To Build

To build this project, run the following shell commands:

meson setup build
meson compile -C build

To test:

meson test -C build

To Run Server

Running the server requires a serial port (e.g. /dev/ttyS0):

touch obmc-console.conf
./obmc-console-server --config obmc-console.conf ttyS0

To Connect Client

To connect to the server, simply run the client:

./obmc-console-client

To disconnect the client, use the standard ~. combination.

Underlying design

This shows how the host UART connection is abstracted within the BMC as a Unix domain socket.

               +---------------------------------------------------------------------------------------------+
               |                                                                                             |
               |       obmc-console-client       unix domain socket         obmc-console-server              |
               |                                                                                             |
               |     +----------------------+                           +------------------------+           |
               |     |   client.2200.conf   |  +---------------------+  | server.ttyVUART0.conf  |           |
           +---+--+  +----------------------+  |                     |  +------------------------+  +--------+-------+
Network    | 2200 +-->                      +->+ @obmc-console.host0 +<-+                        <--+ /dev/ttyVUART0 |   UARTs
           +---+--+  | console-id = "host0" |  |                     |  |  console-id = "host0"  |  +--------+-------+
               |     |                      |  +---------------------+  |                        |           |
               |     +----------------------+                           +------------------------+           |
               |                                                                                             |
               |                                                                                             |
               |                                                                                             |
               +---------------------------------------------------------------------------------------------+

This supports multiple independent consoles. The console-id is a unique portion for the unix domain socket created by the obmc-console-server instance. The server needs to know this because it needs to know what to name the pipe; the client needs to know it as it needs to form the abstract socket name to which to connect.