Opened on 06/26/18 at 09:18:32
Last modified on 01/10/19 at 07:03:50
#3464 assigned task
Move all BSP documentation to the User Manual
Reported by: | Sebastian Huber | Owned by: | Sebastian Huber |
---|---|---|---|
Priority: | normal | Milestone: | Indefinite |
Component: | bsps | Version: | |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
Gather all the information from READMEs, wiki pages, blogs, etc. for each BSP and add it to the User Manual.
Change History (5)
comment:1 Changed on 06/26/18 at 09:20:46 by Sebastian Huber
Owner: | set to Sebastian Huber |
---|---|
Status: | new → assigned |
comment:2 Changed on 06/29/18 at 08:16:25 by Sebastian Huber <sebastian.huber@…>
comment:3 Changed on 01/09/19 at 13:01:53 by Sebastian Huber <sebastian.huber@…>
comment:4 Changed on 01/09/19 at 16:13:35 by Joel Sherrill
How many BSPs have useful content in the wiki? A review of that like I did the SW Eng Handbook for GCI tasks would at least note which BSPs have some existing content to convert and build from. The goal (like with the Handbook) would be to purge this content from the Wiki after it is converted and reviewed.
Just adding URLs into the empty outline would at least be a work plan.
comment:5 Changed on 01/10/19 at 07:03:50 by Sebastian Huber
Some information is also in README files.
Note: See
TracTickets for help on using
tickets.
In 2c2c6cc/rtems-docs: