sercomm/osmocon cant send CMD after PROMPT1
zecke at selfish.org
Sun Mar 14 15:28:42 UTC 2010
On Sunday 14 March 2010 16:04:03 Nathan Fain wrote:
> I'm running into a problem with sercomm. oscmocon is unable to write()
> the CMD after PROMPT1 is received. I've attached a quick python client
> that checks from PROMPT1 and then sends CMD to confirm that it responds and
> its not something with the local system (OSX).
Yes, we turn the file descriptor into non blocking mode and then the write
might fail as we write too early. A patch to turn this code into to use the
write_queue would be totally nice... or at least respond to PROMPT from within
a ready write.
More information about the baseband-devel