Paul Owen starstreak.net> writes:
> intel_reg_read 0x70008 (PIPEACONF): 0xC000 / bits 26 and 13 aren't set
> intel_reg_read 0x70180 (DSPACNTR) : 0xD8004400 / bit 25 isn't set
>
> intel_reg_write 0x70008 0xC4002000
> intel_reg_write 0x70180 0xDA004400
>
> Seems to have the desired effect -
On 29 February 2012 18:36, Jesse Barnes wrote:
>
> Can you file a bug with the findings above just so we don't lose it? I
> expect the fix should be pretty easy, but I don't want to lose track of
> this.
Done - hope that I submitted to the right place in the right way! Thanks again.
https://bug
On Wed, 29 Feb 2012 15:38:44 +
Paul Owen wrote:
> On 28 February 2012 17:59, Jesse Barnes
> wrote:
> >
> > There are several places we need to set extended vs normal range:
> > DSP*CNTR (bit 25)
> > PIPE*CONF (bits 26 and 13)
> > TRANS*CONF (bit 10, for xvYCC DP configs)
> > DVS*CNTR (for sp
On 28 February 2012 17:59, Jesse Barnes wrote:
>
> There are several places we need to set extended vs normal range:
> DSP*CNTR (bit 25)
> PIPE*CONF (bits 26 and 13)
> TRANS*CONF (bit 10, for xvYCC DP configs)
> DVS*CNTR (for sprites, bit 21)
Okay - good learning exercise for me this! So by defau
On Tue, 28 Feb 2012 13:53:20 +
Paul Owen wrote:
> Okay so back to this question of broadcast rgb/limited/full range
> colour. I'm not so sure it is working at all under Sandybridge. I use
> XBMC under Linux (Ubuntu) and do not see any difference in the picture
> when I do either of the followi
On 16 January 2012 22:12, Jesse Barnes wrote:
>
> On Mon, 16 Jan 2012 21:50:22 +
> Andy Burns wrote:
>
> > Jesse Barnes wrote:
> >
> > > Andy Burns wrote:
> > >
> > > There is a way to configure the gamut to be compressed (default) or
> > > expanded (up to 255). But that's not exposed eith
On Mon, 16 Jan 2012 21:57:29 +
Andy Burns wrote:
> On 16 January 2012 18:03, Jesse Barnes wrote:
>
> > There is some 30 bit support in place, but not 36bpp, which is what
> > HDMI sinks generally want.
>
> I did a little experiment, adding a Depth 30 setting to the Display
> SubSection for
On Mon, 16 Jan 2012 21:50:22 +
Andy Burns wrote:
> Jesse Barnes wrote:
>
> > Andy Burns wrote:
> >
> >> Similarly is there any setting to indicate an xvYCC gamut, which might
> >> persuade the amp not to clip the colours?
> >
> > There is a way to configure the gamut to be compressed (defa
On 16 January 2012 18:03, Jesse Barnes wrote:
> There is some 30 bit support in place, but not 36bpp, which is what
> HDMI sinks generally want.
I did a little experiment, adding a Depth 30 setting to the Display
SubSection for the Screen (and removing all lower depth entries) also
a DefaultDept
Jesse Barnes wrote:
> Andy Burns wrote:
>
>> Similarly is there any setting to indicate an xvYCC gamut, which might
>> persuade the amp not to clip the colours?
>
> There is a way to configure the gamut to be compressed (default) or
> expanded (up to 255). But that's not exposed either.
I see
Jesse Barnes wrote:
> Andy Burns wrote:
>
>> Is there any xorg.conf setting to switch the HDMI output to YCbCr mode
>> instead of RGB mode?
>
> No, we haven't exposed that yet. On some chipsets it may mean
> configuring colorspace conversion in the pipe code. Paulo has been
> looking at some o
On Sun, 15 Jan 2012 10:48:28 +
Andy Burns wrote:
> OK, enough scene-setting, here are the xorg questions ...
>
> Is there any xorg.conf setting to switch the HDMI output to YCbCr mode
> instead of RGB mode?
No, we haven't exposed that yet. On some chipsets it may mean
configuring colorspace
I have an ASUS P5E-VM HDMI motherboard which has GMA X3500 graphics
onboard, running Fedora 16, this is used as my mythTV frontend.
Previously the PC was connected directly to a Toshiba Regza 40ZF355DB
(which is an HDMI 1.3 device) and all was well including colour gamut
(RGB output with full 0..2
13 matches
Mail list logo
