| //! Chain macro in Rust | |
| //! | |
| //! A typical usage is to avoid nested match expressions. | |
| //! | |
| //! Supports: | |
| //! - Pattern matching | |
| //! - Or expressions (A | B => ...) | |
| //! - Guarded statements (x if <cond> => ...) | |
| //! - Implicit else (requires all arms to return same type) |
| #!/bin/env bash | |
| # I don't know way, but without this line gcc start to compile stdout :\ | |
| exec 1>&2 | |
| set -x | |
| # build the linux targets with {linux_headers_path}/build; | |
| # compile it to the our Makefile's path and read | |
| # our Makefile from stdin to make its path simpler. |
Information can be put into dmi tables via some qemu-system hosts (x86_64 and aarch64). That information is exposed in Linux under /sys/class/dmi/id and can be read with dmidecode. The names are very annoyingly inconsistent. The point of this doc is to map them.
Example qemu cmdline:
qemu-system-x86_64 -smbios type=<type>,field=value[,...]
qemu-system-x86_64 -smbios type=0,vendor=superco,version=1.2.3