From: Nishanth Menon <nm@ti.com>
To: Tom Rini <trini@konsulko.com>
Cc: Roger Quadros <rogerq@kernel.org>, <michael@amarulasolutions.com>,
<dario.binacchi@amarulasolutions.com>, <afd@ti.com>,
<vigneshr@ti.com>, <praneeth@ti.com>, <srk@ti.com>,
<r-gunasekaran@ti.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH 4/4] configs: am64x_evm_a53_defconfig: Enable NAND
Date: Tue, 9 Jan 2024 14:00:14 -0600 [thread overview]
Message-ID: <20240109200014.wda3anzu4gljeic6@glitch> (raw)
In-Reply-To: <20240109194807.GX1610741@bill-the-cat>
On 14:48-20240109, Tom Rini wrote:
[...]
> > > --
> > > 2.34.1
> > >
> >
> > Why not a config fragment?
>
> To me, this makes sense to keep in the main config. It can be turned off
> as needed, and at run time if it's not present, it's safe.
Three reasons:
* There is going to be duplication across multiple boards
* It confuses the affair of trying to find the minimal configuration needed
to boot the board.
* SRAM is limited already - we have been playing all kind of dances
around this - NAND is a daughter card addon - while I am not trying to
diminish NAND support, we are in a constant struggle to keep SRAM
viable and adding additional boot modes to a single config, IMHO is
the wrong direction to go.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-01-09 20:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 12:26 [PATCH 0/4] arm: mach-k3: am64: Add NAND configuration Roger Quadros
2024-01-09 12:26 ` [PATCH 1/4] memory: ti-gpmc: Fix build Roger Quadros
2024-01-09 12:26 ` [PATCH 2/4] mtd: rawnand: omap_gpmc: Use DT provided IO address Roger Quadros
2024-01-09 12:26 ` [PATCH 3/4] arm: mach-k3: am642: Define NAND boot device Roger Quadros
2024-01-09 12:26 ` [PATCH 4/4] configs: am64x_evm_a53_defconfig: Enable NAND Roger Quadros
2024-01-09 19:16 ` Nishanth Menon
2024-01-09 19:48 ` Tom Rini
2024-01-09 20:00 ` Nishanth Menon [this message]
2024-01-09 20:35 ` Tom Rini
2024-01-09 19:18 ` Nishanth Menon
2024-01-09 19:54 ` Tom Rini
2024-01-09 20:00 ` Francesco Dolcini
2024-01-09 20:22 ` Nishanth Menon
2024-01-10 9:34 ` Roger Quadros
2024-01-10 16:06 ` Roger Quadros
2024-01-10 16:30 ` Tom Rini
2024-01-09 19:17 ` [PATCH 0/4] arm: mach-k3: am64: Add NAND configuration Nishanth Menon
2024-01-11 12:15 ` Roger Quadros
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=20240109200014.wda3anzu4gljeic6@glitch \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=michael@amarulasolutions.com \
--cc=praneeth@ti.com \
--cc=r-gunasekaran@ti.com \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.