[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hogSM3OgfJ0GFn7+BYwxR05Hb5ZMLo=NiB2wmpu=qeug@mail.gmail.com>
Date: Mon, 21 Oct 2019 10:14:03 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Alex Hung <alex.hung@...onical.com>,
Karol Herbst <kherbst@...hat.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Dave Airlie <airlied@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
nouveau <nouveau@...ts.freedesktop.org>,
Mario Limonciello <mario.limonciello@...l.com>,
Ben Skeggs <bskeggs@...hat.com>,
Dave Airlie <airlied@...hat.com>
Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to
enable dGPU direct output"
On Mon, Oct 21, 2019 at 4:14 AM Alex Hung <alex.hung@...onical.com> wrote:
>
> We have done some tests on three of Intel + nVidia configuration
> systems with OEM _OSI strings removed - while some bugs are still
> observed, ex. one out of three has suspend/resume issues, no system
> crashes were observed - the biggest issue that worries us.
>
> The positive results give us confident to ack the removal of the OEM
> _OSI strings. While our tests were not able to cover all possible I+N
> systems, we are sure we can fix issues along the way. If there aren't
> systems that cannot be fixed without these OEM _OSI strings, these
> strings should probably enable with DMI quirks (possible future
> patches) so they won't affect others.
>
> Acked-by: Alex Hung <alex.hung@...onical.com>
OK, thanks!
I can queue this up or if it's better to route it through the DRM
tree, please do that (and let me know).
Powered by blists - more mailing lists