DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [DistroKit] [PATCH 4/4] v7a: barebox: am335x-mlo: document some unusual kconfig options
Date: Thu, 11 Jul 2024 13:01:43 +0200	[thread overview]
Message-ID: <20240711110143.470379-4-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20240711110143.470379-1-a.fatoum@pengutronix.de>

While we generally prefer ARM-optimized string/memory routines and
support of GPT in barebox, the MLO configuration is special:
It's size constrained by having to run from on-chip SRAM and it need
only worry about loading barebox from the same partition the MLO came
from.

Therefore leave the configuration as-is, but explain the choices made.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 configs/bsp.ref | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/configs/bsp.ref b/configs/bsp.ref
index b7077411c2dd..5b5b4a763b15 100644
--- a/configs/bsp.ref
+++ b/configs/bsp.ref
@@ -45,6 +45,32 @@ optee_disabled_features:
     - CFG_ENABLE_EMBEDDED_TESTS
     - CFG_TEE_CORE_TA_TRACE
 
+barebox_arm_optimized_string_functions:
+  description: |
+    The use of assembler optimized memcpy / memset functions improves
+    throughput at the cost of an increase in binary size.
+    The am335x-mlo configuration is very size constrained, because it
+    needs to fit into on-chip SRAM to be able to set up DRAM and thus
+    we use the smaller C implementation instead.
+  variants:
+    - condition: kconfig.BareboxConfig()['ARCH_OMAP'] and kconfig.BareboxConfig()['SHELL_NONE']
+      value: False
+    - value: True
+
+barebox_gpt_support:
+  description: |
+    The am335x boot ROM expects SD/MMC media to be formatted as MBR
+    and loads the first stage bootloader from the BOOT.BIN file from the
+    first vfat partition. As the MLO
+
+    As the am335x-mlo configuration's only function is to chainload
+    barebox, we only need GPT support later on in the second stage
+    barebox-am335x configuration.
+  variants:
+    - condition: kconfig.BareboxConfig()['ARCH_OMAP'] and kconfig.BareboxConfig()['SHELL_NONE']
+      value: False
+    - value: True
+
 rootfs_unused_libraries:
   description: |
     - libatomic is needed on mips and rpi1 by libcrypto, but for simplicity ship it on all platforms
-- 
2.39.2




  parent reply	other threads:[~2024-07-11 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 11:01 [DistroKit] [PATCH 1/4] v7a: barebox: enable ARM accelerated SHA1 routines Ahmad Fatoum
2024-07-11 11:01 ` [DistroKit] [PATCH 2/4] v7a: barebox: don't activate first console Ahmad Fatoum
2024-07-11 11:01 ` [DistroKit] [PATCH 3/4] v7a: barebox: don't use root=PARTUUID= when booting from SD/eMMC Ahmad Fatoum
2024-07-11 11:01 ` Ahmad Fatoum [this message]
2024-07-12 14:30 ` [DistroKit] [PATCH 1/4] v7a: barebox: enable ARM accelerated SHA1 routines Robert Schwebel

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=20240711110143.470379-4-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=distrokit@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