From: Andrea <mariofutire@gmail.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: partial success with PS3 sixaxis
Date: Sat, 15 Feb 2014 20:41:58 +0000 [thread overview]
Message-ID: <52FFD116.2080902@gmail.com> (raw)
In-Reply-To: <2534491.XllyezJg3g@uw000953>
On 13/02/14 09:25, Szymon Janc wrote:
> Hi Andrea,
>
>
> I assume you are using bluetoothctl so do:
> agent on
> default-agent
>
> Then you should get authorization request in bluetoothctl when DS3 is connecting.
>
Hi,
I have tried on a different laptop (no more the raspberry pi, where I still have the issues I
reported in the other email), running Fedora 19.
I compiled bluez 5.14 and run it.
It is more stable and /dev/input/js0 is usable.
It is still not able to set the LEDs. This gets written in the output
Feb 15 16:55:02 localhost.localdomain bluetoothd[24620]: sixaxis: compatible device connected:
PLAYSTATION(R)3 Contr
Feb 15 16:55:02 localhost.localdomain kernel: input: PLAYSTATION(R)3 Controller as
/devices/pci0000:00/0000:00:1d.1/
Feb 15 16:55:02 localhost.localdomain kernel: sony 0005:054C:0268.000E: input,hidraw0: BLUETOOTH HID
v1.00 Joystick
Feb 15 16:55:02 localhost.localdomain bluetoothd[24620]: sixaxis: failed to set LEDS (0 bytes written)
I have tried to log the traffic for bluez and sixad (where the LEDs work), to see you can find any
difference.
http://pastebin.com/pExywtUk (this is the log from bluez where LEDs keep flashing)
http://pastebin.com/BgRUnamS (log from sixad where LEDs are set)
Happy to provide more if it can be of any help.
Andrea
next prev parent reply other threads:[~2014-02-15 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 21:31 partial success with PS3 sixaxis Andrea
2014-02-13 9:25 ` Szymon Janc
2014-02-15 12:10 ` Andrea
2014-02-28 10:47 ` Szymon Janc
2014-02-28 21:20 ` Andrea
2014-02-15 20:41 ` Andrea [this message]
2014-02-15 20:49 ` Andrea
2014-02-20 9:47 ` Szymon Janc
2014-02-22 9:19 ` Andrea
2014-02-28 10:35 ` Szymon Janc
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=52FFD116.2080902@gmail.com \
--to=mariofutire@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@tieto.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.