Hi Pavan, I dnt think that Zoom1 / LDp doesn't have an inbuilt Bluetooth module.
Its "product brief and schematics " document clearly mention that zoom1 has an inbuilt + Built-in Bluetooth 2.0 + EDR So can you please confirm this ? Thanks & Regards Nimit On Tue, Apr 21, 2009 at 8:20 PM, pavan savoy <[email protected]> wrote: > Hi deepak, > > Please have a look in > > http://git.omapzoom.org/?p=repo/omapkernel.git;a=blob;f=drivers/misc/wl127x_power.c;h=a452eb41252fa0a88a077b4457145b77893e86cc;hb=refs/heads/android-2.6.27 > > for the relevant driver, as far as I know, zoom1 or ldp1 as its called, > doesn't have an on-board bt device, and the gpio line to enable BT chip > would solely depend on how the BT chip is connected to ldp1. > [are you using exp board+exp connector+carrier brd combo ?] > > > regards, > Pavan > > > On Tue, Apr 21, 2009 at 12:23 AM, deepak singal <[email protected]>wrote: > >> >> Hi NicK, >> >> When I am trying to turn on Bluetooth on ZOOM1(3430) board, using below >> init.rc changes : >> >> ######################################################## >> >> mkdir /data/misc/hcid 0770 bluetooth bluetooth >> chown bluetooth bluetooth /sys/class/rfkill/rfkill0/typeecho >> chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state >> chmod 0660 /sys/class/rfkill/rfkill0/state >> >> chmod 0660 /dev/ttyS1 >> chown bluetooth bluetooth /dev/ttyS1 >> >> service dbus /system/bin/dbus-daemon --system --nofork >> socket dbus stream 660 bluetooth bluetooth >> user bluetooth >> group bluetooth net_bt_admin >> >> #STOPSHIP: disable the verbose logging >> service hcid /system/bin/logwrapper /system/bin/hcid -d -s -n -f >> /etc/bluez/hcid.confsocket bluetooth stream 660 bluetooth bluetooth >> socket dbus_bluetooth stream 660 bluetooth bluetooth >> # init.rc does not yet support applying capabilities, so run as root >> and >> # let hcid drop uid to bluetooth with the right linux capabilities >> group bluetooth net_bt_admin misc >> disabled >> oneshot >> >> service hciattach /system/bin/hciattach -n -s 115200 /dev/ttyS1 texas >> 115200 flow >> user bluetooth >> group bluetooth net_bt_admin misc >> disabled >> oneshot >> >> service hfag /system/bin/sdptool add --channel=10 HFAG >> user bluetooth >> group bluetooth net_bt_admin >> disabled >> oneshot >> >> service hsag /system/bin/sdptool add --channel=11 HSAG >> user bluetooth >> group bluetooth net_bt_admin >> disabled >> oneshot >> ############################################################### >> >> Android now uses the rfkill interface to turn on/off bluetooth. It looks >> for a type of "bluetooth" in each of the rfkill interfaces >> (/sys/class/rfkill/rfkill*/type). We need to have kernel support for this >> to work as devices should be powering on/off with it. >> >> I would like to know how does the /sys/class/rfkill/* entry present. >> >> I'm already apply below configuration in zoom1 kernel >> >> CONFIG_RFKILL=y >> CONFIG_RFKILL_PM=y >> CONFIG_RFKILL_INPUT=y >> CONFIG_ANDROID_PARANOID_NETWORK is not set >> >> After booting the zoom1 kernel nothing present in /sys/class/rfkill/ >> directory. >> bttest also looking for /sys/class/rfkill/* entry. If nothing present its >> give -1. >> >> Please help me if I need to do something else enable or disable in kernel >> (patch). >> >> *Any other way to enable* / disable *bluetooth* device? >> >> >> Thanks in advance, >> Deepak >> >> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
