Console and outputs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 57: | Line 57: | ||
| | | | ||
* A ne2k compatible ethernet card. | * A ne2k compatible ethernet card. | ||
| | |||
For sending the logs: | |||
* the linux kernel | |||
|- | |- | ||
! [[Cbmem console]] | ! [[Cbmem console]] | ||
Line 67: | Line 70: | ||
* A coreboot device that supports cbmem: not all devices supports it in coreboot. | * A coreboot device that supports cbmem: not all devices supports it in coreboot. | ||
| | | | ||
For writting to the buffer which is in the coreboot target computer: | For writting to the buffer which is in the coreboot target computer: | ||
* coreboot console output | * coreboot console output |
Revision as of 12:59, 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:
|
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?