From: Pavel Shlyak <p.shlyak@pantherx.org>
To: 57070@debbugs.gnu.org
Subject: [bug#57070] [PATCH] bootloader: extlinux: support for optional FDTDIR
Date: Sat, 20 Aug 2022 13:15:38 +0300 [thread overview]
Message-ID: <483BAA4D-ADDE-43C2-B1E3-BADAD7C43E7D@pantherx.org> (raw)
In-Reply-To: <20220809145730.435ef8d0@pantherx.org>
Dear Maxime,
I do not think I can agree that «a relevant code could check what the hardware is» as it’s not hardware-defined, but also user-defined. It’s not just about detection, it’s also about choice. The same system definition I have on RPI4, for example, can boot both with kernel-provided FDT (loaded with uboot) and bootloader-provided FDT (loaded with RPI bootloader). There are also a lot of different devices out there on the market and there’s no common way to know how OS definition is written for it. If you have ideas - you’re welcome to propose your way to do it.
It does not appear to «be simply a kernel bug» to me. Kernel does not pass configuration to the bootloader and we’re configuring a bootloader entry here. It’s simple as that: bootloader entry may include or not include that line and that’s user-defined.
Of course, you’re always welcome to suggest your ideas how the automation you like to have could be implemented. Also, please, keep in mind this change doesn’t change anything on current boards/systems and most users won’t even notice this change is merged.
Sincerely,
Pavel Shlyak
next prev parent reply other threads:[~2022-08-20 10:16 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=483BAA4D-ADDE-43C2-B1E3-BADAD7C43E7D@pantherx.org \
--to=p.shlyak@pantherx.org \
--cc=57070@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.