![]() ![]() Is there any way to avoid this blocking and anycodings_blocking have it overflow the read buffer of B? It is unclear to me whether there is some anycodings_blocking internal feedback between the read buffer of anycodings_blocking B, or if the actual blocking is occurring in anycodings_blocking the write buffer of A due to some other anycodings_blocking internal feedback within whatever socat anycodings_blocking setup that tells blocks the writing because anycodings_blocking there is no room in the read buffer of B. However, if I start anycodings_blocking writing a large amount of data to A without anycodings_blocking reading any from B, the writing to A will anycodings_blocking eventually block until I read from B and anycodings_blocking make room in its read buffer. Which creates two virtual serial ports that anycodings_blocking I can send data across. (For the sake of the example, lets say it anycodings_blocking creates /dev/pts/2 and /dev/pts/3, referred anycodings_blocking to as A and B respectively). Is there a way to simulate this behavior anycodings_blocking using a virtual serial port with socat? For anycodings_blocking my testing so far, I have used the following anycodings_blocking command: socat -d -d pty,raw,echo=0 pty,raw,echo=0 When writing from a laptop to an external anycodings_blocking serial device that I am using, it is anycodings_blocking possible for the laptop to be writing faster anycodings_blocking than the program running on the device can anycodings_blocking actually clear its serial read buffer, anycodings_blocking leading to data being lost do to the buffer anycodings_blocking overflowing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |