-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
hi,
https://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html
please do all relevant tests and submit a "coreboot status" report on
asus kgpe-dcma8. you use this board for "critical" applications
relative to your own interests,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
- Forwarded Message
Subject: coreboot is going to make kcma-d8 obsolete
Date: Fri, 6 Apr 2018 22:14:17 +0100
From: Leah Rowe
To: Elijah Smith <9f57e...@openmailbox.org>, coreboot@coreboot.org
isn't git commit history forever?
2018-04-06 18:14 GMT-03:00 Leah Rowe :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> hi,
>
> https://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html
>
> please do all relevant tests and submit a "coreboot status" report
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I might be able to get a report in. Need to pull a machine out of
production though to do it, so it could be a bit (have to wait for a
maintainance window).
On 04/06/2018 04:18 PM, Felipe Sanches wrote:
> isn't git commit history forever?
>
>
On Fri, Apr 6, 2018 at 5:43 PM, Daniel Gröber wrote:
> I'd be happy to upload a board-status report if someone can give me
> (or tell me how to get) commit rights for the appropriate repo. I
> cannot for the life of me figure out what the proper procedure for
> that is just
Like I have said before these types of policies are eventually going to
result in coreboot only having unobtainable development boards in the
tree (that are of course not owner controlled)
It simply isn't right.
How can one learn firmware programming when all the available boards
have hardware
I'd be happy to upload a board-status report if someone can give me
(or tell me how to get) commit rights for the appropriate repo. I
cannot for the life of me figure out what the proper procedure for
that is just from the wiki.
I just recently started playing around with my KCMA-D8 and coreboot,
On Fri, Apr 6, 2018 at 5:45 PM Thierry Laurion
wrote:
> I agree. This is wrong.
> Kgpe-d16 and alike are the last resorts for x86 blob free hardware.
>
> This NEEDS to be kept maintained and upstreamed.
>
>
>
I like the board too. I have one. I have no time to keep it
On Fri, Apr 6, 2018 at 3:40 PM, taii...@gmx.com wrote:
> Like I have said before these types of policies are eventually going to
> result in coreboot only having unobtainable development boards in the
> tree (that are of course not owner controlled)
>
> It simply isn't right.
>
I agree. This is wrong.
Kgpe-d16 and alike are the last resorts for x86 blob free hardware.
This NEEDS to be kept maintained and upstreamed.
Le ven. 6 avr. 2018 18:41, taii...@gmx.com a écrit :
> Like I have said before these types of policies are eventually going to
> result
Am Mi., 4. Apr. 2018 um 18:10 Uhr schrieb Aaron Durbin via coreboot <
coreboot@coreboot.org>:
> > Agree, but coreboot use old commit from edk2. Is it fine to push
> vUDK2018?
>
> I guess? I'm not really sure who uses edk2. I guess tianocore payload?
> Patrick is on holiday right now, but he would
On 04/06/2018 12:20 PM, Patrick Georgi wrote:
> Am Mi., 4. Apr. 2018 um 18:10 Uhr schrieb Aaron Durbin via coreboot
> >:
>
> > Agree, but coreboot use old commit from edk2. Is it fine to push
> vUDK2018?
>
> I guess? I'm not
Hello,
I finally found the time to complete the first draft of my Coreboot x230
How-to.
While I need to fill in some small gaps how to put the hardware parts
together, all the other stuff is covered including extracting Blobs and
vga.rom.
The how-to is located here:
Am Fr., 6. Apr. 2018 um 17:15 Uhr schrieb Piotr Król :
> Can you tell what is this "one system"?
>
Sorry, "any one system" - just the system that the developer who last
touched the payload integration happened to test with.
As said, there's little rigor around the payload
14 matches
Mail list logo