[maemo-users] [maemo-users] Bad Freedom Input keyboard or poor kbdd driver on N800?
From: Rene Jensen centipede at takhis.netDate: Tue Feb 13 20:01:34 EET 2007
- Previous message: [maemo-users] Bad Freedom Input keyboard or poor kbdd driver on N800?
- Next message: [maemo-users] Python2.5 not available for ITOS 3.2006.49-2 ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Frantisek Dufka wrote: > centipede wrote: > >> Funny you mention the bluetooth stack. By now I have disemboweled the >> kbdd >> driver, which after all just opens a serial connection to /dev/rfcommN. > > Yes, there is no bluetooth magic in kbdd. And rfcomm must be reliable > In case of problems it should close connection completely, not loose > data. If this does not happen it is bluetooth protocol or device > problem. I would blame the keyboard but who knows. Try with same kbdd > recompiled on linux PC with bluetooth if it works the same. Easier said than done, I'm afraid :( A lengthy attempt to make my Toshiba Tecra M4 turn on bluetooth has failed (on the other hand, now I know how to adjust light intensity on the LCD, so, I guess I'm kind of glad?!). Drivers are in a pretty bad state. If I get near a linux machine with bluetooth, I shall test the keyboard and report back. Regards Rene Jensen
- Previous message: [maemo-users] Bad Freedom Input keyboard or poor kbdd driver on N800?
- Next message: [maemo-users] Python2.5 not available for ITOS 3.2006.49-2 ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]