From: Ike Panhc <ike.pan@canonical.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ideapad: No hardware switch after 2016
Date: Tue, 16 Feb 2016 01:05:26 +0800 [thread overview]
Message-ID: <56C20556.7040900@canonical.com> (raw)
In-Reply-To: <87r3gew4zw.fsf@nemi.mork.no>
On 02/15/2016 08:08 PM, Bjørn Mork wrote:
> Ike Panhc <ike.pan@canonical.com> writes:
>
>> There are complains on few ideapads that wireless is always hard
>> blocked but there is no physical radio switch. For now, we need
>> each user to report its dmi information and ignore hard blocks
>> on their ideapad. With more and more ideapads available in market
>> to maintain the dmi table becomes never-ended job.
>>
>> I've checked lenovo website and for recent design none of the
>> ideapads has radio switch. I do not believe there will be in the
>> future. Therefore to disable hard block according to BIOS date is
>> reasonable approach.
>>
>> This patch will disable rfkill hardblock if BIOS year > 2015.
>
> Huh? And what happens when a user upgrades the BIOS on older hardware?
>
That's why I believe > 2015 is a better choice, not > 2014.
Ideapads in market now carries BIOS year 2015 and I found no radio switch
on them. And I don't believe anyone will receive or upgrade BIOS for more
then 1y old machine. In fact I haven't heard anyone upgrading BIOS for a
long time.
--
Ike Panhc
next prev parent reply other threads:[~2016-02-15 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 10:23 [PATCH v2 0/2] Disable rfkill hardblock if BIOS date > 2016 Ike Panhc
2016-02-15 10:24 ` [PATCH 1/2] ideapad: No hardware switch after 2016 Ike Panhc
2016-02-15 12:08 ` Bjørn Mork
2016-02-15 17:05 ` Ike Panhc [this message]
2016-02-15 17:32 ` Bjørn Mork
2016-02-16 2:04 ` Ike Panhc
2016-02-17 7:15 ` Darren Hart
2016-02-15 10:24 ` [PATCH 2/2] ideapad: show has_hw_rfkill_switch in debugfs Ike Panhc
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=56C20556.7040900@canonical.com \
--to=ike.pan@canonical.com \
--cc=bjorn@mork.no \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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