Hi,
as you might have noticed, http://www.coreboot.org/Supported_Motherboards looks slightly different from what it looked like yesterday. (and if you didn’t, the old version is still available at http://www.coreboot.org/Supported_Motherboards/old).
The new version looks boring, and one could think there’s no board supported at all in coreboot. Which might in fact be true - what is the most recent commit on coreboot master that was booted on, let’s say, getac/p470?
This is where you come in: The page is generated from data pushed into the board-status repository (no review desired, even though it’s hosted on review.coreboot.org - just push to master). coreboot's util/board_status/ contains the tools to compile that data.
The more often you can show that your system runs a recent coreboot build, the better its support looks like on the page.
The wiki-page generation scripts are in that repository (but will likely move to coreboot’s util/ soon), so if you have proposals on how to improve matter, patches (and later: changesets on gerrit) are welcome!
Patrick
Hi Patrick,
Although I'm not a developer as such, I would like to be able to conribute by using this for the 3 models of Chromebook I have. However, I don't have push rights to the board-status repo (according to the script). Can you sort that out for me?
Thanks,
John.
On 05/12/13 04:43, Patrick Georgi wrote:
Hi,
as you might have noticed, http://www.coreboot.org/Supported_Motherboards looks slightly different from what it looked like yesterday. (and if you didn’t, the old version is still available at http://www.coreboot.org/Supported_Motherboards/old).
The new version looks boring, and one could think there’s no board supported at all in coreboot. Which might in fact be true - what is the most recent commit on coreboot master that was booted on, let’s say, getac/p470?
This is where you come in: The page is generated from data pushed into the board-status repository (no review desired, even though it’s hosted on review.coreboot.org - just push to master). coreboot's util/board_status/ contains the tools to compile that data.
The more often you can show that your system runs a recent coreboot build, the better its support looks like on the page.
The wiki-page generation scripts are in that repository (but will likely move to coreboot’s util/ soon), so if you have proposals on how to improve matter, patches (and later: changesets on gerrit) are welcome!
Patrick
Am 2013-12-06 12:03, schrieb John Lewis:
Although I'm not a developer as such, I would like to be able to conribute by using this for the 3 models of Chromebook I have. However, I don't have push rights to the board-status repo (according to the script). Can you sort that out for me?
Set up an account on Gerrit. See http://www.coreboot.org/Git#Register_with_gerrit for how to do that. That's enough for now. Should we encounter problems (eg. spam), we can still restrict access later.
Patrick
On 06/12/13 11:54, Patrick Georgi wrote:
Am 2013-12-06 12:03, schrieb John Lewis:
Although I'm not a developer as such, I would like to be able to conribute by using this for the 3 models of Chromebook I have. However, I don't have push rights to the board-status repo (according to the script). Can you sort that out for me?
Set up an account on Gerrit. See http://www.coreboot.org/Git#Register_with_gerrit for how to do that. That's enough for now. Should we encounter problems (eg. spam), we can still restrict access later.
I already have an account on review.coreboot.org/Gerrit, and it won't allow me push. This is the output I get:
remote: Resolving deltas: 100% (10/10) remote: Branch refs/heads/master: remote: You are not allowed to perform this operation. remote: To push into this reference you need 'Push' rights. remote: User: jlewis remote: Please read the documentation and contact an administrator remote: if you feel the configuration is incorrect remote: Processing changes: refs: 1, done To ssh://jlewis@review.coreboot.org:29418/board-status ! [remote rejected] master -> master (prohibited by Gerrit) error: failed to push some refs to 'ssh://jlewis@review.coreboot.org:29418/board-status'
So, it seems it's not as unrestricted as you think it is.
John.
Hi,
Thanks, I had something similar in my mind. Would it be possibe to combine the new wiki page with old Board Information page? I mean the detailed page which lists some quirks and todos..http://www.coreboot.org/ASUS_F2A85-M
Thanks Rudolf
Am Samstag, den 07.12.2013, 00:37 +0100 schrieb Rudolf Marek:
Hi,
Thanks, I had something similar in my mind. Would it be possibe to combine the new wiki page with old Board Information page? I mean the detailed page which lists some quirks and todos..http://www.coreboot.org/ASUS_F2A85-M
These pages are still accessible via http://www.coreboot.org/Supported_Motherboards/old
The to-wiki scripts have access to the coreboot tree, so for the vendor/board tuple, they could look up an identifier and create a wiki link from that (instead of the amd/persimmon currently in the page). We'd probably have to clean up the pages' naming scheme, and while at it, we could prefix them into the "Board:" namespace.
Long term, I'd love to autogenerate them from data in the source tree - some yet to invent status.{txt,yaml,whatever that is not xml} in each board's directory.
Patrick
On 12/07/2013 02:26 AM, Patrick Georgi wrote:
Long term, I'd love to autogenerate them from data in the source tree - some yet to invent status.{txt,yaml,whatever that is not xml} in each board's directory.
For that, markdown is very nice. Just put a README.md in the ${maiboard_dir}.
Alex
On Sat, Dec 7, 2013 at 2:31 PM, mrnuke mr.nuke.me@gmail.com wrote:
On 12/07/2013 02:26 AM, Patrick Georgi wrote:
Long term, I'd love to autogenerate them from data in the source tree - some yet to invent status.{txt,yaml,whatever that is not xml} in each board's directory.
For that, markdown is very nice. Just put a README.md in the ${maiboard_dir}.
For any of this, patches, not email messages, are very nice :-)
ron
-
John Lewis -
mrnuke -
Patrick Georgi -
ron minnich -
Rudolf Marek