From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: Jean-Louis Dupond <jean-louis@dupond.be>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Mario Limonciello <mario_limonciello@dell.com>,
Kamal Mostafa <kamal@canonical.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dell-laptop: rfkill blacklist Dell XPS 13z, 15z
Date: Tue, 15 May 2012 17:05:54 +0200 [thread overview]
Message-ID: <4FB270D2.8030705@fold.natur.cuni.cz> (raw)
In-Reply-To: <4FB182BB.6090303@dupond.be>
Jean-Louis Dupond wrote:
> Hi
>
> I'm the owner of a XPS 15, which has this issue.
> The best solution would indeed be to solve the real bug, and not work
> around it in Linux.
>
> But still, if we can fix it with rather small impact/code on linux, I
> think we should just do it.
> It makes linux more user friendly this way.
>
> A small remark also:
> Is it really possible to disable bluetooth without killing wifi in
> Windows on the XPS?
I rebooted into Win7. You are right, on this Dell Vostro 3550 the Fn+F2 has
only two states: turn on both BT+WiFi or turn both off. My old ASUS laptop
had 3 states and I could turn off independently BT while not WiFi. ;)
So, rfkill application on Linux behaves in the same way as the Fn+F2 in Linux
and in Win 7.
Martin
next prev parent reply other threads:[~2012-05-15 15:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 19:27 Kamal Mostafa
2012-05-14 19:37 ` Matthew Garrett
2012-05-14 20:00 ` Kamal Mostafa
2012-05-14 20:08 ` Mario Limonciello
2012-05-14 21:19 ` Matthew Garrett
2012-05-14 21:21 ` Mario Limonciello
2012-05-14 21:28 ` Matthew Garrett
2012-05-14 21:48 ` Mario Limonciello
2012-05-14 21:55 ` Matthew Garrett
2012-05-14 22:10 ` Jean-Louis Dupond
2012-05-15 15:05 ` Martin Mokrejs [this message]
2012-05-14 20:02 ` Martin Mokrejs
2012-05-14 20:03 ` [PATCH v2] dell-laptop: rfkill blacklist Dell XPS 13z, 15 Kamal Mostafa
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=4FB270D2.8030705@fold.natur.cuni.cz \
--to=mmokrejs@fold.natur.cuni.cz \
--cc=jean-louis@dupond.be \
--cc=kamal@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=mjg59@srcf.ucam.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
all inboxes | Powered by JetHome®