>> I think we still need to have a difference between hacky vendor stuff
>> and normal coreboot code. For example, the Eltan mboot stuff is
>> something we didn't really want to have in coreboot in that form, and
>> so they kinda put it in vendorcode as a compromise. We should make
>> sure it
Hi!thishttps://review.coreboot.org/c/coreboot/+/52144resolve the problem, too.Thanks! 07.04.2021, 19:49, "Michael Niewöhner" :Hi,could you test if this one resolves the problem, too,
Hi,
could you test if this one resolves the problem, too, please?
https://review.coreboot.org/c/coreboot/+/52144
Thanks!
Michael
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org
Hi Patrick.
> I'm not sure about Siemens' hwilib: if that's imported, it remains there, if
> this version is written for coreboot, src/drivers/siemens perhaps?
This code is basically a pure software library to access defined fields within
a binary image kept inside CBFS.
Since there is no
Am Mi., 7. Apr. 2021 um 01:12 Uhr schrieb Julius Werner <
jwer...@chromium.org>:
> I think we still need to have a difference between hacky vendor stuff
> and normal coreboot code. For example, the Eltan mboot stuff is
> something we didn't really want to have in coreboot in that form, and
> so
Am Di., 6. Apr. 2021 um 21:21 Uhr schrieb Peter Stuge :
> Patrick Georgi via coreboot wrote:
> > Any objections to moving the code out there that has no other upstream
> > (e.g. src/vendorcode/google/chromeos or src/vendorcode/eltan, I think?)
> > while moving in code from elsewhere in the tree
6 matches
Mail list logo
