Re: [Bluez-devel] [RFC] PS3 Bluetooth quirk for HCI_FLT_CLEAR_ALL

[Geoff Levand <geoffrey.levand@am.sony.com>]

Geoff Levand wrote:
> Marcel Holtmann wrote:
>> Hi David,
>> 
>>> [root@ps3 ~]# hciconfig hci0 revision
>>> hci0:   Type: USB
>>>         BD Address: 00:13:A9:79:09:C3 ACL MTU: 384:8 SCO MTU: 64:8
>>>         Build 3608
>>>         Chip version: Unknown
>>>         Max key size: 128 bit
>>>         SCO mapping:  HCI
> 
> hci0:   Type: USB
>         BD Address: 00:13:A9:73:1F:0D ACL MTU: 384:8 SCO MTU: 64:8
>         Build 3608
>         Chip version: Unknown (4h)
>         Max key size: 128 bit
>         SCO mapping:  HCI
> 
>> 
>> the chip version is unknown. That is strange. I need to modify bccmd to
>> read the raw value of the chip version. Can you quickly poke around the
>> hciconfig code to get me the raw value of it.
>> 
>>> [root@ps3 ~]# bccmd builddef
>>> Build definitions:
>>> 0x0009 - TRANSPORT_BCSP
>>> 0x000a - TRANSPORT_H4
>>> 0x000b - TRANSPORT_USB
>>> 0x000d - MAX_CRYPT_KEY_LEN_128
>>> 0x0012 - REQUIRE_8MBIT
>>> 0x0013 - RADIOTEST
>>> 0x0015 - INSTALL_FLASH
>>> 0x0016 - INSTALL_EEPROM
>>> 0x0017 - INSTALL_COMBO_DOT11
>>> 0x001d - CHIP_BASE_BC3
>>> 0x0020 - INSTALL_HCI_MODULE
>>> 0x002a - BT_VER_1_2
>>> 0x0031 - CHIP_BASE_BC4
>>> [root@ps3 ~]# bccmd buildname
>>> Build name: sly_8hci_fl_bt2.0_tachikoma-rc29_encr128_tachikoma
>>> 2006-10-16
>> 
>> This looks like a specific firmware build. Need to investigate what is
>> so special about it.
>> 
>> Can you dfutool archive it for me.
> 
> The device seems to disconnect when you try to read
> the firmware.  I get this when I try:
> 
> [root@ps3-nfs ~]# dfutool archive ps3.dfu
> Available devices with DFU support:
> 
>          1) Bus 002 Device 003: ID 054c:0267 Interface 3
> 
> Select device (abort with 0): 1
> 
> Can't identify device with DFU mode
> 
> And see this in the log:
> 
> May  8 15:50:07 ps3-nfs kernel: usb 2-2: reset high speed USB device using ps3-ehci-driver and address 3
> May  8 15:50:07 ps3-nfs kernel: usb 2-2: USB disconnect, address 3
> May  8 15:50:07 ps3-nfs hcid[2286]: HCI dev 0 down
> May  8 15:50:07 ps3-nfs hcid[2286]: Device hci0 has been disabled
> May  8 15:50:07 ps3-nfs hcid[2286]: HCI dev 0 unregistered
> May  8 15:50:07 ps3-nfs hcid[2286]: Unregister path: /org/bluez/hci0
> May  8 15:50:07 ps3-nfs hcid[2286]: Device hci0 has been removed
> 
> Any suggestions?

There seems to be some trouble in dfutool...  Others tried it with
the same results.  I'll look at it some more tomorrow.

-Geoff


*** glibc detected *** dfutool: double free or corruption (fasttop): 
0x08016080 
***
======= Backtrace: =========
/lib/libc.so.6[0x7ed0394]
/lib/libc.so.6(cfree+0xc8)[0x7ed05e8]
/usr/lib/libusb-0.1.so.4(usb_close+0x3c)[0x7fd87ec]
dfutool[0x8002840]
dfutool[0x8002ba4]
dfutool[0x8003640]
/lib/libc.so.6[0x7e6fd4c]
/lib/libc.so.6(__libc_start_main+0x144)[0x7e6ff74]
======= Memory map: ========
00100000-00103000 r-xp 00100000 00:00 0 
07e52000-07fb1000 r-xp 00000000 2a:02 693780 /lib/libc-2.5.so
07fb1000-07fbe000 ---p 0015f000 2a:02 693780 /lib/libc-2.5.so
07fbe000-07fc2000 r--p 0016c000 2a:02 693780 /lib/libc-2.5.so
07fc2000-07fc3000 rw-p 00170000 2a:02 693780 /lib/libc-2.5.so
07fc3000-07fc6000 rw-p 07fc3000 00:00 0 
07fd6000-07fde000 r-xp 00000000 2a:02 1021105 /usr/lib/libusb-0.1.so.4.4.4
07fde000-07fee000 ---p 00008000 2a:02 1021105 /usr/lib/libusb-0.1.so.4.4.4
07fee000-07ff0000 rw-p 00008000 2a:02 1021105 /usr/lib/libusb-0.1.so.4.4.4
08000000-08006000 r-xp 00000000 2a:02 281135 /usr/bin/dfutool
08015000-08016000 rw-p 00005000 2a:02 281135 /usr/bin/dfutool
08016000-08037000 rwxp 08016000 00:00 0 [heap]
0ffc0000-0ffde000 r-xp 00000000 2a:02 693779 /lib/ld-2.5.so
0ffef000-0fff0000 r--p 0001f000 2a:02 693779 /lib/ld-2.5.so
0fff0000-0fff1000 rw-p 00020000 2a:02 693779 /lib/ld-2.5.so
f7fce000-f7fcf000 rw-p f7fce000 00:00 0 
f7ffc000-f7fff000 rw-p f7ffc000 00:00 0 
ffc89000-ffc9e000 rw-p ffc89000 00:00 0 [stack]
Aborted