There are usually two threads on AT driver. One sitting on the device to READ. So its waiting in a poll call until some data arrives to be read. The other sits on a list and waits until bearerbox main driver puts something in it and wakes the thread by doing that.On 20.08.2006, at 09:04, Akshat
Yeah, I noticed the two threads. The one which is supposed to write to the modem is the one that appears to be blocking and delaying the whole system. The outgoing_sms list is getting populated for that device but it is not waking up as soon as the message is forwarded. How can we wake this thread
Found another detail. The write thread seems to be blocking inside tcdrain() call from at2_write_line.what could be the issue here?thanks,akshatOn 8/20/06,
Akshat Choudhary [EMAIL PROTECTED] wrote:
Yeah, I noticed the two threads. The one which is supposed to write to the modem is the one that
