public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ATAGS for Tegra, Sunxi, etc.
Date: Thu, 17 Dec 2015 08:41:53 -0500	[thread overview]
Message-ID: <20151217134153.GE5877@bill-the-cat> (raw)
In-Reply-To: <56727FAF.2060304@redhat.com>

On Thu, Dec 17, 2015 at 10:26:07AM +0100, Hans de Goede wrote:
> Hi,
> 
> On 17-12-15 10:21, Ian Campbell wrote:
> >On Thu, 2015-12-17 at 07:40 +0100, Karsten Merker wrote:
> >>On Thu, Dec 17, 2015 at 01:59:57PM +0900, Masahiro Yamada wrote:
> >>>2015-12-17 13:58 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.c
> >>>om>:
> >>>>Hi,
> >>>>
> >>>>I noticed some well-maintained new SoC families still
> >>>>define CONFIG_CMDLINE_TAG.
> >>>>
> >>>>
> >>>>For example,
> >>[...]
> >>>>include/configs/sunxi-common.h
> >>>>
> >>>>  #define CONFIG_SETUP_MEMORY_TAGS
> >>>>  #define CONFIG_CMDLINE_TAG
> >>>>  #define CONFIG_INITRD_TAG
> >>>>  #define CONFIG_SERIAL_TAG
> >>
> >>>>Do they still use ATAGS, not device tree?
> >>
> >>Sunxi uses devicetree for mainline kernels, but AFAIK ATAG
> >>support is necessary to enable booting legacy vendor kernels.
> >>There is still new sunxi-based hardware sold today that comes
> >>with legacy 3.4-based kernels.
> >
> >That legacy kernel is FEX (allwinners own description blob) based, I don't
> >know to what extent that involves ATAGs in some way though.
> >
> >There are also people who use the 3.4 based fork from linux-sunxi.org, but
> >I don't know if that is DT or ATAGS or FEX.
> >
> >A dependency on CONFIG_OLD_SUNXI_KERNEL_COMPAT might be an option depending
> >on what the kernels need, Hans probably knows better than I do.
> 
> The 3.4 based kernels use both ATAGS for things like memory size, and fex
> for other hw config info.
> 
> I'm not in favor of wrapping things in CONFIG_OLD_SUNXI_KERNEL_COMPAT, because
> recent 3.4 based kernels can boot without that, and I believe that removing
> the ATAG support will break this, without really buying us much.

+1.  ATAG is also used iirc for some other operating systems, still.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151217/83ebe555/attachment.sig>

  reply	other threads:[~2015-12-17 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK7LNATeQZBGJ6LkHCDvQgUGBA_+mXikzK559ZhHbrdn6Ydp0Q@mail.gmail.com>
2015-12-17  4:59 ` [U-Boot] ATAGS for Tegra, Sunxi, etc Masahiro Yamada
     [not found]   ` <20151217064026.GA1883@excalibur.cnev.de>
2015-12-17  9:21     ` Ian Campbell
2015-12-17  9:26       ` Hans de Goede
2015-12-17 13:41         ` Tom Rini [this message]
2015-12-17 16:44   ` Stephen Warren
2015-12-18 11:35     ` Masahiro Yamada
2015-12-19 20:31     ` Marcel Ziswiler

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=20151217134153.GE5877@bill-the-cat \
    --to=trini@konsulko.com \
    --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