On Fri, Jul 23, 2010 at 9:00 AM, Anatolij Gustschin wrote:
> Adds support for encoding display mode information
> in the device tree using verbatim EDID block.
>
> If the EDID entry in the DIU node is present, the
> driver will build mode database using EDID data
> and allow setting the display mo
On Thu, Dec 16, 2010 at 9:47 AM, Timur Tabi wrote:
> On Fri, Jul 23, 2010 at 9:00 AM, Anatolij Gustschin wrote:
>> Adds support for encoding display mode information
>> in the device tree using verbatim EDID block.
>>
>> If the EDID entry in the DIU node is present, the
>> driver will build mode
Grant Likely wrote:
> This is for devices which don't have an i2c edid channel.
So are we expecting board-specific code in U-Boot to add the data to the device
tree?
--
Timur Tabi
Linux kernel developer at Freescale
___
Linuxppc-dev mailing list
Linux
On Thu, Dec 16, 2010 at 9:55 AM, Timur Tabi wrote:
> Grant Likely wrote:
>> This is for devices which don't have an i2c edid channel.
>
> So are we expecting board-specific code in U-Boot to add the data to the
> device
> tree?
No. It is a static property of the board/machine. It is expected i
"K.Prasad" writes:
> How about the revised patch below? It is only compile-tested; have you
> got a quick test case that I can run?
It crashes the kernel when running the watch-vfork test.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 4
Grant Likely wrote:
> No. It is a static property of the board/machine. It is expected it
> to be encoded into the board's .dts file.
Ok, but that only makes sense if the monitor is hard-wired to the board itself.
If a user can attach any monitor he wants, then the EDID data can't be known at
c
On Thu, 16 Dec 2010 10:47:53 -0600
Timur Tabi wrote:
> On Fri, Jul 23, 2010 at 9:00 AM, Anatolij Gustschin wrote:
> > Adds support for encoding display mode information
> > in the device tree using verbatim EDID block.
> >
> > If the EDID entry in the DIU node is present, the
> > driver will bui
On Thu, Dec 16, 2010 at 10:28 AM, Timur Tabi wrote:
> Grant Likely wrote:
>> No. It is a static property of the board/machine. It is expected it
>> to be encoded into the board's .dts file.
>
> Ok, but that only makes sense if the monitor is hard-wired to the board
> itself.
> If a user can at
