On Tue, 2009-07-21 at 12:51 +0100, Henry Gomersall wrote: > I've tried doing the same thing using the rfcomm program. This allows > me > to set up a stable connection using: > rfcomm connect /dev/rfcomm0 'XX:XX:XX:XX:XX:XX' I've done a little more investigation. (please correct me if I am wrong) The rfcomm app speaks directly to the kernel bluetooth interface. It works fine. The sample test-serial program works through the dbus interface to the bluetooth daemon and has exactly the same problem as my test program - namely the serial link is dropped as soon as I attempt to write data to it. The problem I have is the large overhead to understanding the source tree, with the wiki being pretty out of date. I'm keen to sort this problem. Cheers, Henry -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
