On Wed, Apr 28, 2010 at 7:43 AM, Anatolij Gustschin wrote:
> On Mon, 01 Mar 2010 14:45:20 +1100
> Benjamin Herrenschmidt wrote:
>
>> On Sat, 2010-02-27 at 22:44 -1000, Mitch Bradley wrote:
>>
>> > As it turns out, I'm doing exactly that - exporting verbatim EDID
>> > data
>> > as the value of the
On Mon, 01 Mar 2010 14:45:20 +1100
Benjamin Herrenschmidt wrote:
> On Sat, 2010-02-27 at 22:44 -1000, Mitch Bradley wrote:
>
> > As it turns out, I'm doing exactly that - exporting verbatim EDID
> > data
> > as the value of the "edid" property - for the display node on the Via
> > version of t
At some stage, Grant wrote:
> > First off, I did a tiny amount of research, and I didn't find any
> > existing OpenFirmware bindings for describing video displays.
> > Otherwise, I'd suggest considering that.
There's a binding for framebuffers but it sucks big time :-) It doesn't
provide a reliab
On Sun, Feb 28, 2010 at 1:44 AM, Mitch Bradley wrote:
> Grant Likely Wrote:
>> On Sat, Feb 27, 2010 at 2:58 PM, Anatolij Gustschin wrote:
>> Also, since you're now in the realm of describing a video display,
>> which is separate from the display controller, you should consider
>> describing the d
Hi Anatolij,
[added cc: to devicetree-disc...@lists.ozlabs.org]
On Sat, Feb 27, 2010 at 2:58 PM, Anatolij Gustschin wrote:
> Framebuffer drivers may want to get panel timing info
> from the device tree. This patch adds appropriate support.
> Subsequent patch for FSL DIU frame buffer driver
Hi Anatolij,
[added cc: to devicetree-disc...@lists.ozlabs.org]
On Sat, Feb 27, 2010 at 2:58 PM, Anatolij Gustschin wrote:
> Framebuffer drivers may want to get panel timing info
> from the device tree. This patch adds appropriate support.
> Subsequent patch for FSL DIU frame buffer driver makes
