mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH] Documentation: boards: k3: remove obsolete k3.rst
Date: Thu,  5 Jun 2025 12:14:16 +0200	[thread overview]
Message-ID: <20250605101416.463490-1-s.hauer@pengutronix.de> (raw)

k3.rst describes the initial k3 documentation when we only had second
stage support after U-Boot. This is now obsolete and the full
documentation is in ti-k3.rst.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
 Documentation/boards/k3.rst | 29 -----------------------------
 1 file changed, 29 deletions(-)
 delete mode 100644 Documentation/boards/k3.rst

diff --git a/Documentation/boards/k3.rst b/Documentation/boards/k3.rst
deleted file mode 100644
index f675c4510c..0000000000
--- a/Documentation/boards/k3.rst
+++ /dev/null
@@ -1,29 +0,0 @@
-Texas Instruments K3
-====================
-
-K3 is for Keystone 3 and denotes a family of SoCs from Texas Instruments. From these
-SoCs the AM62x is currently supported under barebox. The boot flow needs several images,
-only the last stage is supported by barebox. To start up the help of U-Boot is still
-needed.
-
-The board currently supported by barebox is the BeaglePlay board, see
-https://www.beagleboard.org/boards/beagleplay. The following examples assume
-this board is used.
-
-Building barebox
-----------------
-.. code-block:: sh
-
-  make ARCH=arm CROSS_COMPILE=<ARM toolchain prefix> multi_v8_defconfig
-
-Running barebox
----------------
-
-barebox can be started from running U-Boot with:
-
-.. code-block:: sh
-
-  dhcp 0x82000000 <serverip>:barebox-beagleplay.img; bootm 0x82000000
-
-To start barebox from SD/eMMC replace the ``u-boot.img`` on a bootable SD/eMMC card
-with the content of ``images/barebox-beagleplay-fit.img``
-- 
2.39.5




             reply	other threads:[~2025-06-05 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 10:14 Sascha Hauer [this message]
2025-06-05 11:54 ` 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=20250605101416.463490-1-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox