I think we are also seeing this issue after downstreaming:
https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/1637073
+Matt Delco posted some comments on this CL.
On Tue, Jun 4, 2019 at 1:11 PM Martin Kepplinger wrote:
> Hi,
>
> Just tested a build using this config:
Hi,
Just tested a build using this config:
https://github.com/merge/skulls/blob/master/x230/nonfree-defconfig-139b3cef03
with a recent coreboot (my master branch HEAD is at 0da3a8a91b
soc/intel/baytrail: set default VBIOS filename and PCI ID)
When selecting "3" or "4" for the secondary
-- Forwarded message -
From: Matt B
Date: Mon, Jun 3, 2019 at 7:19 PM
Subject: Re: [coreboot] Re: Starting the coreboot 4.10 release process
To: Mike Banon
On a side note, when more than one option is possible, it's good to know
which the tester used.
Hypothetical example: did
Okay, I returned your boards but added a note that "no board_status
report yet". Hopefully you could submit them in the near future, at
least for the archival purposes. And there's a similar question to
someone else who added "Asus P8H61-M Pro" despite that the latest
report for it is one year
I added those devices, all of which I have in my possession and were tested
over the weekend with TOT. I'd not yet had a chance to upload board status
for them, but figured knowing a good range of platforms/boards were known
working just prior to release was useful (and the purpose of the list)
On Mon, Jun 3, 2019 at 8:55 AM Mike Banon wrote:
> If the upstream edk2 is so bad - have you tried to upstream your set
> of patches? It is good that your personal fork/repo is stable, but
> inevitably it will always lag behind the upstream, not benefiting from
> some new features and bugfixes.
On 03.06.19 16:13, Mike Banon wrote:
Just noticed that someone included i.e. some Purism Librem devices to
a " Recently tested mainboards: " section - but, when I check
https://review.coreboot.org/cgit/board-status.git/log/purism , the
latest board status for Purism happened even before 4.9 !
Thank you very much, Evgeny, and luckily I could see your additions
here: https://piratenpad.de/p/coreboot4.10-release-checklist
( https://review.coreboot.org/cgit/board-status.git/log/ - Lenovo T420
, Lenovo X200 , Lenovo X220 , Lenovo T530 baseboard )
On Sun, Jun 2, 2019 at 11:12 PM Evgeny
Just noticed that someone included i.e. some Purism Librem devices to
a " Recently tested mainboards: " section - but, when I check
https://review.coreboot.org/cgit/board-status.git/log/purism , the
latest board status for Purism happened even before 4.9 ! And without
a recent enough _public_
If the upstream edk2 is so bad - have you tried to upstream your set
of patches? It is good that your personal fork/repo is stable, but
inevitably it will always lag behind the upstream, not benefiting from
some new features and bugfixes. Same reason why I didn't want to fork
a coreboot despite
Maybe related to this:
when compiling with "check PIRQ table consitency" i get following warnings:
ACPI Warning: NsLookup: Type mismatch on PRQI (RegionField), searching
for (Region) (20190509/nsaccess-730)
ACPI Warning: NsLookup: Type mismatch on SIOI (RegionField), searching
for (Region)
11 matches
Mail list logo
