Console and outputs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(fix typo) |
||
Line 13: | Line 13: | ||
| | | | ||
* An internal(not USB) serial port: | * An internal(not USB) serial port: | ||
** it can on the mainboard | ** it can be on the mainboard | ||
** it can also be a PCIe OXPCIe952 card with the 0x1415 and 0xc158 vendor and device ID (respectively). | ** it can also be a PCIe OXPCIe952 card with the 0x1415 and 0xc158 vendor and device ID (respectively). | ||
** USB serial ports are not supported by coreboot yet. | ** USB serial ports are not supported by coreboot yet. |
Revision as of 17:08, 15 September 2015
Coreboot has various possible consoles:
Output name | direction (from the target coreboot machine point of view) | Requirements | software compatibility (compatibility with software loaded after coreboot, like OS payloads etc...) |
---|---|---|---|
Serial console
(sends coreboot logs over the serial port) |
|
|
|
Console Over EHCI debug port
(sends coreboot logs over the usb debug port) |
|
|
|
Console trough spkmodem
(sends coreboot logs over the sound card) |
|
|
For writting to it from the coreboot target computer:
For reading it from a remote computer:
|
Network console
(sends coreboot logs over the network) |
|
|
For sending the logs:
For receiving the logs:
|
Cbmem console
(Ram buffer, like dmesg) |
|
|
For writting to the buffer which is in the coreboot target computer:
For reading the buffer on the coreboot target computer, after coreboot booted:
|
Other output:
- POST Card
- Tracing the Flash chip's access?