public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: Chris Morgan <macroalpha82@gmail.com>,
	u-boot@lists.denx.de, xypron.glpk@gmx.de, cym@rock-chips.com,
	philipp.tomsich@vrull.eu, sjg@chromium.org,
	eugen.hristev@collabora.com, jonas@kwiboo.se,
	Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH 1/2] rockchip: rk3588: Add support for ATAG parsing
Date: Wed, 27 Mar 2024 08:12:46 -0400	[thread overview]
Message-ID: <20240327121246.GH3442575@bill-the-cat> (raw)
In-Reply-To: <fe9eef97-5814-4d25-8357-60873d565aff@rock-chips.com>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

On Wed, Mar 27, 2024 at 06:32:06PM +0800, Kever Yang wrote:
> Hi Chris,
> 
>     The ATAGS is used for passing parameter from bootloader to kernel at
> first, which has been replaced by DTB now for ARM platform.
> 
>     And Rockchip using ATAGs for passing parameter like dram memory
> size/board uart in different boot process like DRAM init binary/ TPL/SPL to
> U-Boot since 2018.
> 
>     And almost at the same time, Simon add bloblist for mainline U-Boot
> which for similar purpose.
> 
>     So I'm not sure if this ATAGS should be accept in mainline U-Boot or
> not, even for rockchip platform only seems some kind of regression for this
> feature support.
> 
> 
> Hi Simon and Tom,
> 
>      Could you help to give some suggestion for this?

This should be using bloblist, yes, as I understand it.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-03-27 12:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 20:49 [PATCH 0/2] Use ATAGs for RK3588 For RAM Info Chris Morgan
2024-03-26 20:49 ` [PATCH 1/2] rockchip: rk3588: Add support for ATAG parsing Chris Morgan
2024-03-27  9:45   ` Quentin Schulz
2024-03-27 10:32   ` Kever Yang
2024-03-27 12:12     ` Tom Rini [this message]
2024-03-27 13:32     ` Chris Morgan
2024-03-27 14:21       ` Eugen Hristev
2024-03-27 15:03         ` Chris Morgan
2024-03-28 20:02           ` Tom Rini
2024-03-28 21:58             ` Chris Morgan
2024-03-28 22:13               ` Tom Rini
2024-03-26 20:49 ` [PATCH 2/2] rockchip: rk3588: Add Support for RAM Defines from ATAGs Chris Morgan
2024-03-27 10:51   ` Quentin Schulz
2024-03-27 13:10     ` Jonas Karlman

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=20240327121246.GH3442575@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=cym@rock-chips.com \
    --cc=eugen.hristev@collabora.com \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --cc=macroalpha82@gmail.com \
    --cc=macromorgan@hotmail.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --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