[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46811670.AspmkHD9JS@wuerfel>
Date: Fri, 15 May 2015 22:21:13 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Pali Rohár <pali.rohar@...il.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
Russell King <linux@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
Sebastian Reichel <sre@...ian.org>,
Will Deacon <will.deacon@....com>,
linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>,
linux-omap@...r.kernel.org,
Andreas Färber <afaerber@...e.de>
Subject: Re: [PATCH 2/2] arm: boot: store ATAG structure into DT atags field
On Friday 15 May 2015 22:16:24 Pali Rohár wrote:
> On Friday 15 May 2015 22:12:41 Arnd Bergmann wrote:
> > On Friday 15 May 2015 21:50:07 Pali Rohár wrote:
> > > }
> > >
> > > }
> > >
> > > + /* include the terminating ATAG_NONE */
> > > + atag_size = (char *)atag - (char *)atag_list +
> > > sizeof(struct tag_header); + setprop(fdt, "/", "atags",
> > > atag_list, atag_size);
> > > +
> > >
> > > if (memcount) {
> > >
> > > setprop(fdt, "/memory", "reg", mem_reg_property,
> > >
> > > 4 * memcount * memsize);
> >
> > The property should probably have a DT binding, and be named
> > "linux,atags".
> >
> > It may also help to check if the "linux,atags" property already
> > exists and not create it otherwise. That way we can put it into the
> > n900 dts file and have it updated by the compat code, but not expose
> > the atags on other platforms unless they opt in.
> >
> > Arnd
>
> Maybe what would help: Is there a way to tell decompressor/kernel to not
> touch atag memory and then after kernel/board-code starts it save copy
> of atags? I think it is not possible right now, but correct me if I'm
> wrong...
>
I don't think that is possible without an incompatible change to the
boot protocol.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists