FYI, I'm running Robert's latest Debian with beta kernel (3.13.9-bone9), and have compiled and run bluez-5.17 successfully, connecting to BLE devices with an iogear dongle plugged into a hub.
On Monday, April 14, 2014 9:46:03 AM UTC-7, don wrote: > > On 04/14/2014 09:41 AM, [email protected] <javascript:> wrote: > > I upgraded my Debian v3.8 to v3.13.9 so that I could plug a powered USB > hub into the BBB USB host so that I could plug a Rocketfish BT dongle and > my Sony sixaxis concurrently for pairing. Otherwise you can only plug one > device into the USB host at a time. I think there is more to do to support > USB. Long story short in Debian v3.8 my Rocketfish dongle was correctly > identified. In Debian v3.13.9 I get the following- > > root@arm:/# dmesg |tail > [ 1223.364177] usb 2-1: new full-speed USB device number 4 using musb-hdrc > [ 1276.911353] Bluetooth: Core ver 2.17 > [ 1276.911471] NET: Registered protocol family 31 > [ 1276.911482] Bluetooth: HCI device and connection manager initialized > [ 1276.911532] Bluetooth: HCI socket layer initialized > [ 1276.911549] Bluetooth: L2CAP socket layer initialized > [ 1276.911578] Bluetooth: SCO socket layer initialized > [ 1276.944459] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 1276.944480] Bluetooth: BNEP filters: protocol multicast > [ 1276.944530] Bluetooth: BNEP socket layer initialized > root@arm:/# hcitool dev > Devices: > root@arm:/# [ 1349.186393] usb 2-1.1: device v0a5c p4502 is not supported > [ 1349.396415] usb 2-1.2: device v0a5c p4503 is not supported > [ 1349.606618] usb 2-1.3: device v0461 p4d75 is not supported > > ...Back to the drawing board. > > > > On Tuesday, April 8, 2014 9:33:56 PM UTC-7, [email protected] wrote: >> >> Hi All, >> >> First I want to thank Robert, Jason and everyone that coded/tested to >> bring Debian to our projects. My life became considerably easier because of >> those efforts. Magnificent! >> >> The next hurdle for me has been trying to get a Sony PS3 sixaxis >> controller and the Sony wireless keyboard working with Bluetooth (Bluez). >> The problem seems to be that when I plug the controller into the USB port, >> UDEV creates input/js0 and event0 >> >> but Dmesg reports- >> >> [15105.669932] input: Sony PLAYSTATION(R)3 Controller as >> /devices/ocp.3/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input2 >> [15105.671447] usbhid 1-1:1.0: looking for a minor, starting at 96 >> [15105.672694] sony 0003:054C:0268.0002: input,hiddev0,hidraw0: USB HID >> v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on >> usb-musb-hdrc.1.auto-1/input0 >> [15105.675678] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 >> [15105.675776] hub 1-0:1.0: port 1 enable change, status 00000103 >> >> but lacks reporting the following >> >> sony xxxx:xxxx:xxxx:xxxx: Calling sixaxis_set_operational_usb >> sony xxxx:xxxx:xxxx:xxxx: Sony PS3 Controller bdaddr: xx:xx:xx:xx:xx:xx >> >> >> From what I understand there is a patch that went into Linux kernel >> since 2.6.37 but I could never find it in the changelogs. Does anyone know >> if this patch carried through to 3.8.13-bone41? >> >> Also the Bluez version we have for Debian seems to be 4.99 and the >> latest version on www.bluez.org is up to 5.17. Sixaxis looks to be fully >> supported in that version. Any chance we will be going to a newer version >> of Bluez in the near future? >> >> Thanks! >> >> >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > It should build could be a few different reasons its failing for you. If I > get time I will setup a deb install and see about compiling it. But it for > sure builds on Arch. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
