• 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 56
[LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS
#76
ruff Wrote:I submitted first patch, it is still being discussed. I'd appreciate if someone else will try it and report back of any issue.
Patch applied without any issue to 48 rel.
Code:
ruff@ruff:~/bluez-4.48$ patch -p1 </home/share/fakehid.patch
patching file input/device.c
patching file input/device.h
patching file input/fakehid.c
patching file input/fakehid.h
<snip configure && make && make install>
Making install in input
  CC     main.lo
  CC     manager.lo
  CC     server.lo
  CC     device.lo
  CC     fakehid.lo
  CCLD   input.la
<snip>
root@ruff:~# /opt/bluez/sbin/bluetoothd -nd
bluetoothd[14361]: Bluetooth daemon 4.48
bluetoothd[14361]: Enabling debug information
...
bluetoothd[14361]: Agent registered for hci0 at :1.688:/org/blueman/agent/adapter/hci0
bluetoothd[14361]: Changing service classes to 0x5a0104
...
bluetoothd[14361]: ps3remote_out: idle timeout, disconnecting BT channel
bluetoothd[14361]: Input: disconnect /org/bluez/14361/hci0/dev_00_21_4F_B1_F2_79
bluetoothd[14361]: ps3remote_event: Remote unpaired [45:0]

great stuff ruff -

i've successfully patched the 47 build and paired with the remote using blueman. everything works great.

EXCEPT

it unpairs within 1 minute - with the "idle timeout, disconnecting BT channel" message as in your post.

the problem is that i cant get it to re-pair without using the blueman interface again.

how are you doing this? am i missing something?

this is my tail of the daemon log;

Code:
Aug 30 22:45:26 couch bluetoothd[6236]: ps3remote_event: Passed key 108:1
Aug 30 22:45:26 couch bluetoothd[6236]: ps3remote_event: Passed key 108:0
Aug 30 22:45:29 couch bluetoothd[6236]: ps3remote_event: Passed key 103:1
Aug 30 22:45:29 couch bluetoothd[6236]: ps3remote_event: Passed key 103:0
Aug 30 22:45:59 couch bluetoothd[6236]: ps3remote_out: idle timeout, disconnecting BT channel
Aug 30 22:45:59 couch bluetoothd[6236]: Input: disconnect /org/bluez/6236/hci0/dev_00_23_06_EC_BC_B4
Aug 30 22:45:59 couch bluetoothd[6236]: ps3remote_event: Remote unpaired [103:0]
Aug 30 22:45:59 couch bluetoothd[6236]: ps3remote_event: Event failed
Aug 30 22:46:14 couch bluetoothd[6236]: adapter_get_device(00:23:06:EC:BC:B4)
Aug 30 22:46:17 couch bluetoothd[6236]: adapter_get_device(00:23:06:EC:BC:B4)
Reply
#77
I had a similar problem, simply use the init patch to use correct version of bluetoothd on bootup. Also, unplug the BT stick, and reboot the whole box after fixing the init.. When the box is still booting plug the stick back in. I think some sticks don't like warm boots. Mine keeps blinking even if i stop bluetoothd for example Smile
(Side note: Blueman no longer works, but the ps3 remote is correctly paired after boot/timeouts/etc.)
Reply
#78
Asure Wrote:I had a similar problem, simply use the init patch to use correct version of bluetoothd on bootup. Also, unplug the BT stick, and reboot the whole box after fixing the init.. When the box is still booting plug the stick back in. I think some sticks don't like warm boots. Mine keeps blinking even if i stop bluetoothd for example Smile
(Side not: Blueman no longer works, but the ps3 remote is correctly paired after boot/timeouts/etc.)


i figured out why it timed out so fast - the /etc/bluetooth/input.conf file specified 30 for the idle timeout. the comments in the file leave you to believe the unit is in minutes, but clearly its in seconds.

i got that crazy situation where blueman will no longer admin the hci0 anymore after reboot also. not sure why. guessing its because im starting the wrong version of bluez at startup.

thanks for the tip. i will look into this tonight. what init patch are you refering to though?

are you suggesting i patch it manually?

i assume you are refering to /etc/init.d/bluetooth ?

cheers.
Reply
#79
ruff, this is awesome. Thanks for going ahead and making the bluez patch... will test it out with the BD Remote on my Zotac ION MythTV front-end in the next few days.

Does the key mapping allow auto-repeat of the BD Remote keys? Since the remote used discrete press/release codes, there doesn't seem to be anyway in lirc to generate soft auto-repeat.... Although I can see that it must be possible in the input driver itself. (Here's a thread of someone trying to accomplish uinput press/release auto-repeat for an ATI remote: http://www.nabble.com/Re%3A-Linux-input-...#a21203169)



ruff Wrote:yes, with this patch it will disconnect BT channel in IdleTimeout seconds, forcing remote to sleep. If timeout specified less then 5sec (or not specified at all) - default 5min timeout will be enforced.
As for keys - yes, this patch (in posts above) is remapping keys to standard keyboard scancodes, also this mapping resembles XBMC keyboard mapping, thus you don't need to customize keymaps for quick start.
However, key remapping will not be submitted to bluez mainstream, as devs rejected it, stating that current mapping is logical, and new XInput2 is capable to handle it.
Will try to push at least option to choose alternate mapping for compatibility efforts. But after initial timeout will be accepted to mainstream.
Reply
#80
databubble Wrote:Does the key mapping allow auto-repeat of the BD Remote keys?

yes, auto repeat works for me.
Reply
#81
singleuseonly Wrote:yes, auto repeat works for me.

I applied the patch to bluez 4.50 cleanly, and installed on ubuntu 9.10 alpha. The patch works beautifully for controlling the connection/timeout of the BDRemote.

I'm using the remote with lirc (for controlling MythTV). Only some of the keys were recognized using my previous lircd.conf file. I generated a new one with irrecord (this time using key names from the existing lircd key namespace) and modified my .lircrc file accordingly.

This lird.conf file now looks as follows:

Code:
# Please make this file available to others
# by sending it to <[email protected]>    
#                                          
# this config file was automatically generated
# using lirc-0.8.5(devinput) on Thu Sep  3 00:53:10 2009
#                                                      
# contributed by                                        
#                                                      
# brand:                       PS3.rem                  
# model no. of remote control:                          
# devices being controlled by this remote:              
#                                                      

begin remote

  name  SonyBDRemote
  bits            8
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  pre_data_bits   24    
  pre_data       0x800100
  gap          33672    
  toggle_bit_mask 0x0    

      begin codes
          KEY_0                    0x0B
          KEY_1                    0x02
          KEY_2                    0x03
          KEY_3                    0x04
          KEY_4                    0x05
          KEY_5                    0x06
          KEY_6                    0x07
          KEY_7                    0x08
          KEY_8                    0x09
          KEY_9                    0x0A
          KEY_EJECTCD              0xA1
          KEY_AUDIO                0x1E
          KEY_ANGLE                0x2C
          KEY_SUBTITLE             0x14
          KEY_CLEAR                0x6F
          KEY_TIME                 0x6B
          KEY_RED                  0x41
          KEY_GREEN                0x42
          KEY_BLUE                 0x44
          KEY_YELLOW               0x43
          KEY_VIDEO                0x20
          KEY_HOMEPAGE             0x8B
          KEY_MENU                 0x57
          KEY_AB                   0x01
          KEY_OPTION               0x58
          KEY_BACK                 0x9E
          KEY_INFO                 0x2F
          KEY_DELETE               0x2D
          KEY_UP                   0x67
          KEY_DOWN                 0x6C
          KEY_LEFT                 0x69
          KEY_RIGHT                0x6A
          KEY_ENTER                0x1C
          KEY_RECORD               0xAC
          KEY_SELECT               0x6E
          KEY_RESTART              0x66
          KEY_PAGEUP               0x3B
          KEY_PAGEDOWN             0x3E
          KEY_HOME                 0x3C
          KEY_END                  0x3F
          KEY_VOLUMEDOWN           0x3D
          KEY_VOLUMEUP             0x40
          KEY_PLAY                 0xCF
          KEY_STOP                 0x80
          KEY_PAUSE                0xA4
          KEY_REWIND               0x13
          KEY_FASTFORWARD          0x21
          KEY_PREVIOUS             0x6D
          KEY_NEXT                 0x68
          KEY_SCROLLDOWN           0x33
          KEY_SCROLLUP             0x34
      end codes

end remote

This file only contains the key depress events. Instead of repeating, the BDRemote has separate events for key depress / key release.

My only trouble now is trying to enable auto-repeat via lirc or the linux event driver. I presume XBMC is not using lirc, and is taking care of the autorepeat internally somehow.

Anyone have any idea how to generate key autorepeats that can be used with lirc?
Reply
#82
Does anyone know the process of pairing the remote on the command-line? I have bluez-4.50 patched with the keycode patch and powersaving patch and it can discover the remote with this:

hcitool scan

It gives me the mac address but I'm not sure what to do next to get it to pair if that's even needed. bluez-4.50 doesn't have the hidd command anymore.
Reply
#83
databubble Wrote:My only trouble now is trying to enable auto-repeat via lirc or the linux event driver. I presume XBMC is not using lirc, and is taking care of the autorepeat internally somehow.

Anyone have any idea how to generate key autorepeats that can be used with lirc?
Autorepeat is done inside input keyboard driver. PS3BD uinput driver is just sending key-press and key-release events, input is then sending keycodes/scancodes and repeating them. That actually caused that problem with event device handler locking when unpairing with ps button hold (keypress is sent but keyrelease is not - thus input is locked in repeating keycode).

Now, since ps3remote is seen as simple keyboard, and mythtv is capable to be controlled from keyboard - you don't need lirc, just map keys as you wish
http://tips.myhdbox.com/2006/04/tip-1-my...eature.php
Here is mapping with key patch
Code:
eject-cd 1   2   3
a        4   5   6
z        7   8   9
t        DEL 0 END

F7 F8 F9 F10

d Menu F11 Esc

F12    Up    Back
Left Enter Right
v     Down   x

F1 HomePage F4
F2          F5
F3 Ins Home F6

r        Play      f
PageDown Stop PageUp
,     Play-Pause   .
Reply
#84
Ruff: passkey-agent doesn't appear to exist in bluez-4.50. What has it been replaced with?

I found some directions on how to pair but I don't know where to get the passkey-agent equivalent:

passkey-agent –default /usr/bin/bluez-pin
hcitool scan
hcitool cc
hcitool auth
Reply
#85
http://wiki.bluez.org/wiki/HOWTO/Bonding
Quote:Manually insert a pin

my copy of the man page for bluetoothd is missing this:

/var/lib/bluetooth/nn:nn:nn:nn:nn:nn/pincodes

Default location for pins for pairing devices. The file is line separated, with the following columns separated by whitespace:

nn:nn:nn:nn:nn:nn Remote device address.

n 1-8 digit pin code. User may have to consult hardware documentation in cases of hard coded pins. Try 0000
Code:
2008-10-03     Marcel Holtmann     Remove old passkey-agent and auth-agent
Remove old passkey-agent and auth-agent
Reply
#86
Ruff: I think I have it bonded now. I installed blueman to see what it's doing an I saw that it brings up the hci0 interface with page and inquiry scan enabled.

So that's as simple as running this command line:

hciconfig hci0 up piscan

Then when you type hciconfig again, you should see this:

hci0: Type: USB
BD Address: 00:1E:58:3F:64:CD ACL MTU: 384:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:15010 acl:184 sco:0 events:574 errors:0
TX bytes:5839 acl:253 sco:0 commands:149 errors:0


If both page scan and inquiry scan aren't enabled, the bdremote won't communicate with the dongle.

Then now I have hcidump running in a console and when I press a key, it is detected and throws up something like this when pressing the play button:

> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Role Change (0x12) plen 8
> HCI Event: Connect Complete (0x03) plen 11
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 17 scid 0x00ff
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
< ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x00ff result 1 status 0
Connection pending - No futher information available
< ACL data: handle 42 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Command Status (0x0f) plen 4
> ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x0004
< ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x00ff result 0 status 0
Connection successful
> HCI Event: Read Remote Supported Features (0x0b) plen 11
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 185
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x00ff flags 0x00 result 0 clen 4
MTU 185
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x00ff flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
MTU 185
< ACL data: handle 42 flags 0x02 dlen 5
L2CAP(d): cid 0x00ff len 1 [psm 17]
HIDP: Control: Virtual cable unplug
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x00ff scid 0x0040
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 19 scid 0x0100
< ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0100 result 1 status 2
Connection pending - Authorization pending
< ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0100 result 3 status 0
Connection refused - security block
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x00ff
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x00ff
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0100
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0100
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x00ff scid 0x0040
> HCI Event: Remote Name Req Complete (0x07) plen 255
< HCI Command: Read Remote Version Information (0x01|0x001d) plen 2
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
> HCI Event: Read Remote Ver Info Complete (0x0c) plen 8
> HCI Event: Command Status (0x0f) plen 4


The strange thing I've noticed though is lsinput does not list the bdremote as an input device. I know people have previously mentioned that they could see it there but is it necessary to see it there even with your patches?

So at this point I know the remote is communicating with the dongle and I'm wondering how to translate that to keypresses in mythtv.
Reply
#87
not sure how lsinput works, however, as it was already mentioned, you should see device in proc bus input list, like this
Code:
root@ruff:~# cat /proc/bus/input/devices | grep Name
N: Name="Power Button (FF)"
N: Name="Power Button (CM)"
N: Name="Macintosh mouse button emulation"
N: Name="Logitech Logitech Cordless RumblePad 2"
N: Name="PC Speaker"
N: Name="PS3 Remote Controller"
also, if running daemon in debug mode, you should see such events during pairing
Code:
bluetoothd[5117]: adapter_get_device(00:21:4F:F1:B2:07)
bluetoothd[5117]: Incoming connection on PSM 17
bluetoothd[5117]: Incoming connection on PSM 19
bluetoothd[5117]: ps3remote_setup_uinput: input 20 is opened
Last line - if patch was applied
Reply
#88
Ruff: I applied both your bdremote and powersave patch but I don't get that. lsinput lists similar info as cat /proc/bus/input/devices. Here's my output for cat /proc/bus/input/devices | grep Name:

N: Name="Power Button"
N: Name="Power Button"
N: Name="Sleep Button"
N: Name="Microsoft Natural� Ergonomic Keyboard 4000"
N: Name="Microsoft Natural� Ergonomic Keyboard 4000"
N: Name="Logitech USB-PS/2 Optical Mouse"

This is while I have the dongle plugged in and keypresses generate dump signals to hcidump.
Reply
#89
Ruff: This is what I get when I plug the bluetooth dongle in in /var/log/messages:

Sep 6 16:18:58 aragorn bluetoothd[2853]: Bluetooth daemon 4.50
Sep 6 16:18:58 aragorn bluetoothd[2856]: Starting SDP server
Sep 6 16:18:58 aragorn bluetoothd[2856]: Starting experimental netlink support
Sep 6 16:18:58 aragorn bluetoothd[2856]: Failed to find Bluetooth netlink family
Sep 6 16:18:58 aragorn bluetoothd[2856]: Failed to init netlink plugin
Sep 6 16:18:58 aragorn bluetoothd[2856]: Can't create GN bridge
Sep 6 16:18:58 aragorn bluetoothd[2856]: HCI dev 0 registered
Sep 6 16:18:58 aragorn bluetoothd[2856]: Failed to open RFKILL control device
Sep 6 16:18:58 aragorn bluetoothd[2856]: HCI dev 0 up
Sep 6 16:18:58 aragorn bluetoothd[2856]: Starting security manager 0
Sep 6 16:18:59 aragorn bluetoothd[2856]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Sep 6 16:18:59 aragorn bluetoothd[2856]: Adapter /org/bluez/2853/hci0 has been enabled
Reply
#90
Ruff: Here's a short copy of the build.log when I'm applying your patches:

Code:
>>> Unpacking source...
>>> Unpacking bluez-4.50.tar.gz to /var/tmp/portage/net-wireless/bluez-4.50/work
>>> Source unpacked in /var/tmp/portage/net-wireless/bluez-4.50/work
>>> Preparing source in /var/tmp/portage/net-wireless/bluez-4.50/work/bluez-4.50 ...
* Applying bluez-plugdev.patch ...
  [ ok ]
* Applying 4.50-conditional-libsbc.patch ...
  [ ok ]
* Applying 4.50-cups-location.patch ...
  [ ok ]
* Applying bdremote.patch ...
  [ ok ]
* Applying powersave.patch ...
  [ ok ]
* Running eautoreconf in '/var/tmp/portage/net-wireless/bluez-4.50/work/bluez-4.50' ...
* Running aclocal ...
  [ ok ]
* Running libtoolize --copy --force --automake ...
  [ ok ]
* Running aclocal ...
  [ ok ]
* Running autoconf ...
  [ ok ]
* Running autoheader ...
  [ ok ]
* Running automake --add-missing --copy ...
  [ ok ]
* Running elibtoolize in: bluez-4.50
*   Applying portage-1.5.10.patch ...
*   Applying sed-1.5.6.patch ...
*   Applying as-needed-1.5.26.patch ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/net-wireless/bluez-4.50/work/bluez-4.50 ...
* econf: updating bluez-4.50/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating bluez-4.50/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-network --enable-serial --enable-input --enable-audio --enable-service --enable-gstreamer --enable-alsa --enable-usb --enable-netlink --enable-tools --enable-bccmd --enable-hid2hci --enable-dfutool --disable-hidd --disable-pand --disable-dund --enable-cups --disable-test --enable-udevrules --enable-configfiles --disable-pcmcia --disable-debug --localstatedir=/var
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for i686-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking whether i686-pc-linux-gnu-gcc and cc understand -c and -o together... yes
checking whether i686-pc-linux-gnu-gcc accepts -fPIE... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for bison... bison -y
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by i686-pc-linux-gnu-gcc... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 1572864
checking command to parse /usr/bin/nm -B output from i686-pc-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip
checking for correct ltmain.sh version... yes
checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gcc static flag -static works... yes
checking if i686-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
checking for ppoll... yes
checking for dlopen in -ldl... yes
checking for DBUS... yes
checking for dbus_watch_get_unix_fd in -ldbus-1... yes
checking for GLIB... yes
checking for ALSA... yes
checking for clock_gettime in -lrt... yes
checking for GSTREAMER... yes
checking for USB... yes
checking for usb_get_busses in -lusb... yes
checking for usb_interrupt_read in -lusb... yes
checking for NETLINK... yes
checking for SNDFILE... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating scripts/bluetooth.rules
config.status: creating doc/version.xml
config.status: creating src/bluetoothd.8
config.status: creating bluez.pc
config.status: creating config.h
config.status: executing depfiles commands
>>> Source configured.
>>> Compiling source in /var/tmp/portage/net-wireless/bluez-4.50/work
...
--- /etc/
--- /etc/alsa/
>>> /etc/alsa/bluetooth.conf
--- /etc/dbus-1/
--- /etc/dbus-1/system.d/
>>> /etc/dbus-1/system.d/bluetooth.conf
--- /etc/bluetooth/
--- /etc/bluetooth/rfcomm.conf
>>> /etc/bluetooth/network.conf
>>> /etc/bluetooth/main.conf
--- /etc/bluetooth/input.conf
>>> /etc/bluetooth/audio.conf
--- /lib/
--- /lib/udev/
--- /lib/udev/rules.d/
>>> /lib/udev/rules.d/97-bluetooth.rules
>>> /lib/udev/rules.d/97-bluetooth-hid2hci.rules
--- /var/
--- /var/lib/
--- /var/lib/bluetooth/
--- /usr/
--- /usr/bin/
>>> /usr/bin/dfutool
>>> /usr/bin/sdptool
>>> /usr/bin/l2ping
>>> /usr/bin/hcitool
>>> /usr/bin/rfcomm
>>> /usr/bin/ciptool
--- /usr/lib/
>>> /usr/lib/libbluetooth.so -> libbluetooth.so.3.3.0
--- /usr/lib/pkgconfig/
>>> /usr/lib/pkgconfig/bluez.pc
>>> /usr/lib/libbluetooth.so.3.3.0
--- /usr/lib/gstreamer-0.10/
>>> /usr/lib/gstreamer-0.10/libgstbluetooth.so
--- /usr/lib/bluetooth/
--- /usr/lib/bluetooth/plugins/
>>> /usr/lib/bluetooth/plugins/netlink.so
--- /usr/lib/alsa-lib/
>>> /usr/lib/alsa-lib/libasound_module_ctl_bluetooth.so
>>> /usr/lib/alsa-lib/libasound_module_pcm_bluetooth.so
>>> /usr/lib/libbluetooth.so.3 -> libbluetooth.so.3.3.0
--- /usr/sbin/
>>> /usr/sbin/hciattach
>>> /usr/sbin/bccmd
>>> /usr/sbin/hciconfig
>>> /usr/sbin/hid2hci
>>> /usr/sbin/bluetoothd
--- /usr/share/
--- /usr/share/doc/
--- /usr/share/doc/bluez-4.50/
>>> /usr/share/doc/bluez-4.50/AUTHORS.bz2
>>> /usr/share/doc/bluez-4.50/README.bz2
>>> /usr/share/doc/bluez-4.50/ChangeLog.bz2
--- /usr/share/man/
--- /usr/share/man/man1/
>>> /usr/share/man/man1/hcitool.1.bz2
>>> /usr/share/man/man1/dfutool.1.bz2
>>> /usr/share/man/man1/rfcomm.1.bz2
>>> /usr/share/man/man1/ciptool.1.bz2
>>> /usr/share/man/man1/dfubabel.1.bz2
>>> /usr/share/man/man1/sdptool.1.bz2
--- /usr/share/man/man8/
>>> /usr/share/man/man8/l2ping.8.bz2
>>> /usr/share/man/man8/hciconfig.8.bz2
>>> /usr/share/man/man8/bccmd.8.bz2
>>> /usr/share/man/man8/avctrl.8.bz2
>>> /usr/share/man/man8/hciattach.8.bz2
>>> /usr/share/man/man8/bluetoothd.8.bz2
>>> /usr/share/man/man8/hid2hci.8.bz2
--- /usr/libexec/
--- /usr/libexec/cups/
--- /usr/libexec/cups/backend/
>>> /usr/libexec/cups/backend/bluetooth
--- /usr/include/
--- /usr/include/bluetooth/
>>> /usr/include/bluetooth/sdp_lib.h
>>> /usr/include/bluetooth/hci_lib.h
>>> /usr/include/bluetooth/rfcomm.h
>>> /usr/include/bluetooth/hci.h
>>> /usr/include/bluetooth/sco.h
>>> /usr/include/bluetooth/sdp.h
>>> /usr/include/bluetooth/bluetooth.h
>>> /usr/include/bluetooth/bnep.h
>>> /usr/include/bluetooth/cmtp.h
>>> /usr/include/bluetooth/hidp.h
>>> /usr/include/bluetooth/l2cap.h
>>> Regenerating /etc/ld.so.cache...
Reply
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 56

Logout Mark Read Team Forum Stats Members Help
[LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS6