U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Tom Rini <trini@konsulko.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Neha Malcom Francis <n-francis@ti.com>,
	Robert Nelson <robertcnelson@gmail.com>
Cc: Beleswar Padhi <b-padhi@ti.com>, Udit Kumar <u-kumar1@ti.com>,
	Jonathan Humphreys <j-humphreys@ti.com>,
	Andrew Davis <afd@ti.com>, <u-boot@lists.denx.de>,
	Nishanth Menon <nm@ti.com>
Subject: [PATCH 5/9] beagle: beagley-ai: env: Enable DFU env options
Date: Fri, 25 Apr 2025 12:31:15 -0500	[thread overview]
Message-ID: <20250425173120.141503-6-nm@ti.com> (raw)
In-Reply-To: <20250425173120.141503-1-nm@ti.com>

Just enable dfu options, We have MMC and RAM as options here.

Signed-off-by: Nishanth Menon <nm@ti.com>
---
Changes Since v2:
- Dropped the dfu_alt_info override option, let the users select it
- Updated commit message to the effect.

V2: https://lore.kernel.org/r/20250418193943.953952-6-nm@ti.com

 board/beagle/beagley-ai/beagley-ai.env | 1 +
 1 file changed, 1 insertion(+)

diff --git a/board/beagle/beagley-ai/beagley-ai.env b/board/beagle/beagley-ai/beagley-ai.env
index 16a03acfca3c..70afbf9763f9 100644
--- a/board/beagle/beagley-ai/beagley-ai.env
+++ b/board/beagle/beagley-ai/beagley-ai.env
@@ -1,5 +1,6 @@
 #include <env/ti/ti_common.env>
 #include <env/ti/mmc.env>
+#include <env/ti/k3_dfu.env>
 
 #if CONFIG_CMD_REMOTEPROC
 #include <env/ti/k3_rproc.env>
-- 
2.47.0


  parent reply	other threads:[~2025-04-25 17:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 17:31 [PATCH 0/9] board: beagle: beagley-ai: Cleanups and stdboot Nishanth Menon
2025-04-25 17:31 ` [PATCH 1/9] board: beagle: beagley-ai: Add pattern match for MAINTAINERS Nishanth Menon
2025-04-26  2:24   ` Kumar, Udit
2025-04-25 17:31 ` [PATCH 2/9] arch: arm: dts: k3-am67a-beagley-ai-u-boot: Mark main_gpio1 as bootph-all Nishanth Menon
2025-04-25 17:31 ` [PATCH 3/9] beagle: beagley-ai: env: Set up the boot devices and boot methods Nishanth Menon
2025-04-26  2:25   ` Kumar, Udit
2025-04-25 17:31 ` [PATCH 4/9] beagle: beagley-ai: env: Setup scripts for LED control Nishanth Menon
2025-04-25 17:31 ` Nishanth Menon [this message]
2025-04-26  2:26   ` [PATCH 5/9] beagle: beagley-ai: env: Enable DFU env options Kumar, Udit
2025-04-25 17:31 ` [PATCH 6/9] configs: am67a_beagley_ai*: Use saveddefconfig Nishanth Menon
2025-04-25 17:31 ` [PATCH 7/9] configs:am67a_beagley_ai*: Drop un-necessary config options Nishanth Menon
2025-04-25 17:31 ` [PATCH 8/9] configs: am67a_beagley_ai_a53: Enable additional features Nishanth Menon
2025-04-25 17:31 ` [PATCH 9/9] doc: beagle: Add BeagleY-AI documentation Nishanth Menon
2025-04-25 17:36 ` [PATCH 0/9] board: beagle: beagley-ai: Cleanups and stdboot Andrew Davis
2025-04-25 20:03 ` Bryan Brattlof
2025-05-03 16:31 ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2025-04-11 22:57 [PATCH 0/9] board: beagle: beagley-ai: Cleanups and Nishanth Menon
2025-04-11 22:57 ` [PATCH 5/9] beagle: beagley-ai: env: Enable DFU env options Nishanth Menon

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=20250425173120.141503-6-nm@ti.com \
    --to=nm@ti.com \
    --cc=afd@ti.com \
    --cc=b-padhi@ti.com \
    --cc=j-humphreys@ti.com \
    --cc=n-francis@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=xypron.glpk@gmx.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