Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932236Ab3FEVAV (ORCPT ); Wed, 5 Jun 2013 17:00:21 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:45244 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932194Ab3FEVAR (ORCPT ); Wed, 5 Jun 2013 17:00:17 -0400 Message-ID: <51AFA6DD.3000202@wwwdotorg.org> Date: Wed, 05 Jun 2013 15:00:13 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: "jonsmirl@gmail.com" CC: Luke Kenneth Casson Leighton , devicetree-discuss , Linux Kernel Mailing List , debian-arm@lists.debian.org, debian-release@lists.debian.org, Linux on small ARM machines , ARM Linux Mailing List , debian-kernel@lists.debian.org Subject: Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1)) References: In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1530 Lines: 31 On 06/05/2013 02:46 PM, jonsmirl@gmail.com wrote: > On Wed, Jun 5, 2013 at 3:46 PM, Luke Kenneth Casson Leighton > > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/