From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: skylake + drm-next - warn city
Date: Tue, 3 Nov 2015 12:47:05 +0200 [thread overview]
Message-ID: <20151103104705.GR4437@intel.com> (raw)
In-Reply-To: <1446546958.23409.11.camel@intel.com>
On Tue, Nov 03, 2015 at 12:35:58PM +0200, Imre Deak wrote:
> On ti, 2015-11-03 at 11:42 +0200, Jani Nikula wrote:
> > On Tue, 03 Nov 2015, Dave Airlie <airlied@gmail.com> wrote:
> > > Just booted drm-next on a Skylake laptop that happened to be on my
> > > desk for a few days.
> > >
> > > I wasn't impressed. I'm very disappointed. Doesn't anyone have any
> > > pride in the code they write anymore.
> > >
> > > Initially the previous sentence had a lot of curse words and was Linus
> > > like in it's stature, but I've been promised by twitter that being
> > > nice will get me better results, so let's make it so.
> >
> > Much appreciated; we get the message.
> >
> > > So could someone from Intel takes some responsibility for testing the
> > > code they send me actually you know works on the hardware it's meant
> > > to, or at least tell me what is going so horribly wrong here.
> > >
> > > the lockdep trace at the end doesn't look fun.
>
> That's from the GuC firmware loader, so won't be fixed by the DMC
> patches. Ville mentioned he has a fix for that.
No, I don't. I probably just mentioned that I saw this lockdep spew
already some weeks ago, and complained about it at the time. I think
Daniel tried to ping someone specific about it, but no idea if they
took any notice.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-03 10:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 22:51 skylake + drm-next - warn city Dave Airlie
2015-11-03 9:42 ` Jani Nikula
2015-11-03 10:35 ` Imre Deak
2015-11-03 10:47 ` Ville Syrjälä [this message]
2015-11-03 20:07 ` Dave Airlie
2015-11-03 21:23 ` Jesse Barnes
2015-11-03 21:21 ` Patrik Jakobsson
2015-11-03 21:47 ` Daniel Stone
2015-11-03 22:08 ` Patrik Jakobsson
2015-11-04 17:11 ` Daniel Stone
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=20151103104705.GR4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.