linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Takashi Iwai <tiwai@suse.de>, Len Brown <lenb@kernel.org>,
	Oliver Neukum <oneukum@suse.de>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models
Date: Tue, 14 Jan 2014 16:42:27 +0000	[thread overview]
Message-ID: <20140114164227.GA7752@srcf.ucam.org> (raw)
In-Reply-To: <4325437.Itfr0xDDg7@vostro.rjw.lan>

On Tue, Jan 14, 2014 at 05:53:20PM +0100, Rafael J. Wysocki wrote:
> On Tuesday, January 14, 2014 04:34:25 PM Matthew Garrett wrote:
> > rfkill and backlight control presumably work fine under Windows 8, so 
> > there's obviously some new mechanism for doing so. HP will presumably 
> > ship more hardware that behaves this way, so if we don't add support for 
> > the new mechanisms then we'll just have to keep adding entries to the 
> > blacklist.
> 
> Well, presumably.
> 
> To add any kind of support for anything we need to know how that thing
> works in the first place which we don't in this particular case, at least
> at the moment.  I hontestly don't want the users of those systems to wait
> until we figure that out.

Adding blacklist entries without making some effort to figure out what 
the underlying problem is doesn't provide any incentive for fixing the 
underlying problem. In this case Toshio has described what the problem 
is and it sounds like fixing the rfkill problem is straightforward, so 
we should just classify this in the same way as all the other backlight 
control issues. Perhaps we should add it to the native video blacklist 
rather than the OSI one?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

      reply	other threads:[~2014-01-14 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 11:14 [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models Takashi Iwai
2014-01-13 11:46 ` Rafael J. Wysocki
2014-01-13 11:33   ` Takashi Iwai
2014-01-14 16:12 ` Matthew Garrett
2014-01-14 16:33   ` Takashi Iwai
2014-01-14 16:36     ` Matthew Garrett
2014-01-14 16:43       ` Takashi Iwai
2014-01-14 16:44         ` Matthew Garrett
2014-01-14 16:42   ` Rafael J. Wysocki
2014-01-14 16:34     ` Matthew Garrett
2014-01-14 16:53       ` Rafael J. Wysocki
2014-01-14 16:42         ` Matthew Garrett [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=20140114164227.GA7752@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=rjw@rjwysocki.net \
    --cc=tiwai@suse.de \
    /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).