Hi Pavan, As per the ldp1 docs the inbuilt Bluetooth chip is connected on UART only and
that is ttyS1, console is on ttyS2. "what is the chip enable from omap," I didn't understand this what exactly info u r looking for. Regards Nimit On Thu, Apr 23, 2009 at 8:07 PM, pavan savoy <[email protected]> wrote: > yes, it does, which is strange, very strange. > certainly any support on open-source ti, is not certainly meant to have it > for built-in bluetooth chip, which I am kind of still not convinced. > when I did have bluetooth on ldp1, it was on an expansion connector, which > sent out the uart-2 to the chip. > > may be it does have an older BT 6350 or previous kind of bluetooth chip. > not sure, on what interface it is ? > hopefully UART, but which UART ? > and also, what is the chip enable from omap, is the 2nd question which > needs to be answered. > > regards, > Pavan > > > On Wed, Apr 22, 2009 at 11:39 PM, Nimit Manglick > <[email protected]>wrote: > >> Hi Pavan, >> >> Ya its an ldp1 (as shown in first image attached ) , its bought from >> logicpd only. >> >> But can you please have a look on the following link :- >> >> >> http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-mdk >> >> From this link download the product brief document attached and let me >> know. >> >> It clearly says that it has an inbuilt BT module. >> >> I also have one ldp1. >> >> Can you please verify the same. >> >> Thanks & Regards >> Nimit >> >> >> >> On Wed, Apr 22, 2009 at 8:30 PM, pavan savoy <[email protected]>wrote: >> >>> If it's an ldp1 which is bought from logicPD and looks something like, >>> the attached image which says ldp1 then no, it doesn;t have built in bt. >>> >>> however zoom2 has one. >>> see attached image. >>> >>> regards, >>> Pavan >>> >>> >>> On Wed, Apr 22, 2009 at 1:49 AM, Nimit Manglick >>> <[email protected]>wrote: >>> >>>> 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 -~----------~----~----~----~------~----~------~--~---
