Quote:/usr/include/linux/input.h

(2013-04-12, 21:11)OS/2 Wrote: That's probably because patched Bluez didn't deploy properly. I'm running Fedora.

The Fedora repo has package 4.1.1 which I first had to install together with Blueman in order to resolve dependencies. After patching BlueZ 4.9.1 and overwriting into my system/distro it hasn't appeared to have deployed properly.


EDIT:
(1)
Never-mind all that ranting. Managed to get it working now. Stopped the Bluetooth service before applying (Kitlaan's patched) Bluez-4.9.1. Here are the full details and I now have it working on Fedora/openSUSE.

http://wiki.xbmc.org/index.php?title=HOW-TO:Setup_PS3_BD_Remote

I'm actually using this solution with mythTV and here is the input.conf file to use instead:

http://www.mythtv.org/wiki/Sony_PS3_BD_Remote

Great thing is I no longer have to use LIRC with mythTV, so one less service to worry about. The only drawback with this solution is to keep swapping the input.conf when switching between XBMC and mythTV.


(2)
The other solution I considered was patching xf86-input-evdev with an option to remap keys outside of Xorg's 255 keycode limit to unused keycodes < 255. Then rebuilding. It is outlined here:

http://www.mythtv.org/wiki/Remapping_remote_control_key_codes_greater_than_255

Problem: All keycodes of the PS3-RC are detected by the current kernel/uinput. So no special drivers are needed. But due to Xorg's keycode limitation of 255, all keycodes greater than 255 get discarded by Xorg. Hence some keys work rightaway and others don't. Further those keycodes which are < 255 do still have to mapped to something meaningful.
Check it out for the PS3-RC without the above patch:

Code:

# sudo evtest /dev/input/eventX

(3)
The other solution is to edit the kernel source header:

Quote:/usr/include/linux/input.h

It contains all the keycodes which are recognised by a Linux system. You take those keycodes of the PS3-RC which are > 255 and map them to unused keycode values < 255. Then recompile the kernel for the changes to take effect.
You then use xmodmap to map keycodes < 255 to meaningful actions/events/keys. These mappings should be put in a local file .Xmodmap and would look like:

Code:

...
keycode 256 = btn0
keycode 310 = btntl
keycode 311 = btntr
keycode 312 = btntl2
keycode 313 = btntr2
keycode 315 = btnstart
keycode 317 = btnthumbl
keycode 318 = btnthumbr
...

---

I hope this brings the patch/workaround to this problem up to date.

(2013-04-23, 15:03)Bamei Wrote: writing this: sudo systemctl status bluetooth.service gets me this output

sudo: systemctl: command not found



and thank you for looking into this :-)

(2013-04-24, 07:34)MartinHJ Wrote: This all seems rather a lot of effort and inconvenience just to run one less service! My low powered Revo runs mythtv and xbmc using lirc and allows me to switch between the two from the remote without ever needing to pick up a keyboard or swap input.conf files!

(2013-05-01, 15:13)EnderEOC Wrote: Hi !

I'm having issue with my PS3 remote and xbmc.
I can't customize the keymap of the remote. I've used that tutorial http://wiki.xbmc.org/index.php?title=HOW-TO:Setup_PS3_BD_Remote
The remote works fine but the input.conf doesn't seem to be used at all. I can use the remote but since i can't customize any buttons, there's a lot of missing features

Any ideas please ? Thank you

(2013-05-01, 18:15)EnderEOC Wrote: edit : removed 4.99-2 and installed 4.94 with patch, will report after

(2013-05-01, 18:50)EnderEOC Wrote: edit 3 : how come the remote is way slower to react ? and the functions seem to be way off from input.conf like "0x40 = KEY_M # POP UP/MENU", M is player control. But when i hit the pop up menu, it just skip back 30 seconds...
And i have a lot of these in /var/log/syslog
"May 1 19:09:24 localhost bluetoothd[6842]: Input: disconnect /org/bluez/6842/hci0/dev_00_19_C1_55_39_83
May 1 19:09:26 localhost bluetoothd[6842]: Hangup or error on ps3remote socket"