I agree with patrick :-)
On Fri, Feb 15, 2019 at 1:38 PM Patrick Georgi wrote:
>
> It's also possible to make Linux (with included ramdisk) into a
> payload, so maybe that could be a middle ground: It's still usable by
> all payloads that can execute payloads, it's still Linux + userland in
> a
It's also possible to make Linux (with included ramdisk) into a
payload, so maybe that could be a middle ground: It's still usable by
all payloads that can execute payloads, it's still Linux + userland in
a more or less normal configuration. It has some overhead, but OTOH
brings the peace of mind
Makes sense. That was one thing that gave me a bit of a gut feeling to do
it in a small linux install than to try to integrate more tightly with the
firmware. The linux utility is what everyone uses and should be more
reliable.
I've been recently burned by that issue too, on proprietary firmware
On Fri, Feb 15, 2019 at 10:19 AM Frederic Dumas
wrote:
>
>
> Thank you, your answer makes the case to be simply closed.
>
Don't give up that quickly :-) It's an old chipset and I you may just need
to checkout coreboot-v1 (aka LinuxBIOS). SiS 635/735/950 were some of the
first chipsets with
Thank you, your answer makes the case to be simply closed.
Not seeing any SiS chipsets on
https://coreboot.org/status/board-status.html or in src/northbrige
or src/southbridge, so unless those are 100% compatible with one of
the others listed I expect you'd be in for a difficult time.
I
Hi,
It seems the Tianocore Coreboot payload
(CorebootPayloadPkg/CorebootModulePkg) will be replaced in future by
UefiPayloadPkg...
See also:
https://firmwaresecurity.com/2018/09/14/uefipayloadpkg-uefi-payload-project-supports-coreboot-and-slim-bootloader/
The preliminary implementation is
6 matches
Mail list logo
