Received: by 10.205.130.14 with SMTP id hk14mr1488472bkc.5.1344881513829;
Mon, 13 Aug 2012 11:11:53 -0700 (PDT)
X-BeenThere: pandaboard@googlegroups.com
Received: by 10.204.13.17 with SMTP id z17ls4771986bkz.5.gmail; Mon, 13 Aug
2012 11:11:50 -0700 (PDT)
Received: by 10.204.130.7 with SMTP id q7mr1489218bks.2.1344881510692;
Mon, 13 Aug 2012 11:11:50 -0700 (PDT)
Received: by 10.204.130.7 with SMTP id q7mr1489217bks.2.1344881510662;
Mon, 13 Aug 2012 11:11:50 -0700 (PDT)
Return-Path: <pavan.sa...@gmail.com>
Received: from mail-lpp01m010-f49.google.com (mail-lpp01m010-f49.google.com [209.85.215.49])
by gmr-mx.google.com with ESMTPS id k7si40239bks.2.2012.08.13.11.11.50
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 13 Aug 2012 11:11:50 -0700 (PDT)
Received-SPF: pass (google.com: domain of pavan.sa...@gmail.com designates 209.85.215.49 as permitted sender) client-ip=209.85.215.49;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of pavan.sa...@gmail.com designates 209.85.215.49 as permitted sender) smtp.mail=pavan.sa...@gmail.com; dkim=pass header...@gmail.com
Received: by lagu2 with SMTP id u2so2024697lag.36
for <pandaboard@googlegroups.com>; Mon, 13 Aug 2012 11:11:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=NsYfjZlIiGo836IaFAaPT3KIErCSgeuKXsPL9iEJHQg=;
b=RMD8Mbotm8F/uUxgolHwUTa/mAy3Co0No8gtYKCQrb3EgeQ+eOxDx37t1otUMd8rFk
Yufq2niiUfnPL5+E8YOahEDN1TQ7V6b9iUQiH+gbA5+mBgu8sl4OomN4Ye6rotqjmE4C
95x/DPg/E6PCgPPbei+nB/mfLRUK5wcJWSfxXl2zxTwXfbypSR5FUID76spza4rLoaRE
KmHDdxRjmLB2HdOA67zbA884imXZ2uktSLiWHIMkAk5vPWgJCsiSmQN/AFxEfUw1vGmW
x0y8xV/rU/W1QNzbGJdm+F8ax7tx6HtxwP0gMsugwEW8qqolnu8CY8TISWGcOKivJBZj
T3Rw==
MIME-Version: 1.0
Received: by 10.112.26.197 with SMTP id n5mr6918516lbg.18.1344881510115; Mon,
13 Aug 2012 11:11:50 -0700 (PDT)
Received: by 10.112.37.196 with HTTP; Mon, 13 Aug 2012 11:11:49 -0700 (PDT)
In-Reply-To: <CACUGKYPKxsUYC1Q47hV609Gyy6DTDwxTS+5goFpopsRNyYV...@mail.gmail.com>
References: <1711495f-6164-445a-ad17-8bdcd622868f@googlegroups.com>
<CAHd==doPmF9Vw-QWOZ48=XtAB7MpY9AunJSBL7_j9sManZq...@mail.gmail.com>
<CACUGKYOyvqryqtWNem0yWo6V9n6OcLD1M-c8RWdA4gKbSOW...@mail.gmail.com>
<CAHd==dqEFnhHoMaSKfh-M-ZE=vFq770deJLG5N4jsF05i85...@mail.gmail.com>
<CACUGKYOFCYu=3=S+imH3A1FwehQhGUsYO81V=PorcP8ik9u...@mail.gmail.com>
<CAHd==dp6NwfX7OpTe_A-mRAo_Shk+8DOTjV0heSLP-_LNE3...@mail.gmail.com>
<CACUGKYPrdcSRJoWswWZ4j0sNxAxRYBvK4tsQOv70zjZZzvR...@mail.gmail.com>
<CAHd==drGHrZQVFKTwdffYSPTB9Hk5oHiESmCNkMPJbU9jqh...@mail.gmail.com>
<CACUGKYNF7HPHOqmhm9rvor2KyKRVmmrALJdpiAEEGjwfDCb...@mail.gmail.com>
<892F50EE441C4C33A04A6B7A9F9112F4@quad>
<CAHd==drmwZpx2Z8otBWgLkxVaf8+bxJMmR_Vg_T5ae_B7YA...@mail.gmail.com>
<CACUGKYNmZp_Q+ib7xVnQ9bZPu2LHztgLT6d8ZjRB+aOP4S8...@mail.gmail.com>
<CAHd==dra19KDrt_0VPaCeJLP9q8McvZxFWN9cC06HbN=m2X...@mail.gmail.com>
<CACUGKYME9zKM80iY2vHiJPRA5p61t+F+1Ldnxi=ubx9k9yC...@mail.gmail.com>
<CAHd==dpNreNG28x=izo0jcRQGqNTSi+Hk2a4Qs5q=tK1-XB...@mail.gmail.com>
<CACUGKYMPicOzZDyf1fnFEsk=rtjmpC58pWpqhENBOAoGwNL...@mail.gmail.com>
<CACUGKYPv6MvibNu00+QHMz7uwdUga8P3S+rjxQz090KhT03...@mail.gmail.com>
<CAHd==dqG5sy9bOHLDA87iMNrejQRRtcac=PZVzjD5Mpm1Na...@mail.gmail.com>
<CACUGKYPKxsUYC1Q47hV609Gyy6DTDwxTS+5goFpopsRNyYV...@mail.gmail.com>
Date: Mon, 13 Aug 2012 13:11:49 -0500
Message-ID: <CAHd==dpYdg=6zAO9HFs8-yTN-f7+9cWaHfyzu2KgjpAwdGP...@mail.gmail.com>
Subject: Re: [pandaboard] Enabling Bluetooth LE
From: Pavan Savoy <pavan.sa...@gmail.com>
To: pandaboard@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Aug 13, 2012 at 12:56 PM, John Tobias <john.tobias...@gmail.com> wrote:
> Hi Pavan,
>
> I executed the 'hciconfig hci0 leadv' and the hcidump was running in the
> background. Then, found out the "Error: Command Disallowed".
> Any idea how to fix it?.
Did you make sure you ran the VS commands that I sent out earlier ?
You'd want to run it everytime hci0 is reset.
i.e make sure hciconfig hci0 lestates - says few states to be TRUE
before running any of these LE commands.
>
> < HCI Command: LE Set Advertise Enable (0x08|0x000a) plen 1
> 0000: 01 .
> LE set advertise enable on hci0 returned status 12
>> HCI Event: Command Complete (0x0e) plen 4
> LE Set Advertise Enable (0x08|0x000a) ncmd 1
> status 0x0c
> Error: Command Disallowed
>
> Regards,
>
> John
>
>
> On Sun, Aug 12, 2012 at 10:44 AM, Pavan Savoy <pavan.sa...@gmail.com> wrote:
>>
>> On Sun, Aug 12, 2012 at 12:27 PM, John Tobias <john.tobias...@gmail.com>
>> wrote:
>> > Hi,
>> >
>> > I got a working kernel where the Bluetooth is detected correctly. I have
>> > a
>> > bluegia BLDE112, where it broadcast an advertisement (I was able to scan
>> > it
>> > using my iPhone). I was assuming that I can scan the said service in
>> > linux
>> > after executing the commands you sent to me (below), but I did not get
>> > any
>> > result.
>> >
>> > hcitool cmd 0x3f 0x015B 0x1 0x0
>> > hcitool cmd 0x3f 0x01DD 0x1
>> > hciconfig hci0 lestates
>> > hcitool cmd 0x3f 0x015B 0x1 0x0
>> > hciconfig hci0 lestates
>> >
>> > The follow questions after executing the said commands above:
>>
>> hciconfig hci0 lestates -> returning a few states as TRUE suggests LE
>> can be enabled on the device.
>>
>> > 1. What command should I use to scan the le devices?
>> hcitool lescan - scans for devices that are advertising.
>>
>> > 2. What command should I use to advertise, create connection to le
>> > device?.
>> hciconfig hci0 leadv -> Is to enable advertisement, that can be
>> scanned by other devices.
>>
>> hcidump -X in both the above cases will show you what is being
>> advertised by remote device and what you would advertise too.
>>
>> >
>> > Regards,
>> >
>> > John
>> >
>> >
>> >
>> >
>> >
>> > On Fri, Aug 10, 2012 at 9:16 PM, John Tobias <john.tobias...@gmail.com>
>> > wrote:
>> >>
>> >> Still no success.
>> >> hciconfig hci0 up
>> >> Can't get device info: No such device
>> >>
>> >> I compared my kernel messages against to the working version and I've
>> >> noticed that on the working version has the following:
>> >>
>> >> [ 10.850372] hdev ef09c000
>> >> [ 10.854919] HCI device registered (hdev ef09c000)
>> >> [ 10.857116] hci0 ef09c000
>> >> [ 10.857116] (stc): st_register(4)
>> >> [ 10.857116] (stc): chnl_id list empty :4
>> >> [ 10.857147] (stk) : st_kim_start
>> >> [ 10.959899] (stk) :ldisc_install = 1
>> >> [ 11.012634] (stc): st_tty_open
>> >> [ 11.012664] (stk) : line discipline installed
>> >> [ 11.013183] (stk) :ti-connectivity/TIInit_7.6.15.bts
>> >>
>> >> Any idea?.
>> >> Also, can you tell me what version of the kernel are you using and can
>> >> you
>> >> share to me the .config file?.
>> >>
>> >> Thanks,
>> >>
>> >> john
>> >>
>> >> On Fri, Aug 10, 2012 at 8:13 PM, Pavan Savoy <pavan.sa...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Well then you should now be able to see the hciX interface atleast.
>> >>> As in hciconfig -a should throw up hci0 DOWN.
>> >>>
>> >>> Try and do a hciconfig hci0 up. You might need this binary running
>> >>> too.
>> >>> Run it in back-ground (uim-sysfs) & then try hciconfig hci0 up.
>> >>>
>> >>> On Fri, Aug 10, 2012 at 9:46 PM, John Tobias
>> >>> <john.tobias...@gmail.com>
>> >>> wrote:
>> >>> > I searched the sys directory and I got the following:
>> >>> > (But now /sys/devices/platform/btwilink exist on sys directory)
>> >>> >
>> >>> > ./bus/platform/drivers/btwilink
>> >>> > ./module/st_drv/holders/btwilink
>> >>> > ./module/btwilink
>> >>> >
>> >>> > ./devices/platform/kim
>> >>> > ./bus/platform/devices/kim
>> >>> > ./bus/platform/drivers/kim
>> >>> > ./bus/platform/drivers/kim/kim
>> >>> >
>> >>> > Also, I posted my kernel messages;
>> >>> >
>> >>> > [ 0.877746] driver: 'omap_timer.6': driver_bound: bound to device
>> >>> > 'omap_timer'
>> >>> > [ 0.877746] bus: 'platform': really_probe: bound device
>> >>> > omap_timer.6
>> >>> > to
>> >>> > driver omap_timer
>> >>> > [ 0.877807] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_timer.7 with driver omap_timer
>> >>> > [ 0.877838] bus: 'platform': really_probe: probing driver
>> >>> > omap_timer
>> >>> > with
>> >>> > device omap_timer.7
>> >>> > [ 0.877929] driver: 'omap_timer.7': driver_bound: bound to device
>> >>> > 'omap_timer'
>> >>> > [ 0.877929] bus: 'platform': really_probe: bound device
>> >>> > omap_timer.7
>> >>> > to
>> >>> > driver omap_timer
>> >>> > [ 0.877990] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_timer.8 with driver omap_timer
>> >>> > [ 0.877990] bus: 'platform': really_probe: probing driver
>> >>> > omap_timer
>> >>> > with
>> >>> > device omap_timer.8
>> >>> > [ 0.878082] driver: 'omap_timer.8': driver_bound: bound to device
>> >>> > 'omap_timer'
>> >>> > [ 0.878112] bus: 'platform': really_probe: bound device
>> >>> > omap_timer.8
>> >>> > to
>> >>> > driver omap_timer
>> >>> > [ 0.878143] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_timer.9 with driver omap_timer
>> >>> > [ 0.878173] bus: 'platform': really_probe: probing driver
>> >>> > omap_timer
>> >>> > with
>> >>> > device omap_timer.9
>> >>> > [ 0.878265] driver: 'omap_timer.9': driver_bound: bound to device
>> >>> > 'omap_timer'
>> >>> > [ 0.878265] bus: 'platform': really_probe: bound device
>> >>> > omap_timer.9
>> >>> > to
>> >>> > driver omap_timer
>> >>> > [ 0.878326] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_timer.10 with driver omap_timer
>> >>> > [ 0.878326] bus: 'platform': really_probe: probing driver
>> >>> > omap_timer
>> >>> > with
>> >>> > device omap_timer.10
>> >>> > [ 0.878417] driver: 'omap_timer.10': driver_bound: bound to
>> >>> > device
>> >>> > 'omap_timer'
>> >>> > [ 0.878417] bus: 'platform': really_probe: bound device
>> >>> > omap_timer.10 to
>> >>> > driver omap_timer
>> >>> > [ 0.878479] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_timer.11 with driver omap_timer
>> >>> > [ 0.878479] bus: 'platform': really_probe: probing driver
>> >>> > omap_timer
>> >>> > with
>> >>> > device omap_timer.11
>> >>> > [ 0.878570] driver: 'omap_timer.11': driver_bound: bound to
>> >>> > device
>> >>> > 'omap_timer'
>> >>> > [ 0.878601] bus: 'platform': really_probe: bound device
>> >>> > omap_timer.11 to
>> >>> > driver omap_timer
>> >>> > [ 0.879180] Registering sysdev class 'clocksource'
>> >>> > [ 0.879455] Registering sys device of class 'clocksource'
>> >>> > [ 0.879486] Registering sys device 'clocksource0'
>> >>> > [ 0.879852] bus: 'platform': add driver alarmtimer
>> >>> > [ 0.880279] Registering platform device 'alarmtimer'. Parent at
>> >>> > platform
>> >>> > [ 0.880279] device: 'alarmtimer': device_add
>> >>> > [ 0.880310] bus: 'platform': add device alarmtimer
>> >>> > [ 0.880401] PM: Adding info for platform:alarmtimer
>> >>> > [ 0.880706] bus: 'platform': driver_probe_device: matched device
>> >>> > alarmtimer with driver alarmtimer
>> >>> > [ 0.880737] bus: 'platform': really_probe: probing driver
>> >>> > alarmtimer
>> >>> > with
>> >>> > device alarmtimer
>> >>> > [ 0.880798] driver: 'alarmtimer': driver_bound: bound to device
>> >>> > 'alarmtimer'
>> >>> > [ 0.880798] bus: 'platform': really_probe: bound device
>> >>> > alarmtimer
>> >>> > to
>> >>> > driver alarmtimer
>> >>> > [ 1.016540] bus: 'event_source': registered
>> >>> > [ 1.016601] device: 'breakpoint': device_add
>> >>> > [ 1.016632] bus: 'event_source': add device breakpoint
>> >>> > [ 1.016754] PM: Adding info for event_source:breakpoint
>> >>> > [ 1.017089] device: 'tracepoint': device_add
>> >>> > [ 1.017181] bus: 'event_source': add device tracepoint
>> >>> > [ 1.017272] PM: Adding info for event_source:tracepoint
>> >>> > [ 1.017547] device: 'software': device_add
>> >>> > [ 1.017608] bus: 'event_source': add device software
>> >>> > [ 1.017791] PM: Adding info for event_source:software
>> >>> > [ 1.029754] VFS: Disk quotas dquot_6.5.2
>> >>> > [ 1.029998] Dquot-cache hash table entries: 1024 (order 0, 4096
>> >>> > bytes)
>> >>> > [ 1.032592] JFFS2 version 2.2. (NAND) (SUMMARY)
>> >>> > \xffffffc2\xffffffa9\xffffffa9 2001-2006 Red Hat, Inc.
>> >>> > [ 1.033447] msgmni has been set to 1463
>> >>> > [ 1.035949] io scheduler noop registered
>> >>> > [ 1.035980] io scheduler deadline registered
>> >>> > [ 1.036163] io scheduler cfq registered (default)
>> >>> > [ 1.036224] device: 'fbcon': device_add
>> >>> > [ 1.036346] PM: Adding info for No Bus:fbcon
>> >>> > [ 1.036773] bus: 'platform': add driver platform-lcd
>> >>> > [ 1.037200] bus: 'platform': add driver generic-bl
>> >>> > [ 1.037567] device class 'display': registering
>> >>> > [ 1.037902] device: 'ptmx': device_add
>> >>> > [ 1.038024] PM: Adding info for No Bus:ptmx
>> >>> > [ 1.038299] Serial: 8250/16550 driver, 4 ports, IRQ sharing
>> >>> > enabled
>> >>> > [ 1.038482] Registering platform device 'serial8250'. Parent at
>> >>> > platform
>> >>> > [ 1.038513] device: 'serial8250': device_add
>> >>> > [ 1.038543] bus: 'platform': add device serial8250
>> >>> > [ 1.038635] PM: Adding info for platform:serial8250
>> >>> > [ 1.039123] device: 'ttyS0': device_add
>> >>> > [ 1.039398] PM: Adding info for No Bus:ttyS0
>> >>> > [ 1.056365] device: 'ttyS1': device_add
>> >>> > [ 1.056549] PM: Adding info for No Bus:ttyS1
>> >>> > [ 1.087493] device: 'ttyS2': device_add
>> >>> > [ 1.087677] PM: Adding info for No Bus:ttyS2
>> >>> > [ 1.110961] device: 'ttyS3': device_add
>> >>> > [ 1.111114] PM: Adding info for No Bus:ttyS3
>> >>> > [ 1.142181] bus: 'platform': add driver serial8250
>> >>> > [ 1.142303] bus: 'platform': driver_probe_device: matched device
>> >>> > serial8250 with driver serial8250
>> >>> > [ 1.142333] bus: 'platform': really_probe: probing driver
>> >>> > serial8250
>> >>> > with
>> >>> > device serial8250
>> >>> > [ 1.142364] driver: 'serial8250': driver_bound: bound to device
>> >>> > 'serial8250'
>> >>> > [ 1.142395] bus: 'platform': really_probe: bound device
>> >>> > serial8250
>> >>> > to
>> >>> > driver serial8250
>> >>> > [ 1.142730] bus: 'platform': add driver omap_uart
>> >>> > [ 1.142791] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_uart.0 with driver omap_uart
>> >>> > [ 1.142822] bus: 'platform': really_probe: probing driver
>> >>> > omap_uart
>> >>> > with
>> >>> > device omap_uart.0
>> >>> > [ 1.142944] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is
>> >>> > a
>> >>> > OMAP
>> >>> > UART0
>> >>> > [ 1.143127] device: 'ttyO0': device_add
>> >>> > [ 1.143371] PM: Adding info for No Bus:ttyO0
>> >>> > [ 1.157806] driver: 'omap_uart.0': driver_bound: bound to device
>> >>> > 'omap_uart'
>> >>> > [ 1.157836] bus: 'platform': really_probe: bound device
>> >>> > omap_uart.0
>> >>> > to
>> >>> > driver omap_uart
>> >>> > [ 1.157867] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_uart.1 with driver omap_uart
>> >>> > [ 1.157867] bus: 'platform': really_probe: probing driver
>> >>> > omap_uart
>> >>> > with
>> >>> > device omap_uart.1
>> >>> > [ 1.157928] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is
>> >>> > a
>> >>> > OMAP
>> >>> > UART1
>> >>> > [ 1.158020] device: 'ttyO1': device_add
>> >>> > [ 1.158203] PM: Adding info for No Bus:ttyO1
>> >>> > [ 1.189056] driver: 'omap_uart.1': driver_bound: bound to device
>> >>> > 'omap_uart'
>> >>> > [ 1.189056] bus: 'platform': really_probe: bound device
>> >>> > omap_uart.1
>> >>> > to
>> >>> > driver omap_uart
>> >>> > [ 1.189086] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_uart.2 with driver omap_uart
>> >>> > [ 1.189117] bus: 'platform': really_probe: probing driver
>> >>> > omap_uart
>> >>> > with
>> >>> > device omap_uart.2
>> >>> > [ 1.189178] omap_uart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is
>> >>> > a
>> >>> > OMAP
>> >>> > UART2
>> >>> > [ 2.058685] console [ttyO2] enabled
>> >>> > [ 2.062408] device: 'ttyO2': device_add
>> >>> > [ 2.062622] PM: Adding info for No Bus:ttyO2
>> >>> > [ 2.071868] driver: 'omap_uart.2': driver_bound: bound to device
>> >>> > 'omap_uart'
>> >>> > [ 2.071868] bus: 'platform': really_probe: bound device
>> >>> > omap_uart.2
>> >>> > to
>> >>> > driver omap_uart
>> >>> > [ 2.071899] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_uart.3 with driver omap_uart
>> >>> > [ 2.071929] bus: 'platform': really_probe: probing driver
>> >>> > omap_uart
>> >>> > with
>> >>> > device omap_uart.3
>> >>> > [ 2.071990] omap_uart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is
>> >>> > a
>> >>> > OMAP
>> >>> > UART3
>> >>> > [ 2.079620] device: 'ttyO3': device_add
>> >>> > [ 2.079803] PM: Adding info for No Bus:ttyO3
>> >>> > [ 2.126556] driver: 'omap_uart.3': driver_bound: bound to device
>> >>> > 'omap_uart'
>> >>> > [ 2.126556] bus: 'platform': really_probe: bound device
>> >>> > omap_uart.3
>> >>> > to
>> >>> > driver omap_uart
>> >>> > [ 2.129302] device: '1:0': device_add
>> >>> > [ 2.129425] PM: Adding info for No Bus:1:0
>> >>> > [ 2.129760] device: 'ram0': device_add
>> >>> > [ 2.129974] PM: Adding info for No Bus:ram0
>> >>> > [ 2.130554] device: '1:1': device_add
>> >>> > [ 2.130676] PM: Adding info for No Bus:1:1
>> >>> > [ 2.131011] device: 'ram1': device_add
>> >>> > [ 2.131195] PM: Adding info for No Bus:ram1
>> >>> > [ 2.131683] device: '1:2': device_add
>> >>> > [ 2.131774] PM: Adding info for No Bus:1:2
>> >>> > [ 2.132110] device: 'ram2': device_add
>> >>> > [ 2.132293] PM: Adding info for No Bus:ram2
>> >>> > [ 2.132781] device: '1:3': device_add
>> >>> > [ 2.132904] PM: Adding info for No Bus:1:3
>> >>> > [ 2.133239] device: 'ram3': device_add
>> >>> > [ 2.133422] PM: Adding info for No Bus:ram3
>> >>> > [ 2.133911] device: '1:4': device_add
>> >>> > [ 2.134002] PM: Adding info for No Bus:1:4
>> >>> > [ 2.134399] device: 'ram4': device_add
>> >>> > [ 2.134582] PM: Adding info for No Bus:ram4
>> >>> > [ 2.135070] device: '1:5': device_add
>> >>> > [ 2.135192] PM: Adding info for No Bus:1:5
>> >>> > [ 2.135498] device: 'ram5': device_add
>> >>> > [ 2.135681] PM: Adding info for No Bus:ram5
>> >>> > [ 2.136169] device: '1:6': device_add
>> >>> > [ 2.136291] PM: Adding info for No Bus:1:6
>> >>> > [ 2.136627] device: 'ram6': device_add
>> >>> > [ 2.136810] PM: Adding info for No Bus:ram6
>> >>> > [ 2.137298] device: '1:7': device_add
>> >>> > [ 2.137420] PM: Adding info for No Bus:1:7
>> >>> > [ 2.137725] device: 'ram7': device_add
>> >>> > [ 2.137908] PM: Adding info for No Bus:ram7
>> >>> > [ 2.138397] device: '1:8': device_add
>> >>> > [ 2.138519] PM: Adding info for No Bus:1:8
>> >>> > [ 2.138854] device: 'ram8': device_add
>> >>> > [ 2.139068] PM: Adding info for No Bus:ram8
>> >>> > [ 2.139556] device: '1:9': device_add
>> >>> > [ 2.139678] PM: Adding info for No Bus:1:9
>> >>> > [ 2.139984] device: 'ram9': device_add
>> >>> > [ 2.140197] PM: Adding info for No Bus:ram9
>> >>> > [ 2.140686] device: '1:10': device_add
>> >>> > [ 2.140777] PM: Adding info for No Bus:1:10
>> >>> > [ 2.141113] device: 'ram10': device_add
>> >>> > [ 2.141296] PM: Adding info for No Bus:ram10
>> >>> > [ 2.141815] device: '1:11': device_add
>> >>> > [ 2.141937] PM: Adding info for No Bus:1:11
>> >>> > [ 2.142333] device: 'ram11': device_add
>> >>> > [ 2.142517] PM: Adding info for No Bus:ram11
>> >>> > [ 2.143066] device: '1:12': device_add
>> >>> > [ 2.143188] PM: Adding info for No Bus:1:12
>> >>> > [ 2.143524] device: 'ram12': device_add
>> >>> > [ 2.143707] PM: Adding info for No Bus:ram12
>> >>> > [ 2.144165] device: '1:13': device_add
>> >>> > [ 2.144287] PM: Adding info for No Bus:1:13
>> >>> > [ 2.144592] device: 'ram13': device_add
>> >>> > [ 2.144775] PM: Adding info for No Bus:ram13
>> >>> > [ 2.145263] device: '1:14': device_add
>> >>> > [ 2.145385] PM: Adding info for No Bus:1:14
>> >>> > [ 2.145690] device: 'ram14': device_add
>> >>> > [ 2.145874] PM: Adding info for No Bus:ram14
>> >>> > [ 2.146362] device: '1:15': device_add
>> >>> > [ 2.146484] PM: Adding info for No Bus:1:15
>> >>> > [ 2.146850] device: 'ram15': device_add
>> >>> > [ 2.147033] PM: Adding info for No Bus:ram15
>> >>> > [ 2.147491] brd: module loaded
>> >>> > [ 2.150878] device: 'loop-control': device_add
>> >>> > [ 2.151153] PM: Adding info for No Bus:loop-control
>> >>> > [ 2.152099] device: '7:0': device_add
>> >>> > [ 2.152313] PM: Adding info for No Bus:7:0
>> >>> > [ 2.152984] device: 'loop0': device_add
>> >>> > [ 2.153167] PM: Adding info for No Bus:loop0
>> >>> > [ 2.153961] device: '7:1': device_add
>> >>> > [ 2.154083] PM: Adding info for No Bus:7:1
>> >>> > [ 2.154449] device: 'loop1': device_add
>> >>> > [ 2.154632] PM: Adding info for No Bus:loop1
>> >>> > [ 2.155334] device: '7:2': device_add
>> >>> > [ 2.155456] PM: Adding info for No Bus:7:2
>> >>> > [ 2.155822] device: 'loop2': device_add
>> >>> > [ 2.156036] PM: Adding info for No Bus:loop2
>> >>> > [ 2.156707] device: '7:3': device_add
>> >>> > [ 2.156860] PM: Adding info for No Bus:7:3
>> >>> > [ 2.157196] device: 'loop3': device_add
>> >>> > [ 2.157409] PM: Adding info for No Bus:loop3
>> >>> > [ 2.158142] device: '7:4': device_add
>> >>> > [ 2.158264] PM: Adding info for No Bus:7:4
>> >>> > [ 2.158630] device: 'loop4': device_add
>> >>> > [ 2.158843] PM: Adding info for No Bus:loop4
>> >>> > [ 2.159515] device: '7:5': device_add
>> >>> > [ 2.159667] PM: Adding info for No Bus:7:5
>> >>> > [ 2.160003] device: 'loop5': device_add
>> >>> > [ 2.160186] PM: Adding info for No Bus:loop5
>> >>> > [ 2.160888] device: '7:6': device_add
>> >>> > [ 2.161010] PM: Adding info for No Bus:7:6
>> >>> > [ 2.161376] device: 'loop6': device_add
>> >>> > [ 2.161590] PM: Adding info for No Bus:loop6
>> >>> > [ 2.162292] device: '7:7': device_add
>> >>> > [ 2.162414] PM: Adding info for No Bus:7:7
>> >>> > [ 2.162780] device: 'loop7': device_add
>> >>> > [ 2.162963] PM: Adding info for No Bus:loop7
>> >>> > [ 2.163482] loop: module loaded
>> >>> > [ 2.166839] bus: 'i2c': add driver menelaus
>> >>> > [ 2.167205] bus: 'platform': add driver twl4030-audio
>> >>> > [ 2.167694] device class 'scsi_disk': registering
>> >>> > [ 2.167968] bus: 'scsi': add driver sd
>> >>> > [ 2.168365] device class 'mtd': registering
>> >>> > [ 2.168762] device: 'mtd-unmap': device_add
>> >>> > [ 2.168884] PM: Adding info for No Bus:mtd-unmap
>> >>> > [ 2.169342] device: 'mtd-romap': device_add
>> >>> > [ 2.169464] PM: Adding info for No Bus:mtd-romap
>> >>> > [ 2.169952] device: 'mtd-rwmap': device_add
>> >>> > [ 2.170043] PM: Adding info for No Bus:mtd-rwmap
>> >>> > [ 2.170989] mtdoops: mtd device (mtddev=name/number) must be
>> >>> > supplied
>> >>> > [ 2.177886] omap2-nand driver initializing
>> >>> > [ 2.182250] bus: 'platform': add driver omap2-nand
>> >>> > [ 2.182678] OneNAND driver initializing
>> >>> > [ 2.186737] bus: 'platform': add driver omap2-onenand
>> >>> > [ 2.187133] device class 'ubi': registering
>> >>> > [ 2.187438] device: 'ubi_ctrl': device_add
>> >>> > [ 2.187591] PM: Adding info for No Bus:ubi_ctrl
>> >>> > [ 2.187957] bus: 'mdio_bus': add driver SMSC LAN83C185
>> >>> > [ 2.188262] bus: 'mdio_bus': add driver SMSC LAN8187
>> >>> > [ 2.188537] bus: 'mdio_bus': add driver SMSC LAN8700
>> >>> > [ 2.188842] bus: 'mdio_bus': add driver SMSC LAN911x Internal PHY
>> >>> > [ 2.189178] bus: 'mdio_bus': add driver SMSC LAN8710/LAN8720
>> >>> > [ 2.189453] bus: 'spi': add driver ks8851
>> >>> > [ 2.189758] bus: 'platform': add driver ks8851_mll
>> >>> > [ 2.190155] bus: 'platform': add driver smc91x
>> >>> > [ 2.190551] bus: 'platform': add driver smsc911x
>> >>> > [ 2.190948] bus: 'usb': add driver asix
>> >>> > [ 2.191314] usbcore: registered new interface driver asix
>> >>> > [ 2.197052] bus: 'usb': add driver cdc_ether
>> >>> > [ 2.197387] usbcore: registered new interface driver cdc_ether
>> >>> > [ 2.203552] bus: 'usb': add driver smsc95xx
>> >>> > [ 2.203887] usbcore: registered new interface driver smsc95xx
>> >>> > [ 2.209991] bus: 'usb': add driver net1080
>> >>> > [ 2.210327] usbcore: registered new interface driver net1080
>> >>> > [ 2.216339] bus: 'usb': add driver cdc_subset
>> >>> > [ 2.216644] usbcore: registered new interface driver cdc_subset
>> >>> > [ 2.222930] bus: 'usb': add driver zaurus
>> >>> > [ 2.223266] usbcore: registered new interface driver zaurus
>> >>> > [ 2.229217] cdc_ncm: 04-Aug-2011
>> >>> > [ 2.232635] bus: 'usb': add driver cdc_ncm
>> >>> > [ 2.232940] usbcore: registered new interface driver cdc_ncm
>> >>> > [ 2.238983] device class 'usbmon': registering
>> >>> > [ 2.239349] device: 'usbmon0': device_add
>> >>> > [ 2.239471] PM: Adding info for No Bus:usbmon0
>> >>> > [ 2.239898] bus: 'usb': add driver cdc_wdm
>> >>> > [ 2.240234] usbcore: registered new interface driver cdc_wdm
>> >>> > [ 2.246246] Initializing USB Mass Storage driver...
>> >>> > [ 2.251403] bus: 'usb': add driver usb-storage
>> >>> > [ 2.251770] usbcore: registered new interface driver usb-storage
>> >>> > [ 2.258148] USB Mass Storage support registered.
>> >>> > [ 2.263153] bus: 'usb': add driver libusual
>> >>> > [ 2.263854] usbcore: registered new interface driver libusual
>> >>> > [ 2.269958] bus: 'usb': add driver usbtest
>> >>> > [ 2.270324] usbcore: registered new interface driver usbtest
>> >>> > [ 2.276397] device: 'mice': device_add
>> >>> > [ 2.276519] PM: Adding info for No Bus:mice
>> >>> > [ 2.276916] device: 'psaux': device_add
>> >>> > [ 2.277038] PM: Adding info for No Bus:psaux
>> >>> > [ 2.277313] mousedev: PS/2 mouse device common for all mice
>> >>> > [ 2.283264] bus: 'serio': add driver atkbd
>> >>> > [ 2.283721] bus: 'platform': add driver twl4030_keypad
>> >>> > [ 2.284454] bus: 'serio': add driver psmouse
>> >>> > [ 2.284881] bus: 'spi': add driver ads7846
>> >>> > [ 2.285217] bus: 'platform': add driver twl4030_pwrbutton
>> >>> > [ 2.285614] bus: 'platform': remove driver twl4030_pwrbutton
>> >>> > [ 2.285888] driver: 'twl4030_pwrbutton': driver_release
>> >>> > [ 2.285919] bus: 'platform': add driver twl_rtc
>> >>> > [ 2.286010] bus: 'platform': driver_probe_device: matched device
>> >>> > twl_rtc
>> >>> > with driver twl_rtc
>> >>> > [ 2.286041] bus: 'platform': really_probe: probing driver twl_rtc
>> >>> > with
>> >>> > device twl_rtc
>> >>> > [ 2.286529] twl_rtc twl_rtc: Power up reset detected.
>> >>> > [ 2.292938] twl_rtc twl_rtc: Enabling TWL-RTC.
>> >>> > [ 2.299530] device: 'rtc0': device_add
>> >>> > [ 2.299743] PM: Adding info for No Bus:rtc0
>> >>> > [ 2.300201] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
>> >>> > [ 2.307006] driver: 'twl_rtc': driver_bound: bound to device
>> >>> > 'twl_rtc'
>> >>> > [ 2.307006] bus: 'platform': really_probe: bound device twl_rtc
>> >>> > to
>> >>> > driver
>> >>> > twl_rtc
>> >>> > [ 2.307342] i2c /dev entries driver
>> >>> > [ 2.311035] device class 'i2c-dev': registering
>> >>> > [ 2.311462] device: 'i2c-1': device_add
>> >>> > [ 2.311737] PM: Adding info for No Bus:i2c-1
>> >>> > [ 2.312408] device: 'i2c-2': device_add
>> >>> > [ 2.312561] PM: Adding info for No Bus:i2c-2
>> >>> > [ 2.312896] device: 'i2c-3': device_add
>> >>> > [ 2.313049] PM: Adding info for No Bus:i2c-3
>> >>> > [ 2.313354] device: 'i2c-4': device_add
>> >>> > [ 2.313476] PM: Adding info for No Bus:i2c-4
>> >>> > [ 2.313781] Driver for 1-wire Dallas network protocol.
>> >>> > [ 2.319549] bus: 'w1': registered
>> >>> > [ 2.319580] bus: 'w1': add driver w1_master_driver
>> >>> > [ 2.319885] bus: 'w1': add driver w1_slave_driver
>> >>> > [ 2.320190] bus: 'platform': add driver omap_wdt
>> >>> > [ 2.320312] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_wdt
>> >>> > with driver omap_wdt
>> >>> > [ 2.320343] bus: 'platform': really_probe: probing driver
>> >>> > omap_wdt
>> >>> > with
>> >>> > device omap_wdt
>> >>> > [ 2.320922] device: 'watchdog': device_add
>> >>> > [ 2.321166] PM: Adding info for No Bus:watchdog
>> >>> > [ 2.321655] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
>> >>> > [ 2.328033] driver: 'omap_wdt': driver_bound: bound to device
>> >>> > 'omap_wdt'
>> >>> > [ 2.328063] bus: 'platform': really_probe: bound device omap_wdt
>> >>> > to
>> >>> > driver omap_wdt
>> >>> > [ 2.328399] bus: 'platform': add driver twl4030_wdt
>> >>> > [ 2.328796] Bluetooth: HCI UART driver ver 2.2
>> >>> > [ 2.333526] Bluetooth: HCI H4 protocol initialized
>> >>> > [ 2.338623] Bluetooth: HCI BCSP protocol initialized
>> >>> > [ 2.343841] Bluetooth: HCILL protocol initialized
>> >>> > [ 2.348846] Bluetooth: Broadcom Blutonium firmware driver ver 1.2
>> >>> > [ 2.355316] bus: 'usb': add driver bcm203x
>> >>> > [ 2.355651] usbcore: registered new interface driver bcm203x
>> >>> > [ 2.361663] Bluetooth: Digianswer Bluetooth USB driver ver 0.10
>> >>> > [ 2.367919] bus: 'usb': add driver bpa10x
>> >>> > [ 2.368286] usbcore: registered new interface driver bpa10x
>> >>> > [ 2.374206] Bluetooth: Generic Bluetooth USB driver ver 0.6
>> >>> > [ 2.380096] bus: 'usb': add driver btusb
>> >>> > [ 2.380462] usbcore: registered new interface driver btusb
>> >>> > [ 2.386291] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
>> >>> > [ 2.392272] bus: 'sdio': add driver btsdio
>> >>> > [ 2.392578] bus: 'mmc': add driver mmcblk
>> >>> > [ 2.392913] bus: 'sdio': add driver sdio_uart
>> >>> > [ 2.393218] bus: 'platform': add driver mmci-omap
>> >>> > [ 2.393615] bus: 'platform': remove driver mmci-omap
>> >>> > [ 2.393890] driver: 'mmci-omap': driver_release
>> >>> > [ 2.394134] bus: 'platform': add driver omap_hsmmc
>> >>> > [ 2.394195] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_hsmmc.0 with driver omap_hsmmc
>> >>> > [ 2.394226] bus: 'platform': really_probe: probing driver
>> >>> > omap_hsmmc
>> >>> > with
>> >>> > device omap_hsmmc.0
>> >>> > [ 2.398864] device: 'mmc0': device_add
>> >>> > [ 2.398986] PM: Adding info for No Bus:mmc0
>> >>> > [ 2.400695] driver: 'omap_hsmmc.0': driver_bound: bound to device
>> >>> > 'omap_hsmmc'
>> >>> > [ 2.400726] bus: 'platform': really_probe: bound device
>> >>> > omap_hsmmc.0
>> >>> > to
>> >>> > driver omap_hsmmc
>> >>> > [ 2.400787] bus: 'platform': driver_probe_device: matched device
>> >>> > omap_hsmmc.4 with driver omap_hsmmc
>> >>> > [ 2.400817] bus: 'platform': really_probe: probing driver
>> >>> > omap_hsmmc
>> >>> > with
>> >>> > device omap_hsmmc.4
>> >>> > [ 2.401153] device: 'mmc1': device_add
>> >>> > [ 2.401275] PM: Adding info for No Bus:mmc1
>> >>> > [ 2.403533] driver: 'omap_hsmmc.4': driver_bound: bound to device
>> >>> > 'omap_hsmmc'
>> >>> > [ 2.403564] bus: 'platform': really_probe: bound device
>> >>> > omap_hsmmc.4
>> >>> > to
>> >>> > driver omap_hsmmc
>> >>> > [ 2.404479] bus: 'hid': registered
>> >>> > [ 2.404541] bus: 'hid': add driver generic-usb
>> >>> > [ 2.404937] bus: 'usb': add driver usbhid
>> >>> > [ 2.405273] usbcore: registered new interface driver usbhid
>> >>> > [ 2.411224] usbhid: USB HID core driver
>> >>> > [ 2.415252] oprofile: hardware counters not available
>> >>> > [ 2.420715] oprofile: using timer interrupt.
>> >>> > [ 2.425659] TCP cubic registered
>> >>> > [ 2.429077] Initializing XFRM netlink socket
>> >>> > [ 2.433685] NET: Registered protocol family 17
>> >>> > [ 2.438446] NET: Registered protocol family 15
>> >>> > [ 2.443420] Bluetooth: RFCOMM socket layer initialized
>> >>> > [ 2.448944] Bluetooth: RFCOMM ver 1.11
>> >>> > [ 2.452880] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>> >>> > [ 2.458526] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>> >>> > [ 2.464813] bus: 'hid': add driver generic-bluetooth
>> >>> > [ 2.465423] lib80211: common routines for IEEE802.11 drivers
>> >>> > [ 2.471496] lib80211_crypt: registered algorithm 'NULL'
>> >>> > [ 2.471527] Registering the dns_resolver key type
>> >>> > [ 2.476867] VFP support v0.3: implementor 41 architecture 3 part
>> >>> > 30
>> >>> > variant 9 rev 4
>> >>> > [ 2.485015] ThumbEE CPU extension supported.
>> >>> > [ 2.495544] omap_vc_i2c_init: I2C config for all channels must
>> >>> > match.
>> >>> > [ 2.502227] omap_vc_i2c_init: I2C config for all channels must
>> >>> > match.
>> >>> > [ 2.509918] Power Management for TI OMAP4.
>> >>> > [ 2.536773] clock: disabling unused clocks to save power
>> >>> > [ 2.542724] device: 'cpu_dma_latency': device_add
>> >>> > [ 2.542846] PM: Adding info for No Bus:cpu_dma_latency
>> >>> > [ 2.543273] device: 'network_latency': device_add
>> >>> > [ 2.543426] PM: Adding info for No Bus:network_latency
>> >>> > [ 2.543731] device: 'network_throughput': device_add
>> >>> > [ 2.543884] PM: Adding info for No Bus:network_throughput
>> >>> > [ 2.545318] regulator_init_complete: VANA: incomplete
>> >>> > constraints,
>> >>> > leaving on
>> >>> > [ 2.553283] regulator_init_complete: CLK32KG: incomplete
>> >>> > constraints,
>> >>> > leaving on
>> >>> > [ 2.562225] regulator_init_complete: VDAC: incomplete
>> >>> > constraints,
>> >>> > leaving on
>> >>> > [ 2.570343] bus: 'platform': add driver gpio-keys
>> >>> > [ 2.571807] twl_rtc twl_rtc: setting system clock to 2000-01-01
>> >>> > 00:00:00
>> >>> > UTC (946684800)
>> >>> > [ 2.581756] Freeing init memory: 312K
>> >>> > [ 2.871765] mmc0: host does not support reading read-only switch.
>> >>> > assuming write-enable.
>> >>> > [ 2.926239] mmc0: new high speed SDHC card at address 0007
>> >>> > [ 2.932373] device: 'mmc0:0007': device_add
>> >>> > [ 2.932647] bus: 'mmc': add device mmc0:0007
>> >>> > [ 2.932830] PM: Adding info for mmc:mmc0:0007
>> >>> > [ 2.933105] bus: 'mmc': driver_probe_device: matched device
>> >>> > mmc0:0007
>> >>> > with driver mmcblk
>> >>> > [ 2.933105] bus: 'mmc': really_probe: probing driver mmcblk with
>> >>> > device
>> >>> > mmc0:0007
>> >>> > [ 2.984100] mmcblk0: mmc0:0007 SD16G 14.9 GiB
>> >>> > [ 2.989074] device: '179:0': device_add
>> >>> > [ 2.989288] PM: Adding info for No Bus:179:0
>> >>> > [ 2.989746] device: 'mmcblk0': device_add
>> >>> > [ 2.990417] PM: Adding info for No Bus:mmcblk0
>> >>> > [ 2.994750] mmcblk0: p1 p2
>> >>> > [ 2.997894] device: 'mmcblk0p1': device_add
>> >>> > [ 2.998260] PM: Adding info for No Bus:mmcblk0p1
>> >>> > [ 2.998474] device: 'mmcblk0p2': device_add
>> >>> > [ 2.998687] PM: Adding info for No Bus:mmcblk0p2
>> >>> > [ 2.999420] driver: 'mmc0:0007': driver_bound: bound to device
>> >>> > 'mmcblk'
>> >>> > [ 2.999450] bus: 'mmc': really_probe: bound device mmc0:0007 to
>> >>> > driver
>> >>> > mmcblk
>> >>> > [ 3.118164] mmc1: card claims to support voltages below the
>> >>> > defined
>> >>> > range. These will be ignored.
>> >>> > [ 3.196044] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
>> >>> > [ 3.213165] mmc1: new SDIO card at address 0001
>> >>> > [ 3.218048] device: 'mmc1:0001': device_add
>> >>> > [ 3.218231] bus: 'mmc': add device mmc1:0001
>> >>> > [ 3.218383] PM: Adding info for mmc:mmc1:0001
>> >>> > [ 3.218444] bus: 'mmc': driver_probe_device: matched device
>> >>> > mmc1:0001
>> >>> > with driver mmcblk
>> >>> > [ 3.218475] bus: 'mmc': really_probe: probing driver mmcblk with
>> >>> > device
>> >>> > mmc1:0001
>> >>> > [ 3.218536] mmcblk: probe of mmc1:0001 rejects match -19
>> >>> > [ 3.219970] device: 'mmc1:0001:1': device_add
>> >>> > [ 3.220031] bus: 'sdio': add device mmc1:0001:1
>> >>> > [ 3.220184] PM: Adding info for sdio:mmc1:0001:1
>> >>> > [ 3.220397] device: 'mmc1:0001:2': device_add
>> >>> > [ 3.220428] bus: 'sdio': add device mmc1:0001:2
>> >>> > [ 3.220550] PM: Adding info for sdio:mmc1:0001:2
>> >>> > [ 3.635711] EXT4-fs (mmcblk0p2): INFO: recovery required on
>> >>> > readonly
>> >>> > filesystem
>> >>> > [ 3.643524] EXT4-fs (mmcblk0p2): write access will be enabled
>> >>> > during
>> >>> > recovery
>> >>> > [ 7.417083] EXT4-fs (mmcblk0p2): recovery complete
>> >>> > [ 7.450622] EXT4-fs (mmcblk0p2): mounted filesystem with ordered
>> >>> > data
>> >>> > mode. Opts: (null)
>> >>> > [ 8.573547] device: 'vcs7': device_add
>> >>> > [ 8.573883] PM: Adding info for No Bus:vcs7
>> >>> > [ 8.574127] device: 'vcsa7': device_add
>> >>> > [ 8.574279] PM: Adding info for No Bus:vcsa7
>> >>> > [ 21.097686] udevd[3195]: starting version 175
>> >>> > [ 21.334411] EXT4-fs (mmcblk0p2): re-mounted. Opts:
>> >>> > errors=remount-ro
>> >>> > [ 22.135772] bus: 'platform': add driver kim
>> >>> > [ 22.135864] bus: 'platform': driver_probe_device: matched device
>> >>> > kim
>> >>> > with
>> >>> > driver kim
>> >>> > [ 22.135894] bus: 'platform': really_probe: probing driver kim
>> >>> > with
>> >>> > device
>> >>> > kim
>> >>> > [ 22.136077] (stk) :sysfs entries created
>> >>> > [ 22.136199] (stk) : debugfs entries created
>> >>> > [ 22.136199] driver: 'kim': driver_bound: bound to device 'kim'
>> >>> > [ 22.136230] bus: 'platform': really_probe: bound device kim to
>> >>> > driver kim
>> >>> > [ 22.177917] bus: 'i2c': add driver bma150
>> >>> > [ 22.177978] bus: 'i2c': driver_probe_device: matched device
>> >>> > 4-0038
>> >>> > with
>> >>> > driver bma150
>> >>> > [ 22.177978] bus: 'i2c': really_probe: probing driver bma150 with
>> >>> > device
>> >>> > 4-0038
>> >>> > [ 22.178741] bma150 4-0038: BMA150 chip id error: -121
>> >>> > [ 22.184295] bma150: probe of 4-0038 failed with error -22
>> >>> > [ 22.206054] Bluetooth: Bluetooth Driver for TI WiLink - Version
>> >>> > 1.0
>> >>> > [ 22.206085] bus: 'platform': add driver btwilink
>> >>> > [ 22.467651] device: 'vcs2': device_add
>> >>> > [ 22.467834] PM: Adding info for No Bus:vcs2
>> >>> > [ 22.468109] device: 'vcsa2': device_add
>> >>> > [ 22.468231] PM: Adding info for No Bus:vcsa2
>> >>> > [ 22.523498] device: 'vcs3': device_add
>> >>> > [ 22.523651] PM: Adding info for No Bus:vcs3
>> >>> > [ 22.524017] device: 'vcsa3': device_add
>> >>> > [ 22.524200] PM: Adding info for No Bus:vcsa3
>> >>> > [ 22.568725] device: 'vcs4': device_add
>> >>> > [ 22.568969] PM: Adding info for No Bus:vcs4
>> >>> > [ 22.569091] device: 'vcsa4': device_add
>> >>> > [ 22.569274] PM: Adding info for No Bus:vcsa4
>> >>> > [ 22.611572] device: 'vcs5': device_add
>> >>> > [ 22.611724] PM: Adding info for No Bus:vcs5
>> >>> > [ 22.611846] device: 'vcsa5': device_add
>> >>> > [ 22.612182] PM: Adding info for No Bus:vcsa5
>> >>> > [ 22.655059] device: 'vcs6': device_add
>> >>> > [ 22.658660] PM: Adding info for No Bus:vcs6
>> >>> > [ 22.658782] device: 'vcsa6': device_add
>> >>> > [ 22.658935] PM: Adding info for No Bus:vcsa6
>> >>> > [ 23.272979] bus: 'sdio': add driver wl1271_sdio
>> >>> > [ 23.273040] bus: 'sdio': driver_probe_device: matched device
>> >>> > mmc1:0001:1
>> >>> > with driver wl1271_sdio
>> >>> > [ 23.273071] bus: 'sdio': really_probe: probing driver wl1271_sdio
>> >>> > with
>> >>> > device mmc1:0001:1
>> >>> > [ 23.411376] wl1271_sdio: probe of mmc1:0001:1 rejects match -19
>> >>> > [ 23.411437] bus: 'sdio': driver_probe_device: matched device
>> >>> > mmc1:0001:2
>> >>> > with driver wl1271_sdio
>> >>> > [ 23.411468] bus: 'sdio': really_probe: probing driver wl1271_sdio
>> >>> > with
>> >>> > device mmc1:0001:2
>> >>> > [ 23.423614] Registering platform device 'wl1271'. Parent at
>> >>> > platform
>> >>> > [ 23.423645] device: 'wl1271': device_add
>> >>> > [ 23.423675] bus: 'platform': add device wl1271
>> >>> > [ 23.423797] PM: Adding info for platform:wl1271
>> >>> > [ 23.424835] wl1271_sdio mmc1:0001:2: firmware: requesting
>> >>> > ti-connectivity/wl1271-nvs.bin
>> >>> > [ 23.424865] device: 'mmc1:0001:2': device_add
>> >>> > [ 23.425018] PM: Adding info for No Bus:mmc1:0001:2
>> >>> > [ 23.527252] device: 'mmc1:0001:2': device_unregister
>> >>> > [ 23.527252] PM: Removing info for No Bus:mmc1:0001:2
>> >>> > [ 23.527801] device: 'phy0': device_add
>> >>> > [ 23.528198] PM: Adding info for No Bus:phy0
>> >>> > [ 23.529266] device: 'wlan0': device_add
>> >>> > [ 23.530029] PM: Adding info for No Bus:wlan0
>> >>> > [ 23.534576] wl1271: loaded
>> >>> > [ 23.534576] driver: 'mmc1:0001:2': driver_bound: bound to device
>> >>> > 'wl1271_sdio'
>> >>> > [ 23.534606] bus: 'sdio': really_probe: bound device mmc1:0001:2
>> >>> > to
>> >>> > driver
>> >>> > wl1271_sdio
>> >>> > [ 23.908355] init: udev-fallback-graphics main process (3485)
>> >>> > terminated
>> >>> > with status 1
>> >>> > [ 24.174133] wl1271_sdio mmc1:0001:2: firmware: requesting
>> >>> > ti-connectivity/wl127x-fw-3.bin
>> >>> > [ 24.174163] device: 'mmc1:0001:2': device_add
>> >>> > [ 24.174530] PM: Adding info for No Bus:mmc1:0001:2
>> >>> > [ 24.236267] device: 'mmc1:0001:2': device_unregister
>> >>> > [ 24.236297] PM: Removing info for No Bus:mmc1:0001:2
>> >>> > [ 24.630584] wl1271: firmware booted (Rev 6.3.0.0.77)
>> >>> > [ 144.371612] init: alsa-restore main process (3613) terminated
>> >>> > with
>> >>> > status
>> >>> > 19
>> >>> > [ 144.858551] init: plymouth-upstart-bridge main process (3509)
>> >>> > killed
>> >>> > by
>> >>> > TERM signal
>> >>> > [ 144.872467] init: lightdm main process (3639) terminated with
>> >>> > status
>> >>> > 1
>> >>> > [ 145.428863] init: plymouth-stop pre-start process (3841)
>> >>> > terminated
>> >>> > with
>> >>> > status 1
>> >>> > [ 275.520446] bus: 'platform': remove driver btwilink
>> >>> > [ 275.520538] driver: 'btwilink': driver_release
>> >>> > [ 301.856811] Bluetooth: Bluetooth Driver for TI WiLink - Version
>> >>> > 1.0
>> >>> > [ 301.856842] bus: 'platform': add driver btwilink
>> >>> > [ 381.320312] bus: 'platform': remove driver btwilink
>> >>> > [ 381.320404] driver: 'btwilink': driver_release
>> >>> > [ 416.043853] Bluetooth: Bluetooth Driver for TI WiLink - Version
>> >>> > 1.0
>> >>> > [ 416.043914] bus: 'platform': add driver btwilink
>> >>> > [ 564.258239] bus: 'platform': remove driver btwilink
>> >>> > [ 564.258331] driver: 'btwilink': driver_release
>> >>> > [ 566.044036] Bluetooth: Bluetooth Driver for TI WiLink - Version
>> >>> > 1.0
>> >>> > [ 566.044067] bus: 'platform': add driver btwilink
>> >>> >
>> >>> > On Fri, Aug 10, 2012 at 7:22 PM, Pavan Savoy <pavan.sa...@gmail.com>
>> >>> > wrote:
>> >>> >>
>> >>> >> Hi,
>> >>> >>
>> >>> >> On Fri, Aug 10, 2012 at 6:05 PM, John Tobias
>> >>> >> <john.tobias...@gmail.com>
>> >>> >> wrote:
>> >>> >> > Hi Pavan,
>> >>> >> >
>> >>> >> > I have a follow up question, I got the latest kernel being used
>> >>> >> > by
>> >>> >> > ubuntu
>> >>> >> > (3.2.24), I did cross compile, the wifi is working but when I do
>> >>> >> > the
>> >>> >> > hcitool
>> >>> >> > dev, it did not detect the hcixx.
>> >>> >>
>> >>> >> Do you happen to have btwilink.ko built in ? lsmod would show if it
>> >>> >> exists, try and execute a modprobe btwilink.ko if not.
>> >>> >> Also, can you check up on the following sysfs entries ?
>> >>> >>
>> >>> >> /sys/devices/platform/kim ? & /sys/devices/platform/btwilink.
>> >>> >>
>> >>> >> > I am just wondering if there's a step to follow to detect the
>> >>> >> > hcix.
>> >>> >> > I
>> >>> >> > loaded
>> >>> >> > the bluetooth driver, hci_uart.
>> >>> >> >
>> >>> >> >
>> >>> >> > Regards,
>> >>> >> >
>> >>> >> > John
>> >>> >> >
>> >>> >> >
>> >>> >> > On Wed, Aug 8, 2012 at 8:05 AM, Pavan Savoy
>> >>> >> > <pavan.sa...@gmail.com>
>> >>> >> > wrote:
>> >>> >> >>
>> >>> >> >> On Wed, Aug 8, 2012 at 12:39 AM, Martin Maurer
>> >>> >> >> <meinemailingli...@online.de> wrote:
>> >>> >> >> > Hello Pavan,
>> >>> >> >> >
>> >>> >> >> > is there a description of the commands / events you sent to
>> >>> >> >> > the
>> >>> >> >> > module?
>> >>> >> >> > Are the vendor specific command / events and normal BT LE
>> >>> >> >> > commands /
>> >>> >> >> > events
>> >>> >> >> > included somewhere in a datasheet
>> >>> >> >> > of the Bluetooth chip?
>> >>> >> >>
>> >>> >> >> Yes, they are vendor specific commands, They seem to be only
>> >>> >> >> applicable to WL1273L, don't have either a device or data-sheet
>> >>> >> >> at
>> >>> >> >> end
>> >>> >> >> - right away to refer to them.
>> >>> >> >> But those are related to LE reset and LE enable.
>> >>> >> >>
>> >>> >> >> > Best regards,
>> >>> >> >> >
>> >>> >> >> > Martin
>> >>> >> >> >
>> >>> >> >> > ----- Original Message -----
>> >>> >> >> > From: John Tobias
>> >>> >> >> > To: pandaboard@googlegroups.com
>> >>> >> >> > Sent: Tuesday, August 07, 2012 10:15 PM
>> >>> >> >> > Subject: Re: [pandaboard] Enabling Bluetooth LE
>> >>> >> >> >
>> >>> >> >> > Here are the output:
>> >>> >> >> >
>> >>> >> >> > < HCI Command: ogf 0x3f, ocf 0x015b, plen 2
>> >>> >> >> > 01 00
>> >>> >> >> >> HCI Event: 0x0e plen 4
>> >>> >> >> > 01 5B FD 1F
>> >>> >> >> > < HCI Command: ogf 0x3f, ocf 0x01dd, plen 1
>> >>> >> >> > 01
>> >>> >> >> >> HCI Event: 0x0e plen 4
>> >>> >> >> > 01 DD FD 00
>> >>> >> >> > Supported link layer states:
>> >>> >> >> > YES Non-connectable Advertising State
>> >>> >> >> > YES Scannable Advertising State
>> >>> >> >> > YES Connectable Advertising State
>> >>> >> >> > YES Directed Advertising State
>> >>> >> >> > YES Passive Scanning State
>> >>> >> >> > YES Active Scanning State
>> >>> >> >> > YES Initiating State/Connection State in Master Role
>> >>> >> >> > YES Connection State in the Slave Role
>> >>> >> >> > YES Non-connectable Advertising State and Passive
>> >>> >> >> > Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > YES Scannable Advertising State and Passive Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > YES Connectable Advertising State and Passive Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > YES Directed Advertising State and Passive Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Non-connectable Advertising State and Active
>> >>> >> >> > Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Scannable Advertising State and Active Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Connectable Advertising State and Active Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Directed Advertising State and Active Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Non-connectable Advertising State and Initiating
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Scannable Advertising State and Initiating State
>> >>> >> >> > combination
>> >>> >> >> > NO Non-connectable Advertising State and Master Role
>> >>> >> >> > combination
>> >>> >> >> > NO Scannable Advertising State and Master Role
>> >>> >> >> > combination
>> >>> >> >> > NO Non-connectable Advertising State and Slave Role
>> >>> >> >> > combination
>> >>> >> >> > NO Scannable Advertising State and Slave Role
>> >>> >> >> > combination
>> >>> >> >> > NO Passive Scanning State and Initiating State
>> >>> >> >> > combination
>> >>> >> >> > NO Active Scanning State and Initiating State
>> >>> >> >> > combination
>> >>> >> >> > NO Passive Scanning State and Master Role combination
>> >>> >> >> > NO Active Scanning State and Master Role combination
>> >>> >> >> > NO Passive Scanning State and Slave Role combination
>> >>> >> >> > NO Active Scanning State and Slave Role combination
>> >>> >> >> > NO Initiating State and Master Role
>> >>> >> >> > combination/Master
>> >>> >> >> > Role
>> >>> >> >> > and
>> >>> >> >> > Master Role combination
>> >>> >> >> > < HCI Command: ogf 0x3f, ocf 0x015b, plen 2
>> >>> >> >> > 01 00
>> >>> >> >> >> HCI Event: 0x0e plen 4
>> >>> >> >> > 01 5B FD 1F
>> >>> >> >> > Supported link layer states:
>> >>> >> >> > YES Non-connectable Advertising State
>> >>> >> >> > YES Scannable Advertising State
>> >>> >> >> > YES Connectable Advertising State
>> >>> >> >> > YES Directed Advertising State
>> >>> >> >> > YES Passive Scanning State
>> >>> >> >> > YES Active Scanning State
>> >>> >> >> > YES Initiating State/Connection State in Master Role
>> >>> >> >> > YES Connection State in the Slave Role
>> >>> >> >> > YES Non-connectable Advertising State and Passive
>> >>> >> >> > Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > YES Scannable Advertising State and Passive Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > YES Connectable Advertising State and Passive Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > YES Directed Advertising State and Passive Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Non-connectable Advertising State and Active
>> >>> >> >> > Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Scannable Advertising State and Active Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Connectable Advertising State and Active Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Directed Advertising State and Active Scanning
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Non-connectable Advertising State and Initiating
>> >>> >> >> > State
>> >>> >> >> > combination
>> >>> >> >> > NO Scannable Advertising State and Initiating State
>> >>> >> >> > combination
>> >>> >> >> > NO Non-connectable Advertising State and Master Role
>> >>> >> >> > combination
>> >>> >> >> > NO Scannable Advertising State and Master Role
>> >>> >> >> > combination
>> >>> >> >> > NO Non-connectable Advertising State and Slave Role
>> >>> >> >> > combination
>> >>> >> >> > NO Scannable Advertising State and Slave Role
>> >>> >> >> > combination
>> >>> >> >> > NO Passive Scanning State and Initiating State
>> >>> >> >> > combination
>> >>> >> >> > NO Active Scanning State and Initiating State
>> >>> >> >> > combination
>> >>> >> >> > NO Passive Scanning State and Master Role combination
>> >>> >> >> > NO Active Scanning State and Master Role combination
>> >>> >> >> > NO Passive Scanning State and Slave Role combination
>> >>> >> >> > NO Active Scanning State and Slave Role combination
>> >>> >> >> > NO Initiating State and Master Role
>> >>> >> >> > combination/Master
>> >>> >> >> > Role
>> >>> >> >> > and
>> >>> >> >> > Master Role combination
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> > On Tue, Aug 7, 2012 at 1:02 PM, Pavan Savoy
>> >>> >> >> > <pavan.sa...@gmail.com>
>> >>> >> >> > wrote:
>> >>> >> >> >>
>> >>> >> >> >> On Tue, Aug 7, 2012 at 2:44 PM, John Tobias
>> >>> >> >> >> <john.tobias...@gmail.com>
>> >>> >> >> >> wrote:
>> >>> >> >> >> > thanks for the info.
>> >>> >> >> >> > Are you referring to the .bts file?
>> >>> >> >> >>
>> >>> >> >> >> Yes, a BLE enabling BTS file.
>> >>> >> >> >> In the mean-time, just for trial purposes, can you try
>> >>> >> >> >> hcitool cmd 0x3f 0x015B 0x1 0x0 & hcitool cmd 0x3f 0x01DD 0x1
>> >>> >> >> >> ?
>> >>> >> >> >> & then try hciconfig hci0 lestates ?
>> >>> >> >> >>
>> >>> >> >> >> & then hcitool cmd 0x3f 0x015B 0x1 0x0 + hciconfig hci0
>> >>> >> >> >> lestates
>> >>> >> >> >> ?
>> >>> >> >> >>
>> >>> >> >> >> >
>> >>> >> >> >> > On Tue, Aug 7, 2012 at 11:49 AM, Pavan Savoy
>> >>> >> >> >> > <pavan.sa...@gmail.com>
>> >>> >> >> >> > wrote:
>> >>> >> >> >> >>
>> >>> >> >> >> >> On Tue, Aug 7, 2012 at 1:31 PM, John Tobias
>> >>> >> >> >> >> <john.tobias...@gmail.com>
>> >>> >> >> >> >> wrote:
>> >>> >> >> >> >> > Here are the output of the two commands:
>> >>> >> >> >> >> >
>> >>> >> >> >> >> > #hcidump -X
>> >>> >> >> >> >> > HCI sniffer - Bluetooth packet analyzer ver 2.2
>> >>> >> >> >> >> > device: hci0 snap_len: 1028 filter: 0xffffffff
>> >>> >> >> >> >> > < HCI Command: LE Read Supported States (0x08|0x001c)
>> >>> >> >> >> >> > plen
>> >>> >> >> >> >> > 0
>> >>> >> >> >> >> >> HCI Event: Command Complete (0x0e) plen 8
>> >>> >> >> >> >> > LE Read Supported States (0x08|0x001c) ncmd 1
>> >>> >> >> >> >> > 0000: 0c 60 47 bc 53
>> >>> >> >> >> >> > .`G.S
>> >>> >> >> >> >> >
>> >>> >> >> >> >> > #hciconfig hci0 lestates
>> >>> >> >> >> >> > Read LE supported states on hci0 returned status 12
>> >>> >> >> >> >>
>> >>> >> >> >> >> Yep, 0x0c or 12 is for unsupported command. So the fw
>> >>> >> >> >> >> doesn't
>> >>> >> >> >> >> seem
>> >>> >> >> >> >> to
>> >>> >> >> >> >> have support for LE.
>> >>> >> >> >> >> Let me get back to you on this, need to check up what fw
>> >>> >> >> >> >> is
>> >>> >> >> >> >> upon
>> >>> >> >> >> >> the
>> >>> >> >> >> >> repository.
>> >>> >> >> >> >>
>> >>> >> >> >> >> > john
>> >>> >> >> >> >> >
>> >>> >> >> >> >> >
>> >>> >> >> >> >> >
>> >>> >> >> >> >> > On Tue, Aug 7, 2012 at 9:33 AM, Pavan Savoy
>> >>> >> >> >> >> > <pavan.sa...@gmail.com>
>> >>> >> >> >> >> > wrote:
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >> On Tue, Aug 7, 2012 at 11:15 AM, John Tobias
>> >>> >> >> >> >> >> <john.tobias...@gmail.com>
>> >>> >> >> >> >> >> wrote:
>> >>> >> >> >> >> >> > hcitool scan is working. I haveTIInit_7.6.15.bts
>> >>> >> >> >> >> >> > file.
>> >>> >> >> >> >> >> > May I
>> >>> >> >> >> >> >> > know
>> >>> >> >> >> >> >> > the
>> >>> >> >> >> >> >> > latest
>> >>> >> >> >> >> >> > version of .bts file and where can I get a copy?.
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >> Well we need to determine if the existing fw already
>> >>> >> >> >> >> >> supports
>> >>> >> >> >> >> >> LE
>> >>> >> >> >> >> >> or
>> >>> >> >> >> >> >> not.
>> >>> >> >> >> >> >> So, enable hcidump -X & then perform a hciconfig hci0
>> >>> >> >> >> >> >> lestates
>> >>> >> >> >> >> >> -
>> >>> >> >> >> >> >> and
>> >>> >> >> >> >> >> then let's see what the output says ??
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >> > Regards,
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> > John
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> > On Tue, Aug 7, 2012 at 8:42 AM, Pavan Savoy
>> >>> >> >> >> >> >> > <pavan.sa...@gmail.com>
>> >>> >> >> >> >> >> > wrote:
>> >>> >> >> >> >> >> >>
>> >>> >> >> >> >> >> >> On Mon, Aug 6, 2012 at 5:44 PM, John Tobias
>> >>> >> >> >> >> >> >> <john.tobias...@gmail.com>
>> >>> >> >> >> >> >> >> wrote:
>> >>> >> >> >> >> >> >> > Hello All,
>> >>> >> >> >> >> >> >> >
>> >>> >> >> >> >> >> >> > Is there anyone here successfully enabled the
>> >>> >> >> >> >> >> >> > Bluetooth
>> >>> >> >> >> >> >> >> > in
>> >>> >> >> >> >> >> >> > Pandaboard
>> >>> >> >> >> >> >> >> > ES
>> >>> >> >> >> >> >> >> > in
>> >>> >> >> >> >> >> >> > low energy mode?. I tried the "hcitool lescan" but
>> >>> >> >> >> >> >> >> > I
>> >>> >> >> >> >> >> >> > was
>> >>> >> >> >> >> >> >> > getting
>> >>> >> >> >> >> >> >> > an
>> >>> >> >> >> >> >> >> > input/output error.
>> >>> >> >> >> >> >> >>
>> >>> >> >> >> >> >> >> Do you have basic BT working ? hcitool scan ?
>> >>> >> >> >> >> >> >> Can you also try and enable hcidump -X before
>> >>> >> >> >> >> >> >> running
>> >>> >> >> >> >> >> >> the
>> >>> >> >> >> >> >> >> command
>> >>> >> >> >> >> >> >> ?
>> >>> >> >> >> >> >> >>
>> >>> >> >> >> >> >> >> If there is a command not allowed error which is
>> >>> >> >> >> >> >> >> happening
>> >>> >> >> >> >> >> >> then
>> >>> >> >> >> >> >> >> you
>> >>> >> >> >> >> >> >> might need a new fw .bts file.
>> >>> >> >> >> >> >> >> Also, what is the chip ID that you get ?
>> >>> >> >> >> >> >> >> TIInit_7.x.x ?
>> >>> >> >> >> >> >> >>
>> >>> >> >> >> >> >> >> > Regards,
>> >>> >> >> >> >> >> >> >
>> >>> >> >> >> >> >> >> > John
>> >>> >> >> >> >> >> >>
>> >>> >> >> >> >> >> >>
>> >>> >> >> >> >> >> >>
>> >>> >> >> >> >> >> >> --
>> >>> >> >> >> >> >> >> --Pavan Savoy
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >> >
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >>
>> >>> >> >> >> >> >> --
>> >>> >> >> >> >> >> --Pavan Savoy
>> >>> >> >> >> >> >
>> >>> >> >> >> >> >
>> >>> >> >> >> >>
>> >>> >> >> >> >>
>> >>> >> >> >> >>
>> >>> >> >> >> >> --
>> >>> >> >> >> >> --Pavan Savoy
>> >>> >> >> >> >
>> >>> >> >> >> >
>> >>> >> >> >>
>> >>> >> >> >>
>> >>> >> >> >>
>> >>> >> >> >> --
>> >>> >> >> >> --Pavan Savoy
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> --
>> >>> >> >> --Pavan Savoy
>> >>> >> >
>> >>> >> >
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> --
>> >>> >> --Pavan Savoy
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> --Pavan Savoy
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> --Pavan Savoy
>
>
--
--Pavan Savoy
Message from discussion Enabling Bluetooth LE
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2013 Google |