mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Marco Felsch <m.felsch@pengutronix.de>,
	Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH v2 5/5] Documentation: migration-2025.07.0: document CONFIG_DEEP_PROBE_DEFAULT
Date: Mon,  2 Jun 2025 11:57:38 +0200	[thread overview]
Message-ID: <20250602095738.822334-5-a.fatoum@barebox.org> (raw)
In-Reply-To: <20250602095738.822334-1-a.fatoum@barebox.org>

Out of tree boards will get a warning on startup now asking them to
explicitly opt-in or opt-out to deep probe. Document this.

Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
v1 -> v2:
  - Collected Marco's R-b
---
 Documentation/migration-guides/migration-2025.07.0.rst | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/Documentation/migration-guides/migration-2025.07.0.rst b/Documentation/migration-guides/migration-2025.07.0.rst
index 896d2552e9ea..fe47c3109745 100644
--- a/Documentation/migration-guides/migration-2025.07.0.rst
+++ b/Documentation/migration-guides/migration-2025.07.0.rst
@@ -7,3 +7,13 @@ Configuration options
 * The legacy ARM 32-bit ATAGS mechanism is now disabled by default.
   It can be re-enabled using the newly added ``CONFIG_BOOT_ATAGS`` option.
   Use of ATAGS is deprecated. Users should migrate to OpenFirmware device trees.
+
+Board support
+-------------
+
+* barebox now warns at runtime about boards that disable the option
+  ``CONFIG_DEEP_PROBE_DEFAULT`` and list neither the ``barebox,deep-probe``
+  nor ``barebox,disable-deep-probe`` property in the top-level device tree node.
+  It's recommended that all boards switch to deep probe.
+  If deep probe breaks your platform, please report to the mailing list
+  and set ``barebox,disable-deep-probe`` in your device tree.
-- 
2.39.5




  parent reply	other threads:[~2025-06-02  9:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02  9:57 [PATCH v2 1/5] common: deep-probe: inform only about lack of deep-probe support Ahmad Fatoum
2025-06-02  9:57 ` [PATCH v2 2/5] common: deep-probe: support specifying support in DT Ahmad Fatoum
2025-06-02 10:09   ` Marco Felsch
2025-06-02  9:57 ` [PATCH v2 3/5] treewide: dts: describe deep probe support in device tree Ahmad Fatoum
2025-06-02  9:57 ` [PATCH v2 4/5] ARM: configs: enable deep probe for the most popular configs Ahmad Fatoum
2025-06-02  9:57 ` Ahmad Fatoum [this message]
2025-06-02 10:16 ` [PATCH v2 1/5] common: deep-probe: inform only about lack of deep-probe support Sascha Hauer

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=20250602095738.822334-5-a.fatoum@barebox.org \
    --to=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.org \
    --cc=m.felsch@pengutronix.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