Hello, Thanks for the update. I applied the patch to the bluetooth-next kernel and it seems to work as expected. I ran wvdial several times in a row, and it was able to connect every time. > On Sun, Jan 05, 2014 at 04:49:42PM +0100, Gianluca Anzolin wrote: > > Hello, > > > > I looked at your problem this afternoon and I think I know what's happening: > > wvdial is opening the port with the flag O_NONBLOCK. As expected the rfcomm > > code returns immediately instead of waiting for the BT connection to come > > up. Then wvdial sends the AT commands and the writes fail. > > Hi, > > could you please test the attached patch? > > If it works and people are ok with it I'll submit it along with the other fixes > I already sent to the list. > > Thank you, > Gianluca -- Andrey Vihrov <andrey.vihrov@xxxxxxxxx>
Attachment:
signature.asc
Description: This is a digitally signed message part
