Re: rivafb "Badness" using fbdev.diff.gz and 2.5.5[45]

On Tue, 2003-01-21 at 18:29, Geert Uytterhoeven wrote:

On 21 Jan 2003, Antonino Daplas wrote:

quoted

The only problem right now is how do you pass the monitor info to the
driver?  The best way is to parse the EDID block and use I2C/DDC. 
Personally, I think passing the monitor info as a boot/module option is
the simplest and safest method.

Through sysfs? echo MY_MONITOR_LIMITS > /proc/...?

Since ioctls are considered evil these days, changing the resolution etc. could
work in a similar way as well.

True, but I prefer having the monitor limits at driver load time so I
can immediately go into a high resolution.

Tony




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com