linux-kernel - Re: [RFC] [PATCH] Device Tree on ARM platform

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]

Date:	Thu, 28 May 2009 14:43:21 +0200
From:	Holger Schurig <hs4233@...l.mn-solutions.de>
To:	linux-arm-kernel@...ts.arm.linux.org.uk
Cc:	Timur Tabi <timur@...escale.com>,
	Janboe Ye <yuan-bo.ye@...orola.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	linux-kernel@...r.kernel.org, rmk@....linux.org.uk
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform

> Lack of device-tree support on ARM has been a real hindrance to
> getting the ARM-based Linux support on par with PowerPC.

And I always thought that this is because Freescale does some BSP 
in the background, then release a BSP with some kernel and 
doesn't even try getting something included in "main" Linus, 
a.k.a. into Linus' tree.

Hey, but that's better then Marvell, where you need to sign an 
NDA to even access the documentation. With Freescale's doc (and 
help of the community!) I was able to get some Freescale i.MX21 
related drivers into Linus' tree.
--
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/