public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Jerone Young <jerone.young@canonical.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] [RESUBMIT] Fix mute key on older Lenovo made Thinkpads by OSI blacklisting
Date: Wed, 19 May 2010 23:34:05 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1005192325470.2921@localhost.localdomain> (raw)
In-Reply-To: <1272770432.15493.49.camel@laptop>

Hello Jerone,

Thanks for working to make Linux users with these systems happier.

As you know, we really really hate to add OSI(Linux) hooks
because the OSI string "Linux" is not an appropriate OSI string
as it doesn't describe a single interface, or even version of Linux...

Thus in the upstream kernel, we have shipped with OSI(Linux) disabled
since 2.6.23. 

The risk of restoring OSI(Linux) is that BIOS writers will
not realize that they have a BIOS bug when they use it
and the abuse and risk of bugs will become unbounded.

Of course for systems that have shipped already, the damage
is done -- and that seems to be the case here.

So the question I have is if OSI(Linux) *only* changes the
mute button on these boxes, or if it has any other effects.
Generally we need to examine the DSDT for each box to know.
Do you have the DSDT's for these boxes?

thanks,
Len Brown, Intel Open Source Technology Center

>                      DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad T500"),
>                 },
>         },
> +       {
> +       .callback = dmi_enable_osi_linux,
> +       .ident = "Lenovo ThinkPad X200[s][t]",
> +       .matches = {
> +                    DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> +                    DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad X200"),
> +               },
> +       },
> +       {
> +       .callback = dmi_enable_osi_linux,
> +       .ident = "Lenovo ThinkPad R400",
> +       .matches = {
> +                    DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> +                    DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad R400"),
> +               },
> +       },
> +       {
> +       .callback = dmi_enable_osi_linux,
> +       .ident = "Lenovo ThinkPad R500",
> +       .matches = {
> +                    DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> +                    DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad R500"),
> +               },
> +       },
> +       {
> +       .callback = dmi_enable_osi_linux,
> +       .ident = "Lenovo ThinkPad W500",
> +       .matches = {
> +                   DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> +                   DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad W500"),
> +               },
> +       },
> +       {
> +       .callback = dmi_enable_osi_linux,
> +       .ident = "Lenovo ThinkPad W700[ds]",
> +       .matches = {
> +                  DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> +                  DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad W700"),
> +               },
> +       },
>         {}
>  };
>  
> 
> 
> 
> 

  reply	other threads:[~2010-05-20  3:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02  3:20 [PATCH] [RESUBMIT] Fix mute key on older Lenovo made Thinkpads by OSI blacklisting Jerone Young
2010-05-20  3:34 ` Len Brown [this message]
     [not found]   ` <1274329374.4479.403.camel@laptop>
2010-05-20  5:48     ` Len Brown
2010-05-20 19:14       ` Henrique de Moraes Holschuh

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=alpine.LFD.2.00.1005192325470.2921@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=jerone.young@canonical.com \
    --cc=linux-acpi@vger.kernel.org \
    /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