From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Sun, 29 Apr 2012 15:08:00 +0200
Subject: [U-Boot] [PATCH v2 01/11] arm: Optionally use existing atags in
	bootm.c
In-Reply-To: <5992269.LhFVZi1UCt@pali>
References: <1335634011-9104-1-git-send-email-pali.rohar@gmail.com>
	<201204291110.42156.marex@denx.de> <5992269.LhFVZi1UCt@pali>
Message-ID: <201204291508.01145.marex@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Dear Pali Roh?r,

> On Sunday 29 April 2012 11:10:42 Marek Vasut wrote:
> > Dear Pali Roh?r,
> > 
> > > On Sunday 29 April 2012 00:15:23 Marek Vasut wrote:
> > > > Won't it be easier to create a preprocessing function
> > > > that'd
> > > > fill gd properly, so uboot can generate the atags through
> > > > standard means then?
> > > 
> > > Do you mean to generate/copy other atags in board code? This
> > > will not work because u-boot (in bootm.c) always passing
> > > ATAG_CORE in function setup_start_tag. And I do not want to
> > > pass ATAG_CORE two times to kernel (once which I copy from
> > > other bootloader and once which generate u-boot).
> > 
> > No, I mean parse the old ATAGS from nolo and fill u-boot's
> > internal structures with that. Then let uboot generate the
> > ATAGS from it's internal structures as usual.
> > 
> > Best regards,
> > Marek Vasut
> 
> Ok, but what to do with non-standard omap/maemo atags which is
> used only for maemo (atag for bootreason, atag for bootmode ...)?
> U-Boot does not have internal structures for these non-standrad
> atags and also does not support passing it.

Implement support for passing ad-hoc additional non-standard atags then?

Best regards,
Marek Vasut