I am sorry, I do not understand anything from the below technical message.
Does this mean that the only solution is to cover pin13?
Can't it be done with ath5k? It was working fine with ath_pci. So the
code in ath_pci exists.
It can't be so difficult to fix...
Antonis.
Στις 04/08/2011 01:58
2011/8/4 Nick Kossifidis mickfl...@gmail.com:
2011/8/3 Pavel Roskin pro...@gnu.org:
On 08/03/2011 08:42 AM, Antonis Tsolomitis wrote:
Yes I have tried this. It still is hardware blocked:
Antonis.
# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
# rfkill
You could just look at the code in ath5k/rfkill.c and just comment out
the code that glues together the rfkill GPIO pin to the rfkill
personality.
(ie, GPIO pins have personalities, they can be configured as input,
output, rfkill to the baseband, other stuff..)
If the pin isn't configured as
