Console and outputs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 23: | Line 23: | ||
* input? | * input? | ||
* output | * output | ||
| | |||
* grub | |||
* linux kernel in its early initialisation (I'm not sure that it can be kept afterward, because, after the early initialisation, by default it tries to initialise the USB port normally) | |||
|- | |- | ||
! [[Spkmodem| Console trough spkmodem]] | ! [[Spkmodem| Console trough spkmodem]] |
Revision as of 12:47, 15 December 2013
Coreboot has various possible consoles:
Output name | direction (from the target coreboot machine point of view) | 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) |
| |
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?