-----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?
2018-04-06 18:14 GMT-03:00 Leah Rowe <info@gluglug.org.uk mailto:info@gluglug.org.uk>:
hi,
https://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html 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, e.d.ghttps://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html http://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html . asus kgpe dpge-d16 d16
coreboot has a policy of deleting source code (read: maintenance) of "unmaintained" boards). please test coreboot (per coreboot policies) on this board, and submit "board status" information, so that the asus kcma-d8 source code isn't (literally. please read that literally) deleted from coreboot.bit
(by extension, this applies to ASUS KGPE D16)
Don't blame me for coreboot's shortsightedness on this matter. I simply wish for coreboot.git to continue remaining official maintenance of what remains of the maintenance of libre-friendly hardware, within the coreboot project)
- -- coreboot mailing list: coreboot@coreboot.org mailto:coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot https://mail.coreboot.org/mailman/listinfo/coreboot
- -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com
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 initiated via binary blobs? This is what the standards create.
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, Taiidan@gmx.com Taiidan@gmx.com a écrit :
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 initiated via binary blobs? This is what the standards create. -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
On Fri, Apr 6, 2018 at 3:40 PM, Taiidan@gmx.com Taiidan@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.
Indeed, this isn't right (as in correct) so don't spread this FUD. The boards are still in the tree, you just need to check out whatever coreboot version is known to actually work with the board. For example if a board was last reported working in coreboot-4.6, then `git checkout 4.6` or checkout a specific hash reported on the board_status repo.
It does no good for users to have hundreds of boards in master that fail to boot, and no good for developers who need to maintain and refactor code for boards that nobody tests and have been abandoned.
There's obviously a few people on this list using the Asus boards mentioned which is great. The issue we need to solve is getting more people to submit test results so that this isn't a problem in the future.
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, so I still got it right here on my desk :)
--Daniel
On Fri, Apr 06, 2018 at 04:44:35PM -0500, Timothy Pearson wrote:
-----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?
2018-04-06 18:14 GMT-03:00 Leah Rowe <info@gluglug.org.uk mailto:info@gluglug.org.uk>:
hi,
https://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html 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, e.d.ghttps://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html http://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html . asus kgpe dpge-d16 d16
coreboot has a policy of deleting source code (read: maintenance) of "unmaintained" boards). please test coreboot (per coreboot policies) on this board, and submit "board status" information, so that the asus kcma-d8 source code isn't (literally. please read that literally) deleted from coreboot.bit
(by extension, this applies to ASUS KGPE D16)
Don't blame me for coreboot's shortsightedness on this matter. I simply wish for coreboot.git to continue remaining official maintenance of what remains of the maintenance of libre-friendly hardware, within the coreboot project)
coreboot mailing list: coreboot@coreboot.org mailto:coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot https://mail.coreboot.org/mailman/listinfo/coreboot
Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBAgAGBQJax+pAAAoJEK+E3vEXDOFbw4wIAKzCnhL5gO2CZQXzOMoEv8ft 94pMK5yBQvZZsgBvvWlE2AVHPDK0CWJlyji1e7qgHn8k0IDQRcHaCLWU6sQL+nFO DgRk00Kd503eOqV7Pf+vBs9WuxAmZSVvNMzFqjLJWiq+rcD/6rd9c8VFAcciVhop /0Cz3wa5aIDAhzlkFT9IV25DAkyjtEVpFKeBXJsKvubGuPGCQLGsquvNgqoWDWGO 7KgRSDYRHtkCmsAdZoTnVZYhSHDE/LOGct2HRx2yKtjeOfKuWgIJ3ra9/UOOvqIe 4shxpGhmJz6twXgHtIRM0zK0x9n6dEiOnD2/uROmjc67BuU6CG30hDkhyg15U3E= =k/Nm -----END PGP SIGNATURE-----
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
On Fri, Apr 6, 2018 at 5:43 PM, Daniel Gröber dxld@darkboxed.org 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 from the wiki.
I just recently started playing around with my KCMA-D8 and coreboot, so I still got it right here on my desk :)
Hi Daniel, Thanks for volunteering!
Which wiki? For commit rights, have you tried https://www.coreboot.org/Git#Register_with_gerrit ? I just updated the board status wiki to hopefully make that step easier to follow.
Please let us know where you get stuck. Many of us set up our accounts years ago and the documentation may be stale or non-obvious to newcomers, so a fresh perspective is welcome.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 07/04/18 01:43, 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 from the wiki.
I just recently started playing around with my KCMA-D8 and coreboot, so I still got it right here on my desk :)
--Daniel
Thank you Daniel.
if anyone can test D16 too, that'd be great.
I'll be really upset if D8/D16, or any libreboot-supported hardware, is removed from coreboot.git.
- -- Leah Rowe
Libreboot developer and project founder.
Use free software. Free as in freedom. https://www.gnu.org/philosophy/free-sw.html
Use a free BIOS - https://libreboot.org/ Use a free operating system, GNU+Linux.
Support computer user freedom https://sfconservancy.org/ https://fsf.org/ - https://gnu.org/
Minifree Ltd, trading as Ministry of Freedom | Registered in England, No. 9361826 | VAT No. GB202190462 Registered Office: 19 Hilton Road, Canvey Island, Essex SS8 9QA, UK | Web: https://minifree.org/
Leah Rowe wrote:
I'll be really upset if D8/D16, or any libreboot-supported hardware, is removed from coreboot.git.
It's straightforward for you to avoid that: Contribute board status information.
Open source only works reliably for me when I accept that I am responsible for my own needs.
Unfortunately, what that means gets underestimated quite often, by newcomers and experienced experts alike, and many organizations already got really upset when they couldn't merely consume open source.
Please stay proactive to avoid such problems; at a minimum they cause undue stress both for you and for communities which don't work exactly as you would like.
Thanks a lot and take care
//Peter
On Sat, Apr 7, 2018 at 2:54 AM Leah Rowe info@gluglug.org.uk wrote:
I'll be really upset if D8/D16, or any libreboot-supported hardware, is removed from coreboot.git.
and as David has pointed, it never is or will be. It's always there. I don't understand your point here. LinuxBIOS V1 is in git, and everything in between. So why do you say that things are being "removed"?
-
Daniel Gröber -
David Hendricks -
Leah Rowe -
Peter Stuge -
ron minnich -
Taiidan＠gmx.com -
Thierry Laurion -
Timothy Pearson