Console and outputs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 80: | Line 80: | ||
* grub with the cbmemc command | * grub with the cbmemc command | ||
* coreboot's userspace cbmem -c uttility | * coreboot's userspace cbmem -c uttility | ||
|- | |||
|- | |||
! [[Developer Manual/Tools#POST card|POST Card]] | |||
| | |||
* output only. | |||
| | |||
| N/A | |||
|- | |- | ||
|} | |} | ||
Other output: | Other output: | ||
* Tracing the Flash chip's access? | * Tracing the Flash chip's access? |
Revision as of 13:06, 13 March 2016
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:
|
POST Card |
|
N/A |
Other output:
- Tracing the Flash chip's access?