[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877ffrp3fc.fsf@gmail.com>
Date: Thu, 21 Apr 2016 14:11:19 +0200
From: Holger Schurig <holgerschurig@...il.com>
To: Thierry Reding <thierry.reding@...il.com>
Cc: Boris Brezillon <boris.brezillon@...e-electrons.com>,
Riccardo Bortolato <bortolato@...altechitalia.it>,
David Airlie <airlied@...ux.ie>,
Nicolas Ferre <nicolas.ferre@...el.com>,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
Daniel Vetter <daniel@...ll.ch>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] drm/panel: simple: Add support for Innolux AT070TN92
Thierry Reding <thierry.reding@...il.com> writes:
> Applied, thanks.
I once read that this is the recommended way to go, instead of
specifying the timings in the device tree. Why is this so? Any new
display just increases the .text size of the kernel unnessary.
Did this idea stem from the era where bootloaders like Barebox couldn't
modify the DT ad-hoc before handing it over to the kernel?
Powered by blists - more mailing lists