[Openicc] Proposed "ucmm" display profile configuration convention used by ArgyllCMS.

Hal V. Engel hvengel at astound.net
Fri May 30 16:47:05 PDT 2008

On Thursday 29 May 2008 21:47:57 Graeme Gill wrote:
> Hal V. Engel wrote:
> >>Unfortunately I've found it's not easy to test XRandR 1.2 at the moment.
> >>The Intel driver seems to be the only one supporting it, and even though
> >> I specifically bought a Motherboard with an Intel graphics chipset to be
> >> able to test it, the motherboard is rather crippled: There is only one
> >> Video output, and as soon as you plug another video card in, the BIOS
> >> turns the Intel graphics off. The manufacturer seems to think this is a
> >> "feature", aren't interested in fixing it so that you could use the on
> >> board graphics with a plug in card).
> >
> > I think these Intel chip sets expect you to plug in an interface card
> > (not a video card) that is designed to supply the additional video ports.
> >  None (or almost none) of the motherboards with these video chip sets
> > actaully have second video port built in.
> I'd be happy if it had this. It doesn't though, there is no connector to
> add a interface card for a second video out.

My impression is that the chip set talks to the interface card through the 
system bus.  But never having used one of these Intel chip sets I don't know 
for sure how the additional video ports cards work.

> > The Nouveau driver (open source driver for nvidia cards) is now XRandR
> > 1.2 by default and it appears that support for the NV4x series of GPUs
> > (IE. 6xxx and 7xxx cards) is getting farily good now.  The developers
> > claim that in 2D it outperforms the vendors blob and much of the 3D stuff
> > is working for the NV4x GPUs.  But it is at best alpha level code and is
> > also dependant on developement versions of the kernel, xorg and Gallium. 
> > So getting this setup working would be a significant task and it would be
> > difficult to keep it up to date.
> I'm finding the learning curve rather burdensome for non-distro drivers.
> It's easy to waste a week or more trying to get such stuff going, and I
> really don't want to spend time learning all about GIT, building X servers
> etc. etc., since this is not my focus.
> (I wasted over a week playing with Gentoo and Debian, without getting
> either going on my rather vanilla system. Life is too short, and there is
> too much else to do.)
> > I beleave the the RandonHD driver (the new open source driver) is also
> > XRandR 1.2 at this time.  This should be easier to get working than the
> > Nouveau driver because it is closer to being beta level code at this
> > point.   Again the xorg list should have developers working on this that
> > can clarify which version(s) of this driver support XRandR 1.2.

It is rather early in the developement cycle to be using either of these 
drivers unless you have a specific reason for doing it.  You are correct that 
it would likely be a big hassle to get either of these setup.  And on top of 
that it will require some effort to keep these synced up with ongoing 
developement until they are more stable.  The newer open source drivers for 
the AMD cards will start showing up in some distros soon (most likely Fedora 
or SuSE) but it will likely be a while before they are widely available as 
standard packages in most distros.  I would expect the Nouveau driver will 
take even longer to be widely included in distros.

> One can't count on getting a response though in my experience (e.g. my
> report about problems getting the VideoLUTs contents via XRandR 1.2).

I saw this and was wondering if perhaps someone had gotten back to you off 
list.  But I guess not.

Have you learned anything new about this issue or are you still getting back 
all zeros when you ask XRandR for the gamma table?

> Graeme Gill.
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc

More information about the openicc mailing list