Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756151AbaLIJPY (ORCPT ); Tue, 9 Dec 2014 04:15:24 -0500 Received: from mga09.intel.com ([134.134.136.24]:30077 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754980AbaLIJPV (ORCPT ); Tue, 9 Dec 2014 04:15:21 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,691,1406617200"; d="scan'208";a="495920277" Message-ID: <5486BDA0.3000801@intel.com> Date: Tue, 09 Dec 2014 17:15:12 +0800 From: Aaron Lu MIME-Version: 1.0 To: Jani Nikula , Dmitry Tunin , Daniel Vetter , Matthew Garrett , Chris Wilson CC: "intel-gfx@lists.freedesktop.org" , jaime.91@hotmail.es, "Rafael J. Wysocki" , "linux-kernel@vger.kernel.org" , Oleksij Rempel , ACPI Devel Mailing List Subject: Re: [Intel-gfx] [PATCH] drm/i915/opregion: work around buggy firmware that provides 8+ output devices References: <52FAE504.8020001@intel.com> <20140212103156.GC5298@nuc-i3427.alporthouse.com> <52FC8C01.1040002@intel.com> <20140213100814.GM14909@nuc-i3427.alporthouse.com> <53045DD1.5010406@intel.com> <20140219073339.GA30685@srcf.ucam.org> <5304725A.3020909@intel.com> <20140304144504.GE17001@phenom.ffwll.local> <548505D2.8030904@intel.com> <8761dmo17c.fsf@intel.com> <87388qo119.fsf@intel.com> In-Reply-To: <87388qo119.fsf@intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/08/2014 07:04 PM, Jani Nikula wrote: > On Mon, 08 Dec 2014, Jani Nikula wrote: >> On Mon, 08 Dec 2014, Aaron Lu 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/