linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* ath6kl_sdio blocked by RFKILL
@ 2013-05-28 15:01 Ulf Samuelsson
  2013-06-01 12:34 ` Kalle Valo
  0 siblings, 1 reply; 3+ messages in thread
From: Ulf Samuelsson @ 2013-05-28 15:01 UTC (permalink / raw)
  To: linux-wireless; +Cc: ath6kl-devel

Have built the ath6kl_sdio driver for an Cortex-A5 chip using the 
linux-3.6.9 kernel
File system built using Yocto  and Busybox RF-Kill.

Kernel Config contains:

CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not set

When I do

# ifconfig wlan0 up.

I get the error message:

ifconfig: SIOCSIFFLAGS: Operation not possible due to RF-kill

If I run "rfkill list" I get

1: phy1: wlan
         Soft blocked: yes
         Hard blocked: no


If I try to unblock using "rfkill unblock all" or "wifi" or "wlan", the 
soft block remains.

Any clues?

Looking through the Busybox rfkill code, this seems to generate an event.
What is supposed to react to this?
Could there be a rule, which is missing?

BR
Ulf Samuelsson

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: ath6kl_sdio blocked by RFKILL
  2013-05-28 15:01 ath6kl_sdio blocked by RFKILL Ulf Samuelsson
@ 2013-06-01 12:34 ` Kalle Valo
  2013-06-05 11:17   ` Ulf Samuelsson
  0 siblings, 1 reply; 3+ messages in thread
From: Kalle Valo @ 2013-06-01 12:34 UTC (permalink / raw)
  To: Ulf Samuelsson; +Cc: linux-wireless, ath6kl-devel

Ulf Samuelsson <ntp@emagii.com> writes:

> Have built the ath6kl_sdio driver for an Cortex-A5 chip using the
> linux-3.6.9 kernel
> File system built using Yocto  and Busybox RF-Kill.
>
> Kernel Config contains:
>
> CONFIG_RFKILL=m
> CONFIG_RFKILL_LEDS=y
> CONFIG_RFKILL_INPUT=y
> # CONFIG_RFKILL_GPIO is not set
>
> When I do
>
> # ifconfig wlan0 up.
>
> I get the error message:
>
> ifconfig: SIOCSIFFLAGS: Operation not possible due to RF-kill
>
> If I run "rfkill list" I get
>
> 1: phy1: wlan
>         Soft blocked: yes
>         Hard blocked: no
>
>
> If I try to unblock using "rfkill unblock all" or "wifi" or "wlan",
> the soft block remains.

Have you tried "rfkill unblock 1"?

-- 
Kalle Valo

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: ath6kl_sdio blocked by RFKILL
  2013-06-01 12:34 ` Kalle Valo
@ 2013-06-05 11:17   ` Ulf Samuelsson
  0 siblings, 0 replies; 3+ messages in thread
From: Ulf Samuelsson @ 2013-06-05 11:17 UTC (permalink / raw)
  To: Kalle Valo; +Cc: linux-wireless, ath6kl-devel

On 2013-06-01 14:34, Kalle Valo wrote:
> Ulf Samuelsson <ntp@emagii.com> writes:
>
>> Have built the ath6kl_sdio driver for an Cortex-A5 chip using the
>> linux-3.6.9 kernel
>> File system built using Yocto  and Busybox RF-Kill.
>>
>> Kernel Config contains:
>>
>> CONFIG_RFKILL=m
>> CONFIG_RFKILL_LEDS=y
>> CONFIG_RFKILL_INPUT=y
>> # CONFIG_RFKILL_GPIO is not set
>>
>> When I do
>>
>> # ifconfig wlan0 up.
>>
>> I get the error message:
>>
>> ifconfig: SIOCSIFFLAGS: Operation not possible due to RF-kill
>>
>> If I run "rfkill list" I get
>>
>> 1: phy1: wlan
>>          Soft blocked: yes
>>          Hard blocked: no
>>
>>
>> If I try to unblock using "rfkill unblock all" or "wifi" or "wlan",
>> the soft block remains.
> Have you tried "rfkill unblock 1"?
>

Yes, I have now been able to reproduce on another board.

The System has an MMC connector, and if I boot with my SD51 SDIO card in 
the connector, then

"rfkill unblock <x>"

won't work, with x = {all,wifi,1 ...}

If I boot without the SD51 card beeing inserted, and then insert if 
after theboot has been completed,
then rfkill works as expected.

The MMC host driver is  built as a module, maybe it shouldn't.

BR
Ulf Samuelsson

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-06-05 11:24 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-28 15:01 ath6kl_sdio blocked by RFKILL Ulf Samuelsson
2013-06-01 12:34 ` Kalle Valo
2013-06-05 11:17   ` Ulf Samuelsson

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).