[git pull] drm tree for 3.12-rc1
Sean V Kelley
sean.v.kelley at intel.com
Tue Sep 10 13:50:27 PDT 2013
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...
> Non-HD content seems to be fine even full-screen. Either just because
> it's so much easier to do, or because some level of scaling is
SD content should be relatively fine with software codecs. Ideally,
full-screen would disable composition and use hw-overlay in addition
to an actual hw accel codec, h.264 or vp8 for html5 video. But that
is not the case. That being said HSW does not support vp8 hw decode.
> It may well be that I'm using chrome (and chrome seems to tend to use
> its own library versions), and firefox indeed seems to be a bit
> better. But by "a bit better" I mean closer to full frame rate in
> full-screen, but lots of tearing - and it was stil using 70% CPU when
> displaying in a window. So I think firefox is also still doing
> everything in software but may be better about using threads for it.
Sadly none of those would be hw accel without some specific flavor
of flash plugin that favors hw accel over FFmpeg software accel (i.e.,
has older flash + wrapper for vdpau or vaapi). As someone else in this
thread mentioned, it is quite a pain in the arse.
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...
> My previous i5-670 which was inferior in almost every other way didn't
> have these problems.. It had the same 2560x1440 display.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: not available
More information about the dri-devel