<Faisal>
ok i finally got my bluetooth keyboard running with linux
<Faisal>
at last
<utente>
Faisal, how you did it?
\\Mr_C\\ has quit [Quit: .]
<Faisal>
utente: well, first of all 'sudo apt-get install bluetooth bluez-utils bluez-compat', then you need to upload the bluetooth firmware to the chip : sudo /usr/bin/brcm_patchram_plus -d --patchram /lib/firmware/ap6210/bcm20710a1.hcd --enable_hci --bd_addr 11:22:33:44:55:66 --no2bytes /dev/ttyS1 , then you need to pair your keyboard :sudo bluez-simple-agent hci0 <macaddressofthekeyboard >; then trust it : sudo bluez-test-device trusted
<Faisal>
<macaddressofthekeyboard> yes ; then simply run : sudo hidd --connect <macaddressoftheykeyboard> and you are good to go
<Faisal>
works with mice as well
<utente>
good
<utente>
but it get again connection after a reboot?
<utente>
but it get again automatically connection after a reboot?
<Faisal>
at the moment no and i know why
<Faisal>
its simply because i cannot figure out how to load the damn firmware at boottime
<Faisal>
especially because for some reason it needs to be ran twice before it actually works
<utente>
maibe you ahave to set a script to pair the keyboard at boot.
<Faisal>
pairing is a one time process so pairing doesnt need to be done again
<utente>
crate your own script.sh, make it runnable and add it to an existing script present inside /etc/init.d/<another-script>
<Faisal>
only the connection needs to be made again (sudo hidd --connect) and that could be setup eaily at startup, but the firmware needs to uploaded to the chip first
<Faisal>
utente: will most likely do that, but i have to make the script flexible enough to make sure bluetooth is up at bootime everytime
<utente>
you can crreate a new one script and force it to run afher bluettoth stack is loade and running.
<utente>
man update-rc.d for furter info.
<Faisal>
utente: yep most likely, im new to this whole thing but ill get it figured out, i may even sugest an update to the wiki
<utente>
at least you fcan edit the bluetooth script and ad at the end sudo hidd --connect
<Faisal>
yep, but there is a file, /etc/bluetooth/rfcomm where you can set the ttsys1 device to be binded at startup
<Faisal>
so its all about getting the firmware loaded at boottime i guess
<Faisal>
before that
<Faisal>
my next step now is getting 2d and 3d acceleration
<Faisal>
anyone has an idea where to start ?
<utente>
Faisal, un cb1 or cb2?
<Faisal>
utente: cb3 cubietruck
<utente>
it is A20 sof, as is on CB2
<utente>
soc*
<utente>
i can't help, sorry
<Faisal>
np
Cpt-Oblivious has quit [Ping timeout: 252 seconds]
<wickwire>
Faisal: you can try the mali libs
<Faisal>
wickwire: i got the mali module loaded in etc/modules, but what you mean by mali libs please ?
wickwire has quit [Remote host closed the connection]
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
weetabeex has joined #cubieboard
<weetabeex>
hey all
<weetabeex>
was wondering if anyone knows what's the maximum amps I can supply on the cubietruck's 12V 2-pin connector (labeled as NC/12V if I understand it correctly)
DropBear has quit [Ping timeout: 245 seconds]
DropBear has joined #cubieboard
joedj has joined #cubieboard
joedj_ has joined #cubieboard
joedj has quit [Remote host closed the connection]
joedj_ is now known as joedj
jesselang has quit [Ping timeout: 252 seconds]
<Turl>
weetabeex: you mean from? it's an output connector isn't it?