From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Marc Olberding <molberding@nvidia.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arm: dts: aspeed: add an alt 128M flash layout
Date: Thu, 08 Jan 2026 16:34:57 +1030 [thread overview]
Message-ID: <3d6aaf558fd8b60ec7010f976a747d9f0a727f98.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20251218-alt-128-v2-1-10499a0b7eb9@nvidia.com>
Hi Marc,
Regarding the subject prefix, can you please capitalise the 'ARM' portion, so:
ARM: dts: aspeed: add an alt 128M flash layout
That way it's consistent with the rest of history.
On Thu, 2025-12-18 at 10:48 -0800, Marc Olberding wrote:
> Add a 128M layout for the BMC flash chip we didn't boot from. Including
> this allows the user to write to each partition on the alternate spi
> chip. This dtsi follows the existing standard of using the same layout
> as non alt version and prepending `alt` to each partition's name.
>
> Testing: Include this in msx4 and cat size, offsets and name
I think this would be better with s/Testing/Tested by/ and associated
grammar fixes.
> ```
> for devdir in /sys/class/mtd/mtd*; do
> > [[ -d $devdir && -r $devdir/name ]] || continue
> > name=$(<"$devdir/name")
> > [[ $name == alt* ]] || continue
> >
> > size=$(<"$devdir/size")
> > offset=0
> > [[ -r $devdir/offset ]] && offset=$(<"$devdir/offset")
> >
> > dev=$(basename "$devdir")
> > printf "%s name=%s offset=0x%X size=0x%X\n" "$dev" "$name" \
> > "$offset" "$size"
> > done
> mtd10 name=alt-rofs offset=0xA00000 size=0x5600000
> mtd11 name=alt-rwfs offset=0x6000000 size=0x2000000
> mtd7 name=alt-u-boot offset=0x0 size=0xE0000
> mtd8 name=alt-u-boot-env offset=0xE0000 size=0x20000
> mtd9 name=alt-kernel offset=0x100000 size=0x900000
> ```
Can you rather remove the markdown codeblock and instead indent the
code snippet (IMO 4 spaces is fine)?
Also the shell continuation markers seem a little unfortunate. Maybe
just drop them for clarity? You can separate the output from the
script.
I also found this helpful:
diff -u arch/arm/boot/dts/aspeed/openbmc-flash-layout-128{,-alt}.dtsi
Andrew
next prev parent reply other threads:[~2026-01-08 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 18:48 [PATCH v2 0/2] arm: dts: aspeed: Add an alt 128M flash layout Marc Olberding
2025-12-18 18:48 ` [PATCH v2 1/2] arm: dts: aspeed: add " Marc Olberding
2026-01-08 6:04 ` Andrew Jeffery [this message]
2025-12-18 18:48 ` [PATCH v2 2/2] arm: dts: aspeed: Add alt partition support to msx4 Marc Olberding
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=3d6aaf558fd8b60ec7010f976a747d9f0a727f98.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=molberding@nvidia.com \
--cc=robh@kernel.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