From: Tom Rini <trini@konsulko.com>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: u-boot@lists.denx.de, Andre Przywara <andre.przywara@arm.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Phil Sutter <phil@nwl.cc>, Stefan Bosch <stefan_b@posteo.net>
Subject: Re: [PATCH 3/5] arm: Disable ATAGs support
Date: Sat, 4 Sep 2021 12:54:37 -0400 [thread overview]
Message-ID: <20210904165437.GG12964@bill-the-cat> (raw)
In-Reply-To: <YTOe/rrgc8vd4DYt@gerhold.net>
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
On Sat, Sep 04, 2021 at 06:29:50PM +0200, Stephan Gerhold wrote:
> Hi Tom,
>
> On Mon, Aug 30, 2021 at 09:16:30AM -0400, Tom Rini wrote:
> > With the exception of nokia_rx51 and icnova-a20-swac, disable ATAG
> > support. A large number of platforms had enabled support but never
> > supported a kernel so old as to require it. Further, some platforms are
> > old enough to support both, but are well supported by devicetree
> > booting, and have been for a number of years. This is because some of
> > the ATAGs related functions have been re-used to provide the same kind
> > of information, but for devicetree or just generally to inform the user.
> > When needed still, rename these functions to get_board_revision()
> > instead, to avoid conflicts. In other cases, these functions were
> > simply unused, so drop them.
> >
> > Cc: Andre Przywara <andre.przywara@arm.com>
> > Cc: Jagan Teki <jagan@amarulasolutions.com>
> > Cc: Phil Sutter <phil@nwl.cc>
> > Cc: Stefan Bosch <stefan_b@posteo.net>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > [...]
> > ---
> > include/configs/stemmy.h | 3 --
> > [...]
> > +++ b/include/configs/stemmy.h
> > @@ -23,7 +23,4 @@
> > #define CONFIG_SYS_L2_PL310
> > #define CONFIG_SYS_PL310_BASE 0xa0412000
> >
> > -/* Generate initrd atag for downstream kernel (others are copied in stemmy.c) */
> > -#define CONFIG_INITRD_TAG
> > -
> > #endif
>
> Please keep this option for the stemmy board. It's still used
> occasionally to boot the original downstream/vendor kernel which is
> currently still necessary to charge the battery on these devices.
>
> See commit e2f82f93 ("board: stemmy: Copy atags for booting
> downstream/vendor kernel") [1] for details.
OK, I'll re-work this to also keep ATAGS support on stemmy when merging,
thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-09-04 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 13:16 [PATCH 1/5] Convert CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG to Kconfig Tom Rini
2021-08-30 13:16 ` [PATCH 2/5] imx: Convert SERIAL_TAG support to ENV_VARS_UBOOT_RUNTIME_CONFIG Tom Rini
2021-09-08 2:31 ` Tom Rini
2021-08-30 13:16 ` [PATCH 3/5] arm: Disable ATAGs support Tom Rini
2021-09-04 16:29 ` Stephan Gerhold
2021-09-04 16:54 ` Tom Rini [this message]
2021-09-08 2:31 ` Tom Rini
2021-08-30 13:16 ` [PATCH 4/5] arm: Add Kconfig entry for MACH_TYPE Tom Rini
2021-09-08 2:32 ` Tom Rini
2021-08-30 13:16 ` [PATCH 5/5] arm: Finish migration of CONFIG_MACH_TYPE Tom Rini
2021-09-08 2:32 ` Tom Rini
2021-09-08 2:31 ` [PATCH 1/5] Convert CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG to Kconfig Tom Rini
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=20210904165437.GG12964@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=phil@nwl.cc \
--cc=stefan_b@posteo.net \
--cc=stephan@gerhold.net \
--cc=u-boot@lists.denx.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