public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Frédéric Blain" <bluez@frederic-blain.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Sony PS3 sixaxis & bluez
Date: Sat, 24 Nov 2007 14:00:28 +0000	[thread overview]
Message-ID: <47482E7C.9090205@frederic-blain.com> (raw)
In-Reply-To: <1195956126.10878.444.camel@cookie.hadess.net>


[-- Attachment #1.1: Type: text/plain, Size: 1578 bytes --]


Hello Bastien,

Thanks for this, I've updated http://wiki.bluez.org/wiki/Input to 
reflect explicitly this information.

Do you know why device initiated connections are not supported  (Lake of 
time,
technical issues, ...) and if someone is working on this integration ?

Regarding your sixaxis patch, I can help to develop / test it if you want.

-- 
creber



Bastien Nocera wrote:
> On Sat, 2007-11-24 at 00:37 +0000, Frédéric Blain wrote:
>   
>> Hello,
>>
>> With the current bluez-utils version (3.22 or CVS), the PS3 bluetooth 
>> controller (Sixaxis) is
>> not recognized.
>>     
>
> The input service doesn't support device initiated connections. See:
> http://thread.gmane.org/gmane.linux.bluez.devel/12584/focus=12614
>
> <snip>
>   
>> ==== Workaround ====
>>
>> Basically, using the file /var/lib/bluetooth/xx:xx:xx:xx:xx:xx/hidd 
>> renamed as input will help since at startup,
>> bluetoothd-service-input will scan this file and fill 'GSList *devices' 
>> accordingly.
>> Also, the file /var/lib/bluetooth/xx:xx:xx:xx:xx:xx/trusts has to be 
>> updated .
>>
>> For those interested, a step by step description can be found here :
>> http://creber.free.fr/frederic-blain/index.php?n=Main.GentooOnPS3SixaxisBluetooth#Workaround.
>>     
>
> Haaa. Once I get the capabilities right in my sixaxis patch (I'll be
> able to compare the hidd generated output with the one from my patch), I
> think I'll be able to use udev to automatically add the device as
> supported via Bluetooth once connected via USB.
>
> I'll try and get to it in the week.
>
> Cheers
>
>   


[-- Attachment #1.2: Type: text/html, Size: 2445 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-11-24 14:00 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 [this message]
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

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=47482E7C.9090205@frederic-blain.com \
    --to=bluez@frederic-blain.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=hadess@hadess.net \
    /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