On Sun, Feb 28, 2010 at 1:44 AM, Mitch Bradley <wmb@xxxxxxxxxxxxx> wrote:
> Grant Likely Wrote:
>> On Sat, Feb 27, 2010 at 2:58 PM, Anatolij Gustschin <agust@xxxxxxx> 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 display in a separate device tree node. Maybe
>> something like this...
>>
>> video {
>> compatible = "fsl,mpc5121-diu";
>> display {
>> compatible = "<vendor>,<model>";
>> edid = [edid-data];
>> };
>> };
>>
>
>
> 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 the OLPC machine. The kernel driver uses it instead of trying to obtain
> the EDID data from the monitor, because the builtin OLPC display cannot
> supply EDID data through the usual hardware interfaces.
Cool. That sounds sane then. How do you go about generating the EDID
data? Is there a tool that can do that? Or did you hand craft it?
Cheers,
g.
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
