Re: [coreboot] coreboot ported to the ASUS KGPE-D16 (Libreboot: blobless, fully functional!)

2015-05-04 Thread Patrick Georgi via coreboot
2015-05-03 23:12 GMT+02:00 Emilian Bold : > I'm curious, is there some Coreboot Foundation that would gather this money > and purchase the copyright or would Raptor just somehow crowd-fund this > money to license their work as GPLv2 while keeping the copyright? With coreboot there's no organization

[coreboot] REACTS: Also upload failed logs to board status (was: QEMU x86_64 Q35 Automated Test Failure)

2015-05-04 Thread Paul Menzel
Dear coreboot folks, Am Montag, den 04.05.2015, 23:47 -0500 schrieb REACTS: > The QEMU x86_64 Q35 fails verification as of commit > 8ccdeaeb207031eea3881511acfaf3e949678f74 > > The following tests failed: > CBMEM_TIMESTAMP_ACCESS_FAILURE > CBMEM_OBJECT_TABLE_TRUNCATED > > Commits since last s

Re: [coreboot] ASUS KFSN4-DRE Automated Test Failure

2015-05-04 Thread Timothy Pearson
On 05/04/2015 11:55 PM, Raptor Engineering Automated Test Stand wrote: The ASUS KFSN4-DRE fails verification as of commit 8ccdeaeb207031eea3881511acfaf3e949678f74 The following tests failed: BOOT_FAILURE Commits since last successful test: 8ccdeae haswell: Link stage_cache_external_region into

[coreboot] ASUS KFSN4-DRE Automated Test Failure

2015-05-04 Thread Raptor Engineering Automated Test Stand
The ASUS KFSN4-DRE fails verification as of commit 8ccdeaeb207031eea3881511acfaf3e949678f74 The following tests failed: BOOT_FAILURE Commits since last successful test: 8ccdeae haswell: Link stage_cache_external_region into ramstage, too 634899c resource: Adjust memory resources high earlier e6a

[coreboot] QEMU x86_64 Q35 Automated Test Failure

2015-05-04 Thread Raptor Engineering Automated Test Stand
The QEMU x86_64 Q35 fails verification as of commit 8ccdeaeb207031eea3881511acfaf3e949678f74 The following tests failed: CBMEM_TIMESTAMP_ACCESS_FAILURE CBMEM_OBJECT_TABLE_TRUNCATED Commits since last successful test: 8ccdeae haswell: Link stage_cache_external_region into ramstage, too 634899c re

Re: [coreboot] cmos.layout: power_on_after_fail

2015-05-04 Thread Marc Jones
Iru, It is powering on if it thinks that the normal shutdown failed. You can change the default for your build and/or check if there is a logic bug. Also check that the option is correctly cleared on S5. Finally, details of your board and chipset would be good to mention. Marc On Mon, May 4, 20

Re: [coreboot] QEMU x86_64 Q35 Automated Test Failure

2015-05-04 Thread Timothy Pearson
On 05/04/2015 10:08 PM, Raptor Engineering Automated Test Stand wrote: The QEMU x86_64 Q35 fails verification as of commit 8ccdeaeb207031eea3881511acfaf3e949678f74 The following tests failed: BOOT_FAILURE Commits since last successful test: 8ccdeae haswell: Link stage_cache_external_region int

[coreboot] QEMU x86_64 Q35 Automated Test Failure

2015-05-04 Thread Raptor Engineering Automated Test Stand
The QEMU x86_64 Q35 fails verification as of commit 8ccdeaeb207031eea3881511acfaf3e949678f74 The following tests failed: BOOT_FAILURE Commits since last successful test: 8ccdeae haswell: Link stage_cache_external_region into ramstage, too 634899c resource: Adjust memory resources high earlier e6

Re: [coreboot] cmos.layout: power_on_after_fail

2015-05-04 Thread ron minnich
The original use of power_on_after_fail was for HPC server nodes that we wanted to power on after an external power failure without having to go to 1024 nodes and touch a button (this was a real issue at Los Alamos and IIRC the fix came from Linux NetworX). This is LONG before laptops were a gleam