[git pull] drm tree for 3.12-rc1

[Sean V Kelley]

On Tue, Sep 10, 2013 at 1:50 PM, Sean V Kelley <sean.v.kelley at intel.com> wrote:
> On Tue, Sep 10, 2013 at 08:49:58AM -0700, Linus Torvalds writes :
>> [ Dave - your linux.ie email generates bounces for me, trying redhat instead ]
>>
>> On Mon, Sep 9, 2013 at 11:25 PM, Sean V Kelley <sean.v.kelley at intel.com> wrote:
>> >>
>> >> I'm also a bit bummed that hw acceleration of video doesn't seem to
>> >> work on Haswell, meaning that full-screen is now a jerky mess. I fear
>> >> that that is user-space libraries/X.org, but I thought I'd mention it
>> >> in the hope of getting a "oh, it's working for us, you'll get a fix
>> >> for it soon".
>> >
>> > Can you give a little more detail about video not working?  Video
>> > accel should work fine with the current versions of libva/intel-driver
>> > available in Fedora 19 - assuming that's what you're using.
>>
>> It is indeed F19.
>>
>> Easy test: go to youtube, and watch things that are in 1080p HD. They
>> play fine in a window (using about 70% CPU), but full-screened to
>> 2560x1440 they play at about one or two frames per second.
>
> Yep.  I see the same.  Chrome is brain dead and appears to simply
> rely on Flash + FFmpeg software codecs.  At least with Firefox you
> know it will suck and not be hw accelerated. Unless that has changed...
>
....
>
> Ironically, it is relatively trivial for me to do a chromium browser
> build form source myself and enable libva/intel-driver HW accel, h.264.  And say
> screw you to flash et al, and leave that out.  And that will
> work fine for html5 video on youtube with fallback to SW accel for VP8
> based content.  Why it is a chore for Google is not clear to me...


Google actually blacklists hardware video acceleration for Linux x86
in Chromium.  My
builds are based on ChromeOS' browser.  That's how I get around it.

For more details...
https://codereview.chromium.org/16430003/

Sean


>
> Sean
>
>>
>> My previous i5-670 which was inferior in almost every other way didn't
>> have these problems.. It had the same 2560x1440 display.
>>
>>               Linus



-- 
Sean V. Kelley <sean.v.kelley at intel.com>
Open Source Technology Center / SSG
Intel Corp.