Linux kernel mode setting seems to fail to
properly reset the mipi core, causing the
screen to be shifted to the right.

As a work around, we reset the lcdif and
mipi core in a board_quiesce_devices()
function.

GPIO3_20 is the enable for the SN65DSI86,
so power cycling the sdcard would have the
screen turn off.

Modifier keys seem to be broken in boot protocol
of the reform keyboard. But it sends scancodes
for the modifier keys, so just emulate the modifier
key state bits.

Co-authored-by: q66 <daniel@octaforge.org>

Update lpddr4_timing and blobs from upstream

See merge request !7

disable the saveenv command

See merge request !8

set fdtfile environment variable

See merge request !10

 - with our boot.scr this is a no-op because flash-kernel stores a
   symlink from /dtb-5.18.0-4-arm64 to /dtbs/${fk_kvers}/${fdtfile}
 - with extlinux.conf under debian-installer only sets fdtdir to /dtbs/
   and then expects u-boot to read /dtbs/freescale/imx8mq-mnt-reform2.dtb
 - without this patch, u-boot will try reading /dtbs/imx8mq-MNT Reform 2.0.dtb
   which doesn't exist

mntreform-config: set CONFIG_ENV_IS_NOWHERE=y

See merge request !9

This is to avoid that u-boot reads the environment from emmc. This is
another step to make sure that accidentally running "saveenv" doesn't
mess anything up. It also makes sure that a u-boot image flashed to the
SD-Card really provides a pristine environment without external
influence.

Even when u-boot comes from the SD-Card it loads environment variables
from emmc. This means that if somebody accidentally calls "saveenv" with
the wrong environment variables, then there is no easy way to make
u-boot work again and even a freshly flashed SD-Card will fail to work.
If somebody really needs "saveenv" then they can recompile u-boot with
CONFIG_CMD_SAVEENV enabled.

use distro_bootcmd

See merge request !6

 - this partially reverts b3a8287b which prevented BOOTENV as set by
   config_distro_boot.h being appended to CONFIG_EXTRA_ENV_SETTINGS
 - distro_bootcmd can do everything the nested loop can do:
     * boot from usb
     * arbitrary boot order
     * set arbitrary boot partition
     * search arbitrary list of prefixes
     * load a boot.scr
 - in addition to that, distro_bootcmd:
     * is the standard boot mechanism for distros (see doc/README.distro)
     * thus we can replace hard-to-read custom code
     * works with extlinux.conf (needed for debian-installer)

try booting from USB first

See merge request !5

unset devnum so that the loop variable takes precedence

See merge request reform/reform-boundary-uboot!4

use prefix as loop variable so that it can be reused in boot.scr

See merge request !3

boot using boot.scr

See merge request !2