On Tue, Dec 01, 2009 at 10:24:30AM +0530, pavan savoy wrote: > When I meant android specific, I meant that it is only android that is > making use of an rfkill entry to toggle the BT Chip enable GPIO line. > Example: In other linux-bluetooth stacks (including blueZ on a busybox > sort of FS), this can be done via an sysfs entry or BT driver itself > or have it high @ boot in one of the board-*.c files from arch/*/... > directory.
I'm not sure which system you're looking at here but there's embedded boards in mainline which use rfkill for Bluetooth (eg, tosa) - the fact that some things have managed to get merged without using the standard interfaces shouldn't prevent new users using the standard interfaces. > Also, Nick -- Should I be migrating to 2.6.32 ? to upstream this patch to > lkml ? > there are some HUGE changes to 2.6.32 rfkill sub-system !!! Yes, upstream will only be interested in something for a current kernel. IIRC a lot of the restructuring you're looking at was actually largely about making things nicer for non-WiFi rfkill users. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
