public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez@frederic-blain.com,
	BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Sony PS3 sixaxis & bluez
Date: Mon, 26 Nov 2007 06:55:18 +0100	[thread overview]
Message-ID: <1196056518.4217.60.camel@aeonflux> (raw)
In-Reply-To: <47477234.9010007@free.fr>

Hi Frederic,

> With the current bluez-utils version (3.22 or CVS), the PS3 bluetooth 
> controller (Sixaxis) is
> not recognized. As a workaround, you need to use the former HID daemon 
> (hidd), rename
> the file /var/lib/bluetooth/xx:xx:xx:xx:xx:xx/hidd to 
> /var/lib/bluetooth/xx:xx:xx:xx:xx:xx/input
> and restart bluez with bluetoothd-service-input. It will now recognize 
> the controller.

no, no and no. The file formats a different. And you don't have to do anything if you have the hidd file. The input service will import it.

> Could someone explains me what should be the process to establish a HID 
> connection
> from a remote device to the host using bluetoothd-service-input ? What 
> are the
> interactions between hcid and bluetoothd-service-input ? Do you have a 
> doc / diagram
> explaining this ?

The wiki.bluez.org contains a lot of diagrams and there are slides
available from my talks that explains it.

> 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.

The short answer is no. The long one is that we have two L2CAP PSM that
handle the remote connections.

> In bluetoothd-service-input, in which step of this process should the 
> create_device()
> function be called ?  I've noticed interrupt_connect_cb() & 
> control_connect_cb() but
> I can't figure out when they will be called.

You don't do this. It is a security risk. Period. Think about what you
are proposing. Creating a device entry for a remote input device needs
user interaction.

Regards

Marcel



-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2007-11-26  5:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24  0:37 [Bluez-devel] Sony PS3 sixaxis & bluez Frédéric Blain
2007-11-25  2:02 ` Bastien Nocera
2007-11-24 14:00   ` Frédéric Blain
2007-11-26  6:17     ` Marcel Holtmann
2007-11-26  6:15   ` Marcel Holtmann
2007-11-26 17:38     ` Bastien Nocera
2007-11-26 18:59       ` Bastien Nocera
2007-11-26 21:04         ` Frédéric Blain
2007-11-27  8:32         ` Marcel Holtmann
2007-11-27 10:52           ` Bastien Nocera
2007-11-27 11:08             ` Marcel Holtmann
2007-11-26  5:55 ` Marcel Holtmann [this message]

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=1196056518.4217.60.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bluez@frederic-blain.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