Re: [PATCH] fbdev: add a function to parse further EDID Detailed Timing Descriptors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 21 Oct 2010, Dave Airlie wrote:

> On Fri, Aug 20, 2010 at 5:23 PM, Erik Gilling <konkers@xxxxxxxxxx> wrote:
> > Guennadi,
> >    Not sure how you're using the edid but you can get all 4 DTDs by
> > calling fb_edid_to_monspecs() then calling fb_videomode_to_var() on
> > each of the entries in monspecs.modedb.  This is still lacking as
> > modern monitors/tvs can have multiple EDID blocks.  My recent patch
> > [1] is a proposal for addressing that.
> 
> If someone is really interested in fixing up the fbdev EDID parser
> they probably should look at sharing the drm EDID parser, its a lot
> more complete and came mostly from the EDID parser in the X server.

I might be overseeing something, but in next/master I don't see any code 
to parse SVDs in DRM. Could someone, please, point me out to it, if it is 
indeed implemented?

If it is not implemented - how would one do it? Do I understand it right, 
that the precise timing for those modes should be copied from the 
CEA/EIA-861E document?

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
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


[Index of Archives]     [Video for Linux]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Tourism]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux