On Saturday 21 May 2011 03:36:47 James Steele wrote: > Hi, > > On 19 May 2011 08:43, Alan <alanbluetooth@xxxxxxxxxxx> wrote: > > Status my problems are solved for now... > > Great! I always like it when that happens. > > > From here on down the turtles appear to be all mine. Weeee.... There just had to be a splat. I may or may not need or want to implement, a credit based flow control RFComm connection. I had hoped the easiest way was to try it and see if that fixed the problem. I've hunted through the bluez Source and I cant see how I might use flow control on an RF_COMM socket.? (in c) As seen previously (prior thread) In my example in the previous post Bluez succesfully parses packets that have credit based flow control turned on. (on a socket opened by a proprietary app I want to emulate in Unix.) (when Ive seen it in the binary packets credits flow one way only?) So bluez can parse them can it send them? What sock opt or whatever do I turn on to enable credit based flow control? Do I have any control over how many buffers worth of Credit there are? I might even be happy with a solution that lies and always claims they are all available, as Im pretty sure my code runs faster that bluetooth can deliver. ========== Why ? I am emulating a proprietary protocol. and Im not absolutely certain but I am virtually certain Im sending every RFComm payload byte correctly, but the device is seemingly assuming I am busy. Thus when ask for everything thing from Start until end as, 32 bit time stamps, I get much less. The real code gets 5-6 proprietary packets (each made from 6 by 0x6D byte fragments/RFComm packets) with the 5-6 as a sequence. When I dod the same query from linux I just get nearly as much as fits in 1 proprietary packet, it sends me about 6 0x6D byte Rfcomm packets(fragments) to make just one propietary packet. I can issue more smaller requests and walk the list but Id prefer to be compatable not just equivalent. -- 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
