On Mon, Oct 28, 2002 at 07:40:12PM +0100, Michel Dänzer wrote: > Every monitor has a characteristic color response curve; that's one > thing one can compensate for using xgamma. You can't expect the same > values to produce the same result on different monitors. Okay, I'm getting frustrated with you Matrox guys. Jeffrey Baker says: "The capability is obviously there to set gamma on both in hardware." Marc Wilson says: "I used xgamma (at first) in $HOME/.xsession, and later manipulating XF86Config-4 directly, to reduce the gamma on the second monitor" ...but he also doesn't even use Matrox cards anymore, so he is unlikely to be able to reproduce anything. Brett Carter says: "After a quick reboot to windows, looks like the results are the same there - you can't set the gamma on the second head." Given all this contradiction, I'm making the following decree: * Brett Carter is the bug submitter. He is willing and able to see if he can reproduce this on his specific hardware. Maybe he is using a Matrox card that can't set gamma on the secondary head. If so, this is not a bug. Brett, can you confirm this? * If someone has a Matrox card that *can* set the gamma on the second head, file a separate report. Brett has a Matrox MGA G400 AGP rev 130. That is the only model of card that matters for this report. Also, guys, please keep your headers under control. Please mail exactly one address with a bug number in it, and please make sure it is 166413@bugs.debian.org. -- G. Branden Robinson | Debian GNU/Linux | "Bother," said Pooh, as he was branden@debian.org | assimilated by the Borg. http://people.debian.org/~branden/ |
Attachment:
pgpGzK6FfOfR1.pgp
Description: PGP signature