From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mario.Limonciello@dell.com, dmitry.torokhov@gmail.com
Cc: jdelvare@suse.de, alex.hung@canonical.com, rjw@rjwysocki.net,
lenb@kernel.org, gregkh@linuxfoundation.org, davem@davemloft.net,
mika.westerberg@linux.intel.com, f.fainelli@gmail.com,
kishon@ti.com, karniksayli1995@gmail.com,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI / osi: add DMI quirk for Dell systems
Date: Tue, 06 Feb 2018 15:45:31 +0200 [thread overview]
Message-ID: <1517924731.22495.51.camel@linux.intel.com> (raw)
In-Reply-To: <e30274b31bda47c5972621607cf3b605@ausx13mpc120.AMER.DELL.COM>
On Tue, 2018-02-06 at 00:45 +0000, Mario.Limonciello@dell.com wrote:
> > > > Playing with OSI string is a bad idea. I wouldn't do anything
> > > > while
> > > > Rafael, or even Len can confirm that is the right thing to do.
> > > >
> > > > For me, AFAIK we need to be bug-to-bug compatible with Windows
> > > > (at least
> > > > on ACPICA side), so, what Windows exactly does on such laptops?
> > > >
> > >
> > > The issue that's being worked around isn't an ACPICA interpreter
> > > issue, but it's
> > > a graphics device configuration issue.
Then clearly nothing to do with OSI strings here, right?
> > > Windows expects to use RTD3 on the NVIDIA GPU but Linux drivers
> > > don't. It leads to system hangs on the Linux side.
> >
> > Can we adjust Linux drivers to do the right thing?
+100
> > Or is it regarding
> > the binary NVIDIA blob?
nVidia vs. Linux again? :-)
>
> Neither Nouveau nor the NVIDIA blob have support for RTD3.
>
> Last I heard it's waiting on NVIDIA releasing something Nouveau
> needs. So.. Eventually? For now it's better to not hang though.
Hmm... While you are talking sense, the patch itself looks like an ugly
hack.
> That's part of why we wanted to enable this via a transient OSI
> string,
> to let this be removed by Linux whenever the driver does grow support.
So, means "never" then? (Assume a bit of irony here)
I don't know how it feels for maintainers, for me it's quite unlikely to
go (at least in this shape).
I'm sorry I can't be much constructive here, I heard Len once about OSI
huge abuse by almost every party. I would rather let him speak on the
matter.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-02-06 13:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 8:40 [PATCH 1/2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches Alex Hung
2018-01-31 8:40 ` [PATCH 2/2] ACPI / osi: add DMI quirk for Dell systems Alex Hung
2018-02-05 13:14 ` Jean Delvare
2018-02-05 14:15 ` Andy Shevchenko
2018-02-05 17:36 ` Mario.Limonciello
2018-02-05 22:45 ` Dmitry Torokhov
2018-02-06 0:45 ` Mario.Limonciello
2018-02-06 13:45 ` Andy Shevchenko [this message]
2018-02-06 16:24 ` Mario.Limonciello
2018-02-07 20:38 ` Alex Hung
2018-02-07 20:49 ` Mario.Limonciello
2018-02-11 9:29 ` Rafael J. Wysocki
2018-02-11 13:45 ` Lukas Wunner
2018-02-12 9:49 ` Rafael J. Wysocki
2018-02-12 20:29 ` Mario.Limonciello
2018-02-12 22:57 ` Rafael J. Wysocki
2018-02-12 23:14 ` Mario.Limonciello
2018-02-13 5:25 ` Alex Hung
2018-02-13 7:32 ` Mika Westerberg
2018-02-14 9:06 ` Rafael J. Wysocki
2018-02-14 9:50 ` Mika Westerberg
2018-02-13 9:18 ` Rafael J. Wysocki
2018-02-13 9:55 ` Lukas Wunner
2018-02-14 9:10 ` Rafael J. Wysocki
2018-02-14 18:47 ` Mario.Limonciello
2018-02-15 9:44 ` Rafael J. Wysocki
2018-02-05 17:24 ` Mario.Limonciello
2018-02-05 21:55 ` Jean Delvare
2018-02-07 20:05 ` Alex Hung
2018-02-05 10:26 ` [PATCH 1/2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches Jean Delvare
2018-02-07 5:25 ` Alex Hung
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=1517924731.22495.51.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Mario.Limonciello@dell.com \
--cc=alex.hung@canonical.com \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.de \
--cc=karniksayli1995@gmail.com \
--cc=kishon@ti.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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).