Page MenuHomeFreeBSD

release: arm: Add a GENERIC sdcard image
ClosedPublic

Authored by manu on Jul 23 2018, 10:17 PM.

Details

Summary

This produce a generic sdcard image using armv7 GENERIC kernel that
just need some u-boot (or none if the board have u-boot or a SPI flash
for example).

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

We should remove the GUMSTIX image too.

This revision is now accepted and ready to land.Jul 23 2018, 10:21 PM
gjb added a subscriber: gjb.

In the releng side, what is required (both on re@ and end-user point of view) to use the image?

In particular, I'm curious what re@ needs to do specifically to generate GENERICSD images.

In D16410#348607, @gjb wrote:

In the releng side, what is required (both on re@ and end-user point of view) to use the image?

Just install u-boot on the image, I have a script that I need to finish call u-boot-install that will take care of that. (https://gist.github.com/evadot/1bcad7c4c1e5cc7f9a692f4d19ab5421)

In particular, I'm curious what re@ needs to do specifically to generate GENERICSD images.

What do you mean ?

In D16410#348609, @manu wrote:
In D16410#348607, @gjb wrote:

In the releng side, what is required (both on re@ and end-user point of view) to use the image?

Just install u-boot on the image, I have a script that I need to finish call u-boot-install that will take care of that. (https://gist.github.com/evadot/1bcad7c4c1e5cc7f9a692f4d19ab5421)

In particular, I'm curious what re@ needs to do specifically to generate GENERICSD images.

What do you mean ?

For example, the build script wrapper uses a coded list in what kernels to build, which relies on a configuration file existing (see https://svnweb.freebsd.org/base/user/gjb/thermite/builds-12.conf?revision=335326&view=markup for example). Do we just need to add GENERIC64 to the list and create a 12-armv7-GENERIC64-{snap,release}.conf?

In D16410#348610, @gjb wrote:
In D16410#348609, @manu wrote:
In D16410#348607, @gjb wrote:

In the releng side, what is required (both on re@ and end-user point of view) to use the image?

Just install u-boot on the image, I have a script that I need to finish call u-boot-install that will take care of that. (https://gist.github.com/evadot/1bcad7c4c1e5cc7f9a692f4d19ab5421)

In particular, I'm curious what re@ needs to do specifically to generate GENERICSD images.

What do you mean ?

For example, the build script wrapper uses a coded list in what kernels to build, which relies on a configuration file existing (see https://svnweb.freebsd.org/base/user/gjb/thermite/builds-12.conf?revision=335326&view=markup for example). Do we just need to add GENERIC64 to the list and create a 12-armv7-GENERIC64-{snap,release}.conf?

GENERICSD but yes.

In D16410#348611, @manu wrote:

GENERICSD but yes.

Er, yeah, that. Thanks.

This revision was automatically updated to reflect the committed changes.