linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Frédéric Blain" <bluez@frederic-blain.com>
To: Adam Strojek <zwierzak2003@gmail.com>
Cc: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] ps3 sixaxis & bluez 3.22: HDI issue
Date: Tue, 20 Nov 2007 17:22:36 +0000	[thread overview]
Message-ID: <474317DC.6020204@frederic-blain.com> (raw)
In-Reply-To: <c74b6b3d0711200801k7e161bd5kff310b98c5690822@mail.gmail.com>


Hello Adam and thanks for your help.

My Sixaxis has a different Mac address than yours (00:19:C1:ED:21:31) :

# dbus-monitor --system --monitor
signal sender=3D:1.3 -> dest=3D(null destination) path=3D/org/bluez/hci0; =

interface=3Dorg.bluez.Adapter; member=3DRemoteDeviceDisconnected
   string "00:19:C1:ED:21:31"

I've set  /var/lib/bluetooth/[mac od your bluetooth]/trusts accordingly =

and let  /var/lib/bluetooth/[mac od your bluetooth]/input
as yours.

I still have the same issue.
Do you know what's the structure of  /var/lib/bluetooth/[mac od your =

bluetooth]/input ?
Should I change anything ?

Also, I forgot to specify in my original mail :

# uname -a
Linux localhost 2.6.23 #3 SMP Tue Nov 13 23:08:08 CET 2007 ppc64 Cell =

Broadband Engine, altivec supported GNU/Linux


Thanks,

-- =

creber


Adam Strojek wrote:
> I also couldn't use Sixaxis in bluetooth mode until I add this lines
> into pairing informations:
>
> $ cat /var/lib/bluetooth/[mac od your bluetooth]/input
> 05010904A101A102850175089501150026FF0081037501951315002501350045010509190=
1291381027501950D0600FF8103150026FF0005010901A10075089504350046FF0009300931=
093209358102C0050175089527090181027508953009019102750895300901B102C0A102850=
2750895300901B102C0A10285EE750895300901B102C0A10285EF750895300901B102C0C000
> 00000000 Sony Computer Entertainment Wireless Controller
>
> $ cat /var/lib/bluetooth/[mac od your bluetooth]/trusts
> 00:19:C1:E4:2D:06 [all]
>
> All Sixaxis controllers have the same Mac adress, you need only add this =
lines.
>
> 2007/11/20, Fr=E9d=E9ric Blain <bluez@frederic-blain.com>:
>   =

>> Hello,
>>
>> I'm experiencing an issue while trying to use the Sony PS3 sixaxis under
>> Linux (Gentoo). The host machine is a PS3, I use bluez 3.22 out of the
>> box (no patches) on a 64 bits kernel. I followed the documentation at
>> http://www.pabr.org/sixlinux/
>>
>> This is my first bluetooth/Bluez experience, so please forgive if I use
>> the wrong term or if I ask stupid questions ...
>>
>>
>> =3D=3D=3D=3D Problem Description =3D=3D=3D=3D
>>
>> The sixaxis is not recognized by bluetoothd-service-input.
>> According hcidump, a connection is made from the device (sixaxis)
>> to the host controler but when trying to contact HDI on control
>> channel (PSM 17),  bluetoothd-service-input generate an error:
>> "HIDP: Control: Virtual cable unplug".
>>
>> As a consequence, the device try few more times to establish the
>> connection and then give up. Sixaxis is never recognized and
>> created on the host.
>>
>>
>> =3D=3D=3D=3D Investigations =3D=3D=3D=3D
>>
>> Attaching GDB to the running hcid and bluetoothd-service-input
>> processes, I've isolated the following behavior :
>>
>> **** bluetoothd-service-input side ****
>> At startup, it setup the callback mechanism from l2cap control
>> (psm 17) & interrupt (psm 19) sockets to the function
>> connect_event(). Later, when the device ask to open the psm 17 on
>> l2cap, connect_event() is called. Then :
>>
>> connect_event()  =3D=3Dcall=3D> input_device_set_channel() =3D=3Dcall=3D=
=3D>
>> find_device() =3D=3Duse=3D=3D> GSList *devices;
>>
>> In my case, GSList *devices is NULL, so connect_event() do a /* Send
>> unplug virtual cable to unknown devices */.
>>
>> This point out that:
>>   1- The device structure for the sixaxis has not been created
>>   2- Having a device structure is a requirement to use HID
>>
>>
>> **** hcid side ****
>> Everything looks good here.
>> Once the device has completed the connection with hcid, the function
>> conn_complete() is called.
>>
>> This one will :
>>   + Send a dbus system signal via hcid_dbus_conn_complete() :
>>      signal sender=3D:1.3 -> dest=3D(null destination) path=3D/org/bluez=
/hci0; interface=3Dorg.bluez.Adapter; member=3DRemoteDeviceConnected
>>   + Read the remote name of the device
>>
>>
>>
>> **** dbus side ****
>> Everytime the sixaxis tries to establish a connection with the host, the
>> following messages appear :
>>
>> signal sender=3D:1.3 -> dest=3D(null destination) path=3D/org/bluez/hci0=
; interface=3Dorg.bluez.Adapter; member=3DRemoteDeviceConnected
>>    string "00:19:C1:ED:21:31"
>> signal sender=3D:1.3 -> dest=3D(null destination) path=3D/org/bluez/hci0=
; interface=3Dorg.bluez.Adapter; member=3DRemoteNameUpdated
>>    string "00:19:C1:ED:21:31"
>>    string "PLAYSTATION(R)3 Controller"
>> signal sender=3D:1.3 -> dest=3D(null destination) path=3D/org/bluez/hci0=
; interface=3Dorg.bluez.Adapter; member=3DRemoteDeviceDisconnected
>>    string "00:19:C1:ED:21:31"
>>
>>
>>
>> **** Other ****
>> Just to be sure, the pairing has been done using sixpair.c =3D> same iss=
ue
>> I've tested with the CVS versions of hcid and bluetoothd-service-input =
=3D> same issue.
>>
>>
>> =3D=3D=3D=3D Need Help :/ =3D=3D=3D=3D
>>
>> Could someone explains me what should be the process to establish a HID
>> connection via Bluez ?
>>
>> I think bluetoothd-service-input should listen signals from
>> /org/bluez/hci0 and create a device structure when a
>> RemoteDeviceConnected signal is intercepted, but it doesn't seem to
>> work like this.
>>
>> In bluetoothd-service-input, in which step of this process should the
>> create_device() function be called ?
>>
>> Did I miss a something ?
>>
>>
>> Please find in attachment :
>>   + Output of "hcidump -w" while trying to establish a connection
>>   + Output of "dbus-monitor --system --monitor" while trying to establis=
h a connection
>>   + Output of syslog while trying to establish a connection
>>
>> # dbus-daemon --version
>> D-Bus Message Bus Daemon 1.0.2
>>
>> Thanks in advance for your help,
>>
>> --
>> creber
>>
>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Bluez-users mailing list
>> Bluez-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-users
>>
>>
>>
>>     =



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-11-20 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 16:34 [Bluez-users] ps3 sixaxis & bluez 3.22: HDI issue Frédéric Blain
2007-11-20 16:01 ` Adam Strojek
2007-11-20 17:22   ` Frédéric Blain [this message]
     [not found]     ` <c74b6b3d0711200832p56188bc9g87060e3b69df33a@mail.gmail.com>
2007-11-23 20:13       ` Frédéric Blain

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=474317DC.6020204@frederic-blain.com \
    --to=bluez@frederic-blain.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=zwierzak2003@gmail.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).