linux-kernel - Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

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

Message-ID: <51AFA6DD.3000202@wwwdotorg.org>
Date:	Wed, 05 Jun 2013 15:00:13 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	"jonsmirl@...il.com" <jonsmirl@...il.com>
CC:	Luke Kenneth Casson Leighton <lkcl@...l.net>,
	devicetree-discuss <devicetree-discuss@...abs.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	debian-arm@...ts.debian.org, debian-release@...ts.debian.org,
	Linux on small ARM machines 
	<arm-netbook@...ts.phcomp.co.uk>,
	ARM Linux Mailing List <linux-arm-kernel@...ts.infradead.org>,
	debian-kernel@...ts.debian.org
Subject: Re: getting allwinner SoC support upstream (was Re: Uploading linux
 (3.9.4-1))

On 06/05/2013 02:46 PM, jonsmirl@...il.com wrote:
> On Wed, Jun 5, 2013 at 3:46 PM, Luke Kenneth Casson Leighton
> <lkcl@...l.net <mailto:lkcl@...l.net>> wrote:
...
>     the detect line, which is the write-protect line, to setting the DRAM
>     clock timings, saying which kernel driver must be loaded to support
>     the touchscreen, enabling debugging, JTAG, naming the GPIOs for easy
>     and convenient use in the kernel code: basically there isn't a single
>     piece of hardware on the allwinner SoC family which *isn't*
>     reconfigureable through script.fex... and they've even integrated it
>     into u-boot *and* their low-level (early) bootloader as well [which
> 
> 
> Device tree support has been integrated into uboot for about five years now.

There are two aspects to DT support in U-Boot:

1) Having U-Boot pass a DT to the kernel, possibly manipulating a few
properties on the way, e.g. RAM size. As you say, this has been around a
while.

2) Having U-Boot itself read a DT and configure itself, just like the
kernel does. This is relatively new, and only supported by a few boards
(all Tegra to some extent, and a couple each Samsung Exynos and Xilinx
boards). I suspect/guess this is the kind of thing that Luke was
referring to re: U-Boot fex integration.
--
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/