On Mon, Nov 11, 2002 at 08:56:10AM +0000, Dr Andrew C Aitchison wrote:
> On Sun, 10 Nov 2002 [EMAIL PROTECTED] wrote:
> 
> > On Sun, Nov 10, 2002 at 07:05:49PM +0000, Dr Andrew C Aitchison wrote:
> > > That is a success;
> > >  /root/XF86Config.new should have some info about the monitor.
> > 
> > Some, but not much.
> > 
> > Section "Monitor"
> >         #DisplaySize      330   270     # mm
> >         Identifier   "Monitor0"
> >         VendorName   "AY_"
> >         ModelName    "2fd"
> >         Option      "DPMS"
> > EndSection
> 
> So DDCvbe works on your system.
> In mga_driver.c you could change the call to MGAdoDDC into a call
> to MGAProbeDDC (it may be a little more complicated than that).

I'll take a look. Thanks for the pointer.

> What do you actually want to do with DDC info ?
> I think it makes more sense to use DDC at config time (and interactive
> reconfig) than start time, otherwise server state will change
> if the server is started up with the screen turned off.

I agree that using DDC makes the most sense at config time, whether
in the initial configuration or for reconfiguration. I'd like DDC to
be able to detect and configure my monitor - when I installed Red
Hat 7.{0,2,3}, for example, it was able properly to detect my monitor's
relevant sttings. Perhaps this was some feature of the Red Hat
installer, but I seem to recall being able to do "X -configure" and
get the same useful DDC output.

This isn't keeping me up at night, though. Rather, it's a mild 
annoyance.

Kurt
-- 
Religion has done love a great service by making it a sin.
                -- Anatole France
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Reply via email to