From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>,
maxk@qualcomm.com, bluez-devel@lists.sf.net, dwmw2@infradead.org
Subject: Re: [Bluez-devel] [RFC] PS3 Bluetooth quirk for HCI_FLT_CLEAR_ALL
Date: Wed, 09 May 2007 14:54:27 -0700 [thread overview]
Message-ID: <46424313.7040300@am.sony.com> (raw)
In-Reply-To: <1178694136.8628.82.camel@aeonflux.holtmann.net>
Marcel Holtmann wrote:
> Hi Geoff,
>
>> >>> [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.
>
> alternatively you can try dfu-util from the openmoko.org project. I
> never did, but it should work just quite fine.
I see this at their site:
WARNING: Dfu-util is currently broken on big-endian architectures
and this
NOTE: Upload support is currently broken
Any other ideas?
next prev parent reply other threads:[~2007-05-09 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <463F7386.6050900@am.sony.com>
2007-05-08 7:15 ` [Bluez-devel] [RFC] PS3 Bluetooth quirk for HCI_FLT_CLEAR_ALL Marcel Holtmann
2007-05-08 11:06 ` David Woodhouse
2007-05-08 13:19 ` Marcel Holtmann
2007-05-08 15:47 ` David Woodhouse
2007-05-08 16:43 ` Marcel Holtmann
2007-05-08 22:53 ` Geoff Levand
2007-05-09 2:34 ` Geoff Levand
2007-05-09 7:02 ` Marcel Holtmann
2007-05-09 21:54 ` Geoff Levand [this message]
2007-12-16 0:19 ` Geoff Levand
2007-12-16 1:24 ` Marcel Holtmann
2007-12-17 6:23 ` Geoff Levand
2007-12-17 19:08 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46424313.7040300@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).