linux-kernel - Re: [PATCH 2/4] sparc: break out some prom device-tree building code out into drivers/of

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100707051548.2c44f30c@debxo>
Date:	Wed, 7 Jul 2010 05:15:48 +0000
From:	Andres Salomon <dilinger@...ued.net>
To:	David Miller <davem@...emloft.net>
Cc:	grant.likely@...retlab.ca, devicetree-discuss@...ts.ozlabs.org,
	sparclinux@...r.kernel.org, x86@...nel.org, tglx@...utronix.de,
	mingo@...hat.com, hpa@...or.com, cjb@...top.org, wmb@...top.org,
	pgf@...top.org, linux-kernel@...r.kernel.org,
	benh@...nel.crashing.org
Subject: Re: [PATCH 2/4] sparc: break out some prom device-tree building
 code out into drivers/of

On Mon, 05 Jul 2010 19:22:21 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:

> From: Andres Salomon <dilinger@...ued.net>
> Date: Wed, 7 Jul 2010 04:07:34 +0000
> 
> >  - For the pdt, calling into the prom once for each property/node to
> >    create a fdt, and then unflattening it.  This is better than the
> >    previous option, but I don't think the prom->fdt code will be
> > very nice.
> 
> I'll need this on sparc64 at some point to support kexec() anyways.
> 
> So at least for sparc you can assume that a something-->fdt translator
> is going to exist at some point in the future regardless of what
> happens here.
> 


Sounds like we have a winner.  I'll concentrate on that, thanks for
the heads up.
--
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/