From: Vagrant Cascadian <vagrant@debian.org>
To: Patrick Wildt <patrick@blueri.se>, Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>
Cc: u-boot@lists.denx.de, "Lukas F. Hartmann" <lukas@mntre.com>,
Heiko Thiery <heiko.thiery@gmail.com>
Subject: Re: [PATCH v3 2/2] board: mntre: imx8mq: Add MNT Reform 2 board support
Date: Sat, 18 Dec 2021 17:26:03 -0800 [thread overview]
Message-ID: <87y24hwfkk.fsf@ponder> (raw)
In-Reply-To: <Ybj1JcC6kB9bpdIb@ryzen.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]
On 2021-12-14, Patrick Wildt wrote:
> The MNT Reform 2 is a modular DIY laptop. In its initial version it
> is based on the BoundaryDevices i.MX8MQ SoM. Some parts have been
> lifted from BoundaryDevices official U-Boot downstream project.
Successfully loaded u-boot, loaded a kernel and .dtb, thanks!
Tested-By: Vagrant Cascadian <vagrant@debian.org>
This may not be specific to this patch series, but one problem I had
during build is that it doesn't appear to respect the BL31 environment
variable that many other platforms support to specify the path to the
ATF firmware; is there a way to add that with binman?
Similarly, it would be ideal to have environment variables for the other
various firmware (lpddr*.bin, signed-hdmi*.bin) needed to build. The
Debian u-boot packages build all boards from a single source, and
copying *.bin into the top-level directory for each one at the right
time seems trickier than telling each build target where the firmware is
via environment variables.
A couple relatively small things in the patch itself:
> diff --git a/include/configs/imx8mq_reform2.h b/include/configs/imx8mq_reform2.h
> new file mode 100644
> index 0000000000..8aed1acfcf
> --- /dev/null
> +++ b/include/configs/imx8mq_reform2.h
...
> +#define CONFIG_EXTRA_ENV_SETTINGS \
> + BOOTENV \
> + "scriptaddr=" __stringify(CONFIG_SYS_LOAD_ADDR) "\0" \
> + "kernel_addr_r=" __stringify(CONFIG_SYS_LOAD_ADDR) "\0" \
> + "image=Image\0" \
> + "console=ttymxc0,115200\0" \
> + "fdt_addr_r=0x43000000\0" \
This should have ramdisk_addr_r, maybe:
"ramdisk_addr_r=0x44000000\0"
Maybe 0x4400000 is a bit overkill, but anything that that starts
sufficiently after fdt_addr_r to leave room for the .dtb file.
This is needed to support distro_bootcmd functionality (boot scripts,
extlinux.conf support, etc.) where an initrd/initramfs should be an
available option.
> + "boot_fdt=try\0" \
> + "fdtfile=" CONFIG_DEFAULT_FDT_FILE "\0" \
This should be something like:
"fdtfile=freescale/" CONFIG_DEFAULT_FDT_FILE "\0" \
Or maybe CONFIG_DEFAULT_FDT_FILE should have the vendor directory
prepended in configs/imx8mq_reform2_defconfig? Not sure which is more
correct, but the boot environment should have the vendor directory
included in fdtfile one way or another.
Thanks again, it is very nice to be able to build my own bootloader. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2021-12-19 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 19:47 [PATCH v3 0/2] Add MNT Reform 2 board support Patrick Wildt
2021-12-14 19:48 ` [PATCH v3 1/2] arm: dts: imx8mq: add MNT Reform 2 Patrick Wildt
2021-12-14 19:48 ` [PATCH v3 2/2] board: mntre: imx8mq: Add MNT Reform 2 board support Patrick Wildt
2021-12-19 1:26 ` Vagrant Cascadian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y24hwfkk.fsf@ponder \
--to=vagrant@debian.org \
--cc=festevam@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=lukas@mntre.com \
--cc=patrick@blueri.se \
--cc=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox