#3206 assigned defect

BSPs Wiki Page is Out of Date

Reported by: Joel Sherrill Owned by:
Priority: normal Milestone: Indefinite
Component: doc Version:
Severity: blocker Keywords: GCI
Cc: Blocked By:
Blocking:

Description

https://devel.rtems.org/wiki/TBR/Website/Board_Support_Packages is linked to from the top of the Wiki and horribly out of date.

I am not sure what to do about this page. We need a master list of BSPs somewhere. It could be updated or we have to find a way to generate an equivalent page. Given this has some historical information, automatically generating it seems hard.

Change History (6)

comment:1 Changed on Oct 25, 2017 at 10:21:24 PM by Chris Johns

Release README.txt files contain a list of BSPs in that release (scroll down). It is generated automatically using the rtems-bsp script when the release is created.

The current definitive BSP definition is the rtems-bsp which learns from the source tree and:

https://git.rtems.org/rtems-tools/tree/tester/rtems/rtems-bsps.ini

For me a BSP only formally exists if it is in the INI files under the rtems-tester.

A list of BSPs is nice, a list based on the Tier structure would be nicer and a list based on the Tier structure with valid test results even better.

My hope is users of RTEMS will put pressure on those providing services to them to get their architecture and BSP moved up the tier ranks by publishing test results on build@rtems.org.

There is also Amar's django website that has support for managing BSPs however that effort needs work to straighten out some schema issues on the relationship of arch, processors and BSP that resulted from Amar and I talking at cross purposes. I am not sure what is involved and how much work is required to make this production quality. I am also not sure how we maintain this data long term if this database become active.

comment:2 Changed on Oct 25, 2017 at 10:25:13 PM by Joel Sherrill

I would be happy to see that page link to a list of BSPs generated for each branch. Not have the table itself.

But every time we branch, we have to add a link. I was hoping to find something that would stay accurate on its own. Generated from code. Perhaps part of the release process to have a file in the release directory? We could back populate that file and link to those.

We don't have tiers for anything beyond the next release. Could we run the script for 4.10 and 4.11 and link to that? From where to where?

comment:3 in reply to:  2 Changed on Oct 25, 2017 at 10:32:42 PM by Chris Johns

Replying to Joel Sherrill:

We don't have tiers for anything beyond the next release. Could we run the script for 4.10 and 4.11 and link to that? From where to where?

You could ./rtems-bsp > rtems-4.11.2.txt for the 4.11 releases and I can update the release procedure to do this automatically and have the README.txt link to it.

For 4.10 I suggest you copy the rtems-bsp to the source tree and run it. In theory you should be able to do this on a number of the older releases.

Your sh foo is better than mine so a compact list of archs before the BSP list might be a nice addition :)

comment:4 Changed on Oct 26, 2017 at 5:40:39 AM by Sebastian Huber

I would move this information together with the BSP READMEs to the RTEMS CPU Architecture Supplement. Then I would delete this wiki page.

comment:5 Changed on Nov 9, 2017 at 6:27:14 AM by Sebastian Huber

Milestone: 4.12.05.1

Milestone renamed

comment:6 Changed on Oct 14, 2018 at 12:59:03 AM by Chris Johns

Keywords: GCI added
Milestone: 5.1Indefinite
Status: newassigned
Version: 5

This would make a good set of GCI tasks.

What happens to BSPs in old releases?

Note: See TracTickets for help on using tickets.