unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Reza Alizadeh Majd <r.majd@pantherx.org>
To: 57070@debbugs.gnu.org
Subject: [bug#57070] [PATCH] bootloader: extlinux: support for optional FDTDIR
Date: Tue, 9 Aug 2022 14:57:30 +0430	[thread overview]
Message-ID: <20220809145730.435ef8d0@pantherx.org> (raw)

There are situations that u-boot doesn't have to load from the device
tree. some provide the device tree using a vendor bootloader (like what
raspberry-pi does) or with an external bootloader that chainloads the
u-boot (what Asahi does for m1n1 bootloader). 

Unfortunately we couldn't find any reliable document to enforce u-boot
to pass the device tree via `extlinux.conf`, however during our tests,
we found that removing the `FDTDIR` line from the `extlinux.conf` tend
us to do so.

There is also no reliable way to guess if u-boot bootloader should load
device tree or not on a specific hardware. in addition, there are
hardware that can be booted with both firmware device tree on some
kernels and with special device tree on other (modified) kernels. 

so we propose the following patch to define an optional parameter in
`bootloader` record, called `ignore-fdtdir?` which by default is set to
`#f` to keep the current behavior unchanged. if this paramter is set to
`#t`, the `FDTDIR` line will be discarded from the `extlinux.conf` and
u-boot doesn't load the device tree automatically.

This patch was tested on a Raspberry PI and in a VM. It is proven to
preserve the old behavior. We’d love to hear your feedback and hope we
can support more arm hardware in the future.


Regards,
Reza

-- 
Reza Alizadeh Majd
PantherX Team
https://pantherx.org




             reply	other threads:[~2022-08-09 10:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 10:27 Reza Alizadeh Majd [this message]
2022-08-09 10:30 ` [bug#57070] [PATCH] bootloader: extlinux: support for optional FDTDIR 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
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=20220809145730.435ef8d0@pantherx.org \
    --to=r.majd@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 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).