public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Wei Shun Chang <wei.shun.chang@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: add LynxPoint-LP PCH ID
Date: Tue, 13 Nov 2012 00:29:14 +0100	[thread overview]
Message-ID: <20121112232914.GR5854@phenom.ffwll.local> (raw)
In-Reply-To: <20121112232429.GA18140@jtriplet-mobl1>

On Mon, Nov 12, 2012 at 03:24:29PM -0800, Josh Triplett wrote:
> On Tue, Nov 13, 2012 at 12:04:53AM +0100, Daniel Vetter wrote:
> > On Mon, Nov 12, 2012 at 06:54:13PM -0200, Paulo Zanoni wrote:
> > > From: Wei Shun Chang <wei.shun.chang@intel.com>
> > > 
> > > [pzanoni: rebase, print it's an LP PCH]
> > > 
> > > Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/i915_drv.c |    6 ++++++
> > >  1 file changed, 6 insertions(+)
> > > 
> > > 
> > > I can't test the patch since I don't have the LP PCH.
> > 
> > Including Josh, since he has such a machine.
> 
> Tested-by: Josh Triplett <josh@joshtriplett.org>

Merged, thanks for testing&patch.

> With this patch, I can boot and run on such a board.  I do get an odd
> kernel gripe, though: "More than 8 outputs detected".

That's just our fake opregion code complaining. Most likely a devboard
artefact, since those just enable everything.

-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2012-11-12 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 20:54 [PATCH] drm/i915: add LynxPoint-LP PCH ID Paulo Zanoni
2012-11-12 23:04 ` Daniel Vetter
2012-11-12 23:24   ` Josh Triplett
2012-11-12 23:29     ` Daniel Vetter [this message]

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=20121112232914.GR5854@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=josh@joshtriplett.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=wei.shun.chang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox