> >From our experience using RFCOMM ttys is not a good idea. The bluetooth > rfcomm tty driver in the kernel is too unreliable in certain situations. We > actually have to patch our device kernels in order to get it working somewhat > correctly. > I know that RFcomm tty is a bit buggy, I've been investigating on ways to implement a user-space tty device, but I can't find anything that can apply to a 2.6 kernel. There's a hole framework but for the 2.4 branch. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Bluez-devel mailing list Bluez-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/bluez-devel
