I think that having OEM BIOS logs from supported boards does make a lot of sense, but when I talked to Stefan about it before, he didn't want to add unsupported boards.  His thinking was that we didn't want to be the world's largest lspci database, which seems reasonable to me.  I'd even support submitting them at the same time as the first commit for a mainboard went into gerrit, but I don't think a board should be submitted when there's absolutely nothing in coreboot yet.

I've already put some various logs into the board status tree.  I can post the script that I use to generate these.  It already looks for coreboot vs non-coreboot BIOS to determine which tests to run.
https://review.coreboot.org/gitweb/cgit/board-status.git/tree/gigabyte/ga-b75m-d3h/4.2-619-gd890b45/2015-12-26T19_53_49Z/tests

are you thinking of putting them someplace like an oem_bios_logs directory under the mainboard?
.../tree/gigabyte/ga-b75m-d3h/oem_bios_logs/2015-12-26T19_53_49Z

Martin


On Thu, Mar 17, 2016 at 1:46 PM, Denis 'GNUtoo' Carikli <GNUtoo@no-log.org> wrote:
On Tue, 1 Mar 2016 06:51:37 +0800
persmule <persmule@gmail.com> wrote:
> [dell_e4300_bios_flashrom.log  text/x-log (42687 bytes)]
> [dell_e4300_bios.layout  text/plain (135 bytes)]

Hi,

What do you think about storing devices's log obtained while running the
stock boot firmware somewhere?

Before having laptops supported in coreboot, something like that was
attempted at:
https://www.coreboot.org/Laptop

However having a repository of logs of supported and unsupported devices
would make sense.

The supported devices's log could be used to compare them with the
board-status repository.

Denis.

--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot