linux-kernel - RE: [PATCH 12/60] microblaze_v4: Generic dts file for platforms

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] [day] [month] [year] [list]

Message-Id: <1214958330.20711.205.camel@pasglop>
Date:	Wed, 02 Jul 2008 10:25:30 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>
Cc:	John Williams <john.williams@...alogix.com>,
	grant.likely@...retlab.ca, linux-arch@...r.kernel.org,
	Michal Simek <monstr@...str.eu>, vapier.adi@...il.com,
	arnd@...db.de, matthew@....cx, microblaze-uclinux@...e.uq.edu.au,
	linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
	will.newton@...il.com, hpa@...or.com, John Linn <linnj@...inx.com>,
	monstr@...nam.cz, drepper@...hat.com, alan@...rguk.ukuu.org.uk
Subject: RE: [PATCH 12/60] microblaze_v4: Generic dts file for platforms

On Tue, 2008-07-01 at 08:58 -0700, Stephen Neuendorffer wrote:
> Doing this at the binary level would be nice, but I see enough problems
> just doing it at the source level and at least for my purposes, doing it
> on a dtb would be overkill, I think.   
> 
> The main difficulty remains how to deal with cross references between
> nodes in a reasonable way where the references cross from one fragment
> to another.

I would have those done in the toplevel .dts

You can always override the property with the reference....

Ie. you #include your CPU or your SOC for example, and then override
some property to point to something else using the override mechanism I
mentioned.

Ben.




--
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/