linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	Dmitry Tunin <hanipouspilot@gmail.com>,
	Daniel Vetter <daniel@ffwll.ch>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Chris Wilson <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	jaime.91@hotmail.es, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Oleksij Rempel <linux@rempel-privat.de>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/opregion: work around buggy	firmware that provides 8+ output devices
Date: Tue, 09 Dec 2014 17:15:12 +0800	[thread overview]
Message-ID: <5486BDA0.3000801@intel.com> (raw)
In-Reply-To: <87388qo119.fsf@intel.com>

On 12/08/2014 07:04 PM, Jani Nikula wrote:
> On Mon, 08 Dec 2014, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> On Mon, 08 Dec 2014, Aaron Lu <aaron.lu@intel.com> wrote:
>>> We have a new bug report that has the same problem:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=88941
>>>
>>> The posted patch solves the problem. I know it's not perfect, but it
>>> doesn't seem it would do any harm to existing systems so should be safe.
>>>
>>> Better, if someone can shed some light on how this should be properly
>>> handled, that would be great.
>>
>> There was a bug report that I can't find right now that had a similar
>> problem. I wrote a few patches, even somewhat polished ones (that I now
>> pushed to [1] for reference) to handle extended DIDL. Unfortunately this
>> didn't help the bug reporter because the right one was beyond the
>> extended DIDL too, so I don't think I even sent these to the list.
>>
>> Anyway, just one more data point. This might help your reporter, so
>> worth a try. But it doesn't solve everything.
> 
> [1] http://cgit.freedesktop.org/~jani/drm/log/?h=didl

Thanks for the info, I've asked Dmitry to give it a try.

Regards,
Aaron


      reply	other threads:[~2014-12-09  9:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  3:05 [PATCH] drm/i915/opregion: work around buggy firmware that provides 8+ output devices Aaron Lu
2014-02-12 10:31 ` Chris Wilson
2014-02-12 10:52   ` Jani Nikula
2014-02-13  9:10   ` Aaron Lu
2014-02-13 10:08     ` Chris Wilson
2014-02-13 12:03       ` Daniel Vetter
2014-02-19  7:31         ` Aaron Lu
2014-02-19  7:33           ` Matthew Garrett
2014-02-19  8:59             ` Aaron Lu
2014-03-04 14:45               ` Daniel Vetter
2014-12-08  1:58                 ` Aaron Lu
2014-12-08 11:00                   ` Jani Nikula
2014-12-08 11:04                     ` [Intel-gfx] " Jani Nikula
2014-12-09  9:15                       ` Aaron Lu [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=5486BDA0.3000801@intel.com \
    --to=aaron.lu@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=hanipouspilot@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jaime.91@hotmail.es \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@rjwysocki.net \
    /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).