Opened 9 years ago

Last modified 5 years ago

#76 new enhancement

coreboot messages should be accessible in dmesg

Reported by: stepan Owned by: rminnich
Priority: major Milestone:
Component: coreboot Keywords:
Cc: Dependencies:
Patch Status: there is no patch


The LinuxBIOS messages should be written to a log buffer so they can be read from Linux' dmesg command.

Attachments (0)

Change History (6)

comment:1 Changed 8 years ago by uwe

Untested yet by me, but it looks like this is (partly?) implemented in r590.

comment:2 Changed 8 years ago by hailfinger

  • Type changed from defect to enhancement

I implemented the buffer in r590, but the payload has to know a hardcoded buffer address to read the message buffer. There is no explicit mechanism for passing the log buffer address to a payload.

comment:3 Changed 8 years ago by anonymous

No. The code in r590 only creates infrastructure within coreboot. Someone on the uboot mailing list stated that you have to change the linux kernel to know where to look for the buffer (and potentially check the format, not sure). This (at least a pointer to the log) should be passed in the coreboot table.

comment:4 Changed 8 years ago by uwe

  • Summary changed from LinuxBIOS messages should be accessible in dmesg to coreboot messages should be accessible in dmesg

FYI, I'll add a coreinfo module which can display (and scroll through) the coreboot "dmesg buffer" as part of GSoC (if I'll get accepted). Actually, that code is pretty much finished already and works quite nicely (hardcodes the buffer address in RAM though). Will post a patch when GSoC officially started.

I haven't done any work on using it from _Linux_, though.

comment:5 Changed 8 years ago by uwe

Done, that module is in coreinfo now.

comment:6 Changed 5 years ago by uwe

  • Milestone Setting up coreboot v3 deleted

v3 is obsolete, but having the feature in v4 would be great.

Add Comment

Modify Ticket

as new The owner will remain rminnich.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.