From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Paulo Zanoni <paulo.r.zanoni@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
"Beauchesne, Gwenole" <gwenole.beauchesne@intel.com>,
Sean V Kelley <sean.v.kelley@intel.com>
Subject: Re: [git pull] drm tree for 3.12-rc1
Date: Thu, 5 Sep 2013 15:32:43 -0700 [thread overview]
Message-ID: <20130905153243.43d0346e@jbarnes-desktop> (raw)
In-Reply-To: <CA+55aFwyKmVWkrV3=XiuruZzeTicpfW-JrwjWzpq9eP2yGPeJA@mail.gmail.com>
On Thu, 5 Sep 2013 12:18:32 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, Sep 5, 2013 at 3:41 AM, Dave Airlie <airlied@linux.ie> wrote:
> >
> > i915: Haswell PC8+ support and eLLC support, HDMI 4K support, initial per-process VMA pieces,
> > watermark reworks, convert to generic hdmi infoframes, encoder reworking, fastboot support,
>
> Hmm.
>
> The first time I booted this, I just got a black screen on my Haswell
> desktop when X11 started up. I could ctrl-alt-BS and ctrl-alt-del to
> reboot the machine, and neither the Xorg.0.log nor the dmesg contained
> anything interesting.
Did the console come back after ctl-alt-bs? Or was it just a blind
reboot? Troubling that it doesn't happen again...
> I was about to try to bisect it, but decided to see how repeatable it
> was, and it didn't happen again. But it also hasn't ever happened
> before, so I'm a bit worried.
>
> This is with the DP cable, which has made my other Haswell issues go away.
>
> 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".
AFAIK we have libva support out there for HSW. The trick is getting
your stack to actually use it. Gwenole or Sean may be able to help.
> Because my shiny new 65W haswell is really nice and does a "make
> allmodconfig" in half the time of my old machine, but the GPU side has
> been something of a step backwards...
Well we definitely don't want that...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-09-05 22:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 10:41 [git pull] drm tree for 3.12-rc1 Dave Airlie
2013-09-05 19:18 ` Linus Torvalds
2013-09-05 22:02 ` Dave Airlie
2013-09-05 22:32 ` Jesse Barnes [this message]
2013-09-05 22:51 ` Linus Torvalds
2013-09-05 23:01 ` Linus Torvalds
2013-09-05 23:19 ` Linus Torvalds
2013-09-06 0:56 ` Linus Torvalds
2013-09-10 8:16 ` Benjamin Tissoires
2013-09-10 6:25 ` Sean V Kelley
2013-09-10 15:49 ` Linus Torvalds
2013-09-10 16:06 ` Mike Lothian
2013-09-10 20:50 ` Sean V Kelley
2013-09-10 23:18 ` Sean V Kelley
2013-09-10 23:23 ` Dave Airlie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130905153243.43d0346e@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gwenole.beauchesne@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulo.r.zanoni@intel.com \
--cc=sean.v.kelley@intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).