rfkill is a module in the linux kernel that can kill all radio signals. So,
it controls every bluetooth, wifi, gps and gsm device. The fact that Android
use all that kind of devices makes rfkill a logical choise for Android to
use.
Peter
2010/3/12 pavan savoy
> Why not the chip manufacturers d
Why not the chip manufacturers decide - how best to turn on their chip and
move the system/bluetooth/bluedroid project under hardware/libhardware 'ala
wifi, so that manufacturer is free to have his own functions.
regards,
Pavan
On Thu, Mar 11, 2010 at 7:12 PM, Nick Pelly wrote:
> What do you su
What do you suggest as an alternative?
On Thu, Mar 11, 2010 at 2:15 PM, pavan savoy wrote:
> Android when it wants to turn BT on, write's 1 onto the rfkill entry (which
> has type bluetooth),
> and up until now this is the reason we had wl127x_rfkill.c on OMAP or
> board-*-rfkill.c on MSM.
>
> Ho
Android when it wants to turn BT on, write's 1 onto the rfkill entry (which
has type bluetooth),
and up until now this is the reason we had wl127x_rfkill.c on OMAP or
board-*-rfkill.c on MSM.
However a hci_register_dev from 2.6.32 also creates and rfkill entry by the
same type - bluetooth.
Now bo