Re: [Linux-fbdev-devel] Reading the EDID block for x86 machines

[<sy...@sc...>]

On Thu, Mar 13, 2003 at 01:38:19AM +0800, Antonino Daplas wrote:
> Matrox users are the fortunate few since the author implemented an i2c
> backend.

;)

> That's okay.  The get_EDID() function can get the EDID block several
> ways.
>=20
> 1.  via the driver if it has its own method of getting the EDID block
> (1st choice)
>=20
> 2.  via userland - EDID block (ie get-edid > edid.dmp) uploaded to
> driver via ioctl (2nd choice)
>=20
> 3.  through an arch-specific method -- VBE for x86, OF for PPC, etc
> (last choice)
>=20
> When a user changes monitors without rebooting, he/she can upload an
> edid block appropriate for the display.

Sounds good.

BTW are there public docs available about EDID & DDC? VESA doesn't like
poor open-source developers :(

--=20
Ville Syrj=E4l=E4
sy...@sc...
http://www.sci.fi/~syrjala/