snap-pi:18-armhf

Last commit made on 2022-02-09
Get this branch:
git clone -b 18-armhf https://git.launchpad.net/snap-pi

Branch merges

Branch information

Name:
18-armhf
Repository:
lp:snap-pi

Recent commits

fb9328c... by Dave Jones

Update README with all branches

50414d3... by Łukasz Zemczak

Merge pull request #12 from MirServer/fix-vt

Enable mir-kiosk to start on Ubuntu Core 18/RPi 3

fd40afa... by Dave Jones

Use correct path for armhf kernel's dtbs

The arm64 kernel contains dtbs under an extra "broadcom/" directory,
however the armhf kernel does not. As the "overlays/" sub-directory is
directly under the "dtbs" directory this entry is also redundant in the
armhf gadget definition.

LP: #1907056

9fec912... by Łukasz Zemczak

Merge pull request #71 from snapcore/pidtbs-18-armhf

Backport dtb kernel-assets changes to the UC18 branches.

e452ccb... by Łukasz Zemczak

Backport dtb kernel-assets changes to the UC18 branches.

8dbe7f2... by Alan Griffiths

Merge remote-tracking branch 'upstream/18-armhf' into fix-vt

d837f0c... by Dave Jones

Don't store ethaddr, usbethaddr, or serial# in env

The original uboot environment uses "saveenv" which dumps the *entire*
environment, including values like serial#, ethaddr, and usbethaddr (the
latter two are derived from the former) into the environment. If the SD
card is then switched to another Pi, U-Boot will read those values from
the environment and overwrite the board serial number, and ethernet MAC
address in the device-tree before passing it to the Linux kernel.

This modification introduces an "export_env" value which can be called
(with run) instead of saveenv to export the environment excluding those
values. The list of values exported is in the new "export_vars" value.
This is extensive because the environment is effectively the boot
*script* in addition to the boot *state*. The result has been tested
with armhf and arm64 builds on a 3B+, switching the card to a 3B and
confirming that the MAC address changes.

LP: #1900879

bb3dfaa... by Dave Jones

Reduce CMA in FKMS overlay

Pis with low memory (in particular the 3A+ with 512Mb) cannot boot with
the CMA (contiguous memory area) allocated by the FKMS overlay set to
256Mb (which is also the default). Reducing it to 128Mb permits the
overlay to remain, but also permits the kernel to successfully start on
the 3A+.

e7a4b0a... by Dave Jones

Fix cmdline pointer in config.txt

d81c0d3... by Dave Jones

Use the raspi kernel flavour on everything that's not bionic

This assumes all non-bionic builds will be based on focal (or later)
releases. However, that should be a safe assumption at this point in
time.