From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Matthew Garrett <mjg@redhat.com>,
linux acpi <linux-acpi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hp-wmi: improve rfkill support
Date: Thu, 23 Jul 2009 17:31:45 +0200 [thread overview]
Message-ID: <8db1092f0907230831w1255d0bey951342fb61b67c1e@mail.gmail.com> (raw)
In-Reply-To: <4A65A2F9.1060509@tuffmail.co.uk>
2009/7/21 Alan Jenkins <alan-jenkins@tuffmail.co.uk>:
> 1) Add support for reading the hardware blocked state. Previously
> we read a combination of the hardware and software blocked states,
> reporting it as the software blocked state. This caused some
> confusing behaviour.
>
> 2) The software state is persistent, mark it as such.
>
> 3) Check rfkill in the resume handler. Both the hard and soft
> blocked states may change over hibernation.
>
> Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
> Tested-by: Maciej Rutecki <maciej.rutecki@gmail.com>
It's this patch is added to -rc4? I one case I have strange behaviour.
Before disable by button:
root@gumis:/home/maciek/Desktop# rfkill list
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
16: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
17: phy7: Wireless LAN
Soft blocked: no
Hard blocked: no
Disable by button:
root@gumis:/home/maciek/Desktop# rfkill list
2: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
17: phy7: Wireless LAN
Soft blocked: no
Hard blocked: yes
I do s2disk. After resume from suspend to disk (still disabled by button):
root@gumis:/home/maciek/Desktop# rfkill list
2: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
18: phy8: Wireless LAN
Soft blocked: no
Hard blocked: yes
Try enable by button:
root@gumis:/home/maciek/Desktop# rfkill list
2: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
18: phy8: Wireless LAN
Soft blocked: no
Hard blocked: yes
Nothing change (LED, wireless and bluetooth don't work). To enable it
I use this script rfkill.sh (I must use rfkill program):
#!/bin/sh
PROGRAM=/usr/local/sbin/rfkill
WIFI=`$PROGRAM list | grep -E 'Wireless|Bluetooth' | cut -d ':' -f 1`
for DEVICE in $WIFI; do
echo $DEVICE
$PROGRAM unblock $DEVICE
done
Then works OK:
root@gumis:/home/maciek/Desktop# ./rfkill.sh
2
3
18
root@gumis:/home/maciek/Desktop# rfkill list
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
18: phy8: Wireless LAN
Soft blocked: no
Hard blocked: no
19: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
It's normal behaviour?
--
Maciej Rutecki
http://www.maciek.unixy.pl
next prev parent reply other threads:[~2009-07-23 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 11:14 Alan Jenkins
2009-07-21 11:26 ` Matthew Garrett
2009-07-23 15:31 ` Maciej Rutecki [this message]
2009-07-23 18:27 ` Alan Jenkins
2009-07-23 19:36 ` Maciej Rutecki
2009-07-23 19:28 ` Frans Pop
2009-12-10 4:53 ` Len Brown
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=8db1092f0907230831w1255d0bey951342fb61b67c1e@mail.gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
/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®