>
> Please see the developer documentation:
>
I am afraid this documentation does not answer why this build problem
does not happen when I apply this patch to the standalone cloned seabios
while it does happens when I apply it to the seabios built by a coreboot
Best regards,
Mike
On Sun, Feb
On Sun, Feb 25, 2018 at 03:05:06AM +0300, Mike Banon wrote:
> Friends, I need your help. While trying to improve SeaBIOS I got stuck
> at this very strange problem - which does not appear when you do a
> standalone build of SeaBIOS but it happens when you try building a
> coreboot together with
On 25.02.2018 09:23, Mike Banon wrote:
> just upgrade your git? 1.9.1 is a little bit old
You probably mean, "just" upgrade every git of every system that is used
for coreboot development. Ubuntu 14.04 (which is still maintained btw.)
might not be the only active distribution with an old git
"varverify32init.patch" in the attachments. To apply a patch please copy it
to the coreboot directory, "cd" to coreboot, and - if seabios is already cloned
(e.g. after building a coreboot once, followed by a "make clean" of course)
run " patch -l -p1 < varverify32init.patch "
Sorry, my previous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/2018 02:18 AM, Mike Banon wrote:
>> Any particular reason those patches were not upstreamed?
>
> Because a person who submitted these patches did not fix some problems,
I'm aware of this. Upstreaming was never part of the original funding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually that's quite odd -- it should not work that way. There is a
hardware mux that is switched in when the module is installed; only the
BMC can access the DRAM SPD lines without a BMC GPIO being set.
Which module are you using, the iKVM4 or the
Strange, I didn't apply any patches. I run D16 with stock coreboot 4.7 and
OpenBMC.
Could it be because I have different memory modules (4xKVR16R11D4/16)?
On 18-02-24 12:00:01, coreboot-requ...@coreboot.org wrote:
Send coreboot mailing list submissions to
coreboot@coreboot.org
To
just upgrade your git? 1.9.1 is a little bit old
Although I am unsure if there is anything newer for ubuntu 14.04
since it is very outdated and everyone switched to 16.04 LTS or later.
Maybe you would have to compile a new git from source if you don't
want / can't reinstall OS
On Sat, Feb 24,
> Any particular reason those patches were not upstreamed?
Because a person who submitted these patches did not fix some problems,
if you scroll down to comments at
https://review.coreboot.org/#/c/coreboot/+/19820/
Paul Menzel
May 23, 2017
Patch Set 1:
(2 comments)
9 matches
Mail list logo
