[Gta04-owner] QtMoko v41

[Christoph Mair]

On Tue, Mar 13, 2012 at 6:50 PM, Radek Polak <psonek2 at seznam.cz> wrote:
> On Tuesday 13 March 2012 12:59:23 Michele Brocco wrote:

>> * Bluetooth: I think some paths changed with the never kernel, because
>> the "bluetooth up" script does mentions wrong paths. it used to work
>> in previous versions so I guess it's really just a matter of paths.
>
> For me bluetooth is not working with 3.2 kernel. This is what i get:
>
> root at neo:~# rfkill list
> 0: GPS: GPS
>        Soft blocked: no
>        Hard blocked: no
> 1: Bluetooth: Bluetooth
>        Soft blocked: no
>        Hard blocked: no
> 2: hso-5: Wireless WAN
>        Soft blocked: no
>        Hard blocked: no
> 6: phy3: Wireless LAN
>        Soft blocked: no
>        Hard blocked: no
> root at neo:~# hciattach -s 115200 /dev/ttyO0 any 115200 flow && sleep 2
> Device setup complete
> root at neo:~# hciconfig -a
> hci0:   Type: BR/EDR  Bus: UART
>        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
>        DOWN INIT RUNNING
>        RX bytes:0 acl:0 sco:0 events:0 errors:0
>        TX bytes:39 acl:0 sco:0 commands:9 errors:0
>
> root at neo:~# hciconfig hci0 up; sleep 2
>
> Can't init device hci0: Connection timed out (110)
>
> and there is following error in dmesg repeated:
>
> 14573.206573] Bluetooth: hci0 command tx timeout

If you enable WLan (ifconfig wlan0 up) BT will work too (at least it
stops reporting errors). Maybe the chip is not powered up if only BT
is used. I have to test a bit more to find out what happens.

Christoph