| Age | Commit message (Collapse) | Author | Files | Lines |
|---|---|---|---|---|
| 2005-07-15 | opiebluez: add scanning. | mickeyl | 1 | -4/+16 |
| Ok, guys, everything until now was easy. It gets very ugly to go from here - even to just get the name of a remote device, you have to setup some filters on the bluez socket, fill in some random flags to generate a PDU that calls 'get name' and then afterwards poll until the result comes in. Nasty :/ The BlueZ kernel interface seems to be very badly (if at all) documented. All people are assuming that you use libbluetooth to talk to that stack. However since libbluetooth is GPL, we can't do that :/ Guess, we are stuck here until someone finds time and/or motivation to look into that and create some easy-to-understand examples for how to talk directly to the BlueZ kernel interface. | ||||
| 2005-07-14 | - add device class | mickeyl | 1 | -1/+39 |
| - first bits at inquiry | ||||
| 2005-07-14 | - add bool OBluetoothInterface::setUp( bool ) | mickeyl | 1 | -1/+9 |
| - add void OBluetoothInterface::isUp() const | ||||
| 2005-07-11 | don't link to libbluez since this would taint LGPL | mickeyl | 1 | -1/+1 |
| 2005-07-10 | s/opieshower/opiebluez/, infrared better goes through opienet | mickeyl | 1 | -0/+141 |
| there's the need of a connection abstraction library which bases on opienet and opiebluez in the future. It's for discussion if it makes sense in Opie 1.x | ||||
 |
index : patchwork/opie.git | |
| opie™ hacks and fixes |
| summaryrefslogtreecommitdiff |