Page MenuHomeFreeBSD

build SD images for boards
Needs ReviewPublic

Authored by shigeru_os-hackers.jp on Feb 27 2019, 11:01 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 20 2023, 3:08 AM
Unknown Object (File)
Nov 25 2023, 9:55 PM
Unknown Object (File)
Nov 22 2023, 10:03 PM
Unknown Object (File)
Nov 22 2023, 10:01 PM
Unknown Object (File)
Nov 22 2023, 9:40 PM
Unknown Object (File)
Nov 13 2023, 1:29 PM
Unknown Object (File)
Nov 13 2023, 1:13 PM
Unknown Object (File)
Sep 2 2023, 7:51 PM

Details

Reviewers
rgrimes
Summary

Merge branch 'master' into patch/shigeru_work/release_embedded_boards

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

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.
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.