Console and outputs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 43: | Line 43: | ||
(Ram buffer, like dmesg) | (Ram buffer, like dmesg) | ||
| | | | ||
* output only | * output only for coreboot. | ||
* input/output for grub. | |||
It requires the computer to be booted to retrive the logs. | |||
| | | | ||
For writting to the buffer which is in the coreboot target computer: | For writting to the buffer which is in the coreboot target computer: |
Revision as of 12:45, 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) |
It requires the computer to be booted to retrive the logs. |
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?