Re: [coreboot] How is depreciating 95% of coreboot boards worth it for such minor improvements?
On Wed, Aug 23, 2017 at 09:44:30PM +0000, ron minnich wrote:
On Wed, Aug 23, 2017 at 2:31 PM Taiidan@gmx.com Taiidan@gmx.com wrote:
Ah I see thanks for explaining.
I had read all the AGESA boards were going to be removed, besides the asus D8/D16 those are the last and best owner controlled x86 boards. Is there a current list of boards to be removed?
I don't know, but I have brought this up from time to time. I believe that if they've not got a maintainer for more than a year it is time for them to be removed.
I think we should also take board_status[1] into account here. If a board has recently (for some value of "recently") been successfully booted into linux, the support can't be completely broken.
I would like to have a list of all boards ever supported, along with the last coreboot revision where they can be found.
There is such a page in the wiki[2]. It's probably incomplete. It doesn't list commits, either.
We could migrate it into git, maybe, and make it a requirement that every commit that deletes a board updates the list.
Jonathan
[1]: https://www.coreboot.org/Supported_Motherboards [2]: https://www.coreboot.org/Graveyard
Jonathan Neuschäfer wrote:
I would like to have a list of all boards ever supported, along with the last coreboot revision where they can be found.
There is such a page in the wiki[2]. It's probably incomplete. It doesn't list commits, either.
We could migrate it into git, maybe, and make it a requirement that every commit that deletes a board updates the list.
If an automaton can check commits and detect a board being deleted then I think it should directly publish information to the web, instead of forcing a human to perform redundant work.
//Peter
Hello everyone,
A year ago I ported coreboot to the motherboard (MSI MS7721) that I use in my main PC. In my opinion removing support for boards that are actively used by people in this community would be a setback for the project as a whole.
While I currently don't have the time and knowledge to port my board away from Agesa I can test builds for anyone who wants me to.
Another thing: I don't understand the workflow for putting my boardstatus on the wiki yet. Could someone explain to me how I can publish on the wiki that my board works with a certain version of Coreboot? Also: how can I add a wiki page for my board?
Greetings, Renze Nicolai
On Wed, 2017-08-23 at 22:18 +0000, Peter Stuge wrote:
Jonathan Neuschäfer wrote:
I would like to have a list of all boards ever supported, along with the last coreboot revision where they can be found.
There is such a page in the wiki[2]. It's probably incomplete. It doesn't list commits, either.
We could migrate it into git, maybe, and make it a requirement that every commit that deletes a board updates the list.
If an automaton can check commits and detect a board being deleted then I think it should directly publish information to the web, instead of forcing a human to perform redundant work.
//Peter
On Thu, Aug 24, 2017 at 11:12 AM, Renze Nicolai renze@rnplus.nl wrote:
Another thing: I don't understand the workflow for putting my boardstatus on the wiki yet. Could someone explain to me how I can publish on the wiki that my board works with a certain version of Coreboot? Also: how can I add a wiki page for my board?
Good point - Documentation is a problem here. There's a README in the board_status directory, but it's pretty brief. We expect users to use board_status but fail to document it well. I'll see what I can do to improve this in coming days...
FWIW, the script was originally made for gathering info on a remote host via SSH or serial since that's what Martin and I were doing at the time when we hacked it up. But some people do coreboot development and testing on the same machine which makes board_status usage awkward.
On Wed, Aug 23, 2017 at 3:10 PM, Jonathan Neuschäfer j.neuschaefer@gmx.net wrote:
On Wed, Aug 23, 2017 at 09:44:30PM +0000, ron minnich wrote:
On Wed, Aug 23, 2017 at 2:31 PM Taiidan@gmx.com Taiidan@gmx.com wrote:
Ah I see thanks for explaining.
I had read all the AGESA boards were going to be removed, besides the asus D8/D16 those are the last and best owner controlled x86 boards. Is there a current list of boards to be removed?
I don't know, but I have brought this up from time to time. I believe
that
if they've not got a maintainer for more than a year it is time for them
to
be removed.
I think we should also take board_status[1] into account here. If a board has recently (for some value of "recently") been successfully booted into linux, the support can't be completely broken.
Correct, and going back thru Martin's blog (https://blogs.coreboot.org/ blog/author/martinroth/) that was the intention: *To further clean things up, starting with the 4.8 release, any platform that does not have a successful boot logged in the board_status repo in the previous year (that is, within the previous two releases) will be removed from the maintained coreboot codebase.*
Did that policy stuff ever get written up on a wiki page or somewhere more easily searchable?
I would like to have a list of all boards ever supported, along
with the last coreboot revision where they can be found.
There is such a page in the wiki[2]. It's probably incomplete. It doesn't list commits, either.
We could migrate it into git, maybe, and make it a requirement that every commit that deletes a board updates the list.
+1 to what Peter said - This feels like it could/should be scripted, run periodically, and used to generate a wiki page. Now if only someone had a few spare cycles to do it...
-
David Hendricks -
Jonathan Neuschäfer -
Peter Stuge -
Renze Nicolai