From: Mathieu Othacehe <othacehe@gnu.org>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: 57070@debbugs.gnu.org
Subject: [bug#57070] [PATCH] bootloader: extlinux: support for optional FDTDIR
Date: Thu, 25 Aug 2022 19:35:45 +0200 [thread overview]
Message-ID: <87lerc5iq6.fsf_-_@gnu.org> (raw)
In-Reply-To: <20220816224004.1744c1d5@pantherx.org> (Reza Alizadeh Majd's message of "Tue, 16 Aug 2022 22:40:04 +0430")
Hey,
OK, so I read the long thread. There's still something unclear to me. If
FDTDIR is not passed, where is located the device tree that is loaded?
Directly in the /boot partition?
It looks like the corresponding code is in the label_boot function of
the u-boot/boot/pxe_utils.c file. I quickly read this part hoping to
find a way to define a priority between device trees located in the
FDTDIR directory and device trees installed elsewhere.
> * gnu/bootloader.scm (<bootloader>)[device-tree-support?]: new field.
You need to document this new field in the "Bootloader Configuration"
documentation section.
> * gnu/tests/bootloader.scm: add tests for FDTDIR modification.
This will test for regressions on an x86_64-linux machine that will
probably never use this FDTDIR thing. As those tests are expensive to
run an maintain we can probably remove the test.
Thanks,
Mathieu
next prev parent reply other threads:[~2022-08-25 17:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 10:27 [bug#57070] [PATCH] bootloader: extlinux: support for optional FDTDIR Reza Alizadeh Majd
2022-08-09 10:30 ` Reza Alizadeh Majd
2022-08-15 9:27 ` Mathieu Othacehe
2022-08-16 18:10 ` Reza Alizadeh Majd
2022-08-25 17:35 ` Mathieu Othacehe [this message]
2022-08-28 8:19 ` Reza Alizadeh Majd
2022-08-28 15:49 ` Mathieu Othacehe
2022-08-29 18:17 ` Reza Alizadeh Majd
2022-08-30 6:53 ` bug#57070: " Mathieu Othacehe
2022-08-10 9:31 ` [bug#57070] " Maxime Devos
2022-08-15 10:57 ` Tobias Geerinckx-Rice via Guix-patches via
2022-08-10 9:32 ` Maxime Devos
2022-08-16 17:08 ` Reza Alizadeh Majd
2022-08-16 18:44 ` Maxime Devos
2022-08-10 14:37 ` Pavel Shlyak
2022-08-11 10:00 ` Maxime Devos
2022-08-11 11:13 ` Pavel Shlyak
2022-08-10 14:46 ` Pavel Shlyak
2022-08-20 10:15 ` Pavel Shlyak
2022-08-22 8:54 ` Maxime Devos
2022-08-22 10:52 ` Pavel Shlyak
2022-08-22 18:57 ` Maxime Devos
2022-08-22 19:19 ` Pavel Shlyak
2022-08-22 21:17 ` Maxime Devos
2022-08-22 21:29 ` Pavel Shlyak
2022-08-23 18:11 ` Vagrant Cascadian
2022-08-25 19:16 ` Pavel Shlyak
2022-08-30 6:52 ` Mathieu Othacehe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lerc5iq6.fsf_-_@gnu.org \
--to=othacehe@gnu.org \
--cc=57070@debbugs.gnu.org \
--cc=r.majd@pantherx.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).