"poltrone" <> wrote in message
news:...
> I found some code to interpret EDID data at
> http://john.fremlin.de/programs/linux/read-edid/
> You can compile 'parse-edid.c' from
> http://john.fremlin.de/programs/linu...d-1.4.1.tar.gz
> and then save the EDID data to a file which in turn has to be supplied to
> 'parse-edid.exe'
>
> poltrone
>
> "Calvin Guan" <> schrieb im Newsbeitrag
> news:e#...
> > > Thank you so much. I did read out the EDID with your code. I really
> don't
> > > understand your code. But anyway, here is the result after running it:
> >
> > Each time a child PDO (monitor) is enumerated by the videoport/miniport
> > combo, the port driver stores the Edid data into child's device registry
> > key, (Actually, it took me sometime to figure out in windbg) so that app
> can
> > use SetupAPI to read it.
> >
> > > it is a whole screen of strange numbers.
> > > From my understanding the EDID should have some manufactorer
> information,
> > > Gamma value, display modes, etc.
> >
> > It also contains standard/extended timing info, pixel clock, display
> > PhySize(not for projector though) and many other.
> >
> > > Do you mean I should find some detailed
> > > specifications of these numbers and do some translation? I think I can
> > find
> > > some specifications if they are available to the public somewhere on
the
> > > Internet.
> >
> > See this:
> > http://www.vesa.org/standards_faqs.html#EDID
> >
> > I'm not sure if you have to be a member to access the doc. I bet you may
> > find the definition of EDID struct in open source community?
> >
> > EDID can have extension block, i.e. CEA861 block in many plasma TV which
> is
> > not governed by VESA.
> >
> > > btw, did you use any DDK function in your above code?
> >
> > SetupDiXxx is documented in DDK.
> >
> > >Thank you so much. I
> > > really apreciate that.
> >
> > You are very welcome.
> >
> > Calvin
> > -
> > Calvin Guan Software Engineer
> > ATI Technologies Inc. www.ati.com
> >
> >
>
Hi poltrone,
This is a smart solution. That's great. Thank you very much. Yet after some
reading, I still could not find the interepreation for Gamma value which is
one BYTE in EDID...
I read 120 from my EDID of DELL 2001FP. But how does that 120 relate to
real-world Gamma value?
1.2? 2.2? etc.?
anybody has an idea?
Thank you