Console and outputs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 51: | Line 51: | ||
|- | |- | ||
! [[Network console]] | ! [[Network console]] | ||
(sends coreboot logs over the network) | |||
| | | | ||
* output | * output | ||
* probably no input | * probably no input | ||
| | | | ||
* A ne2k compatible ethernet card. | * A ne2k compatible ethernet card. | ||
Line 60: | Line 60: | ||
For sending the logs: | For sending the logs: | ||
* the linux kernel | * the linux kernel | ||
For receiving the logs: | |||
* nc and similar networking uttilities. | |||
|- | |- | ||
! [[Cbmem console]] | ! [[Cbmem console]] |
Revision as of 13:00, 15 December 2013
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?