From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Fri, 26 Jul 2013 10:43:55 +0200 Subject: [U-Boot] [RFC] Remove static display data In-Reply-To: <20130726095049.3ee4a02e@crub> References: <20130726095049.3ee4a02e@crub> Message-ID: <51F236CB.3060906@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Robert, Anatolji, On 26/07/2013 09:50, Anatolij Gustschin wrote: >> >> I realize that there's already the FDT and CONFIG_OF_CONTROL functionality >> and device trees sort of cover the passing to Linux part so maybe before >> handing it off, converting the relevant data into a device tree that Linux >> can already use/parse would work. > > Devicetree bindings for describing display timings info exist in recent > Linux kernel versions (since v3.9 I think) and are documented under > Documentation/devicetree/bindings/video/display-timing.txt. In Linux > there are also DT helpers to parse display timings nodes and read the > timing values into fb_videomode structure (of_get_display_timings, > of_get_fb_videomode). Code for adding such display timings nodes to > the device tree under U-Boot doesn't exist yet. IMHO adopting DT looks very interesting, as it can really simplify sharing configuration between u-boot and kernel. On i.MX6 we have not yet started to use DT to configure u-boot as it is already done on other SOCs (Tegra), but it seems to me the right way to do. Best regards, Stefano Babic -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================