Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / obmc-console / bae933a7c1aed0708b6c76a8833f4a4cbeb4190a
commitbae933a7c1aed0708b6c76a8833f4a4cbeb4190a[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Tue Oct 24 03:15:52 2023 -0500
committerAndrew Jeffery <andrew@codeconstruct.com.au>Fri Oct 27 16:54:24 2023 +1030
tree1093eedb3248bf6dedda46318d4687be905191e4
parent955d140e3caafb8a082a094d4fb6ebd2e3d7782a [diff]
meson: rename options file

Meson supports the options being in a `meson.options` instead of a
generic text file so leverage this option. Use of `meson.options`
requires at least meson v1.1.0, but that in turn yields an issue with
the options file:

```
meson.options:2: WARNING: Project targets '>=1.1.0' but uses feature deprecated since '1.1.0': "boolean option" keyword argument "value" of type str. use a boolean, not a string
```

Fix all of these issues together.

Change-Id: Idebe8f5ccd2d7ba2dbb0a45a274deac0c1fd327d
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
2 files changed
tree: 1093eedb3248bf6dedda46318d4687be905191e4
  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.