Differential D19380

build SD images for boards
Needs ReviewPublic
Actions

Authored by shigeru_os-hackers.jp on Feb 27 2019, 11:01 AM.

Details

Reviewers

rgrimes

Summary

Merge branch 'master' into patch/shigeru_work/release_embedded_boards

add builddate and revison to SD image file name

Merge branch 'master' into patch/shigeru_work/release_embedded_boards

build SD images for boards
add builddate and revison to SD image file name

Test Plan

We do need to figure out how to test this.

Diff Detail

Lint

Lint Passed

Unit

No Test Coverage

Build Status

Buildable 22770
Build 21862: arc lint + arc unit

Event Timeline

shigeru_os-hackers.jp created this revision.Feb 27 2019, 11:01 AM

Herald added subscribers: emaste, andrew. · View Herald TranscriptFeb 27 2019, 11:01 AM

Harbormaster completed remote builds in B22770: Diff 54466.Feb 27 2019, 11:01 AM

I don't think this is a good approach.
My goal for this is :

Finish u-boot-install (https://gist.github.com/evadot/1bcad7c4c1e5cc7f9a692f4d19ab5421) to handle multi file u-boot
Do a rpi-fw-install script and include it in the rpi-firmware package
Create to GENERICSD image for arm64 (like the armv7 one), one with MBR and one with GPT scheme.
Remove board configs that have no quirks from release.
re@ could then create only two images (GENERICSD-MBR, GENERICSD-GPT) and install u-boot on each one based on list somewhere.

linimon added a subscriber: linimon.Feb 27 2019, 5:52 PM

rgrimes edited the test plan for this revision. (Show Details)Feb 27 2019, 7:25 PM

rgrimes added a reviewer: rgrimes.

In D19380#414840, @manu wrote:

I don't think this is a good approach.
My goal for this is :

Finish u-boot-install (https://gist.github.com/evadot/1bcad7c4c1e5cc7f9a692f4d19ab5421) to handle multi file u-boot

Do a rpi-fw-install script and include it in the rpi-firmware package

Create to GENERICSD image for arm64 (like the armv7 one), one with MBR and one with GPT scheme.

Remove board configs that have no quirks from release.

re@ could then create only two images (GENERICSD-MBR, GENERICSD-GPT) and install u-boot on each one based on list somewhere.

If you have work going on to facilitate this much simpler approach that is wonderful.

I discuss a plan with manu (Emmanuel) at AsiaBSDCon 2019.

create generic image without board dependent codes
- create GENERICSD-MBR
add new stage to add board dependent codes for each boards
- I think need a new function to install board dependent codes
  - copy GENERICSD-MBR to BOARDIMAGE
  - install board dependent codes to BOARDIMAGE

Now I try to rewrite new code.
I need more time.
Please wait.