I know there's not a lot of information here, but I have a program (tcpser) written to accept input on the serial port and output network packets, and vice versa (it's for interfacing a Commodore 64): http://www.quantumlink.tk/ http://www.jbrain.com/pub/linux/serial/ It compiled and ran on openSUSE 10.2 (and Ubuntu 7.04), but under 10.3 (and Ubuntu 7.10), I get a clean compile but at run time, it exits as soon as a serial packet is received with the cryptic message "I/O possible". I haven't had any success googling for this error message, does anybody have a clue what might be happening? I don't see the message in the tcpser source. -- "After the vintage season came the aftermath - and Cenbe." Glenn Holmer (Q-Link: ShadowM) http://www.lyonlabs.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 October 2007 12:23:33 Glenn Holmer wrote:
I know there's not a lot of information here, but I have a program (tcpser) written to accept input on the serial port and output network packets, and vice versa (it's for interfacing a Commodore 64):
http://www.quantumlink.tk/ http://www.jbrain.com/pub/linux/serial/
It compiled and ran on openSUSE 10.2 (and Ubuntu 7.04), but under 10.3 (and Ubuntu 7.10), I get a clean compile but at run time, it exits as soon as a serial packet is received with the cryptic message "I/O possible".
I haven't had any success googling for this error message, does anybody have a clue what might be happening? I don't see the message in the tcpser source.
"I/O possible" basically means that the application has received a SIGIO, which means there is data for it to read. Why it isn't processed is another question. Maybe the semantics of the java calls used have changed. Are you using the same version of java in all places? Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 October 2007 08:15, Anders Johansson wrote:
"I/O possible" basically means that the application has received a SIGIO, which means there is data for it to read.
Why it isn't processed is another question. Maybe the semantics of the java calls used have changed. Are you using the same version of java in all places?
Thanks for the info, that's the first clear explanation I've heard. But this isn't the Java version (tcpser4j), it's the Linux version (tcpser-1.0rc9), written in C. I compiled from source. -- "After the vintage season came the aftermath - and Cenbe." Glenn Holmer (Q-Link: ShadowM) http://www.lyonlabs.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Glenn Holmer wrote:
On Sunday 21 October 2007 08:15, Anders Johansson wrote:
"I/O possible" basically means that the application has received a SIGIO, which means there is data for it to read.
Why it isn't processed is another question. Maybe the semantics of the java calls used have changed. Are you using the same version of java in all places?
Thanks for the info, that's the first clear explanation I've heard.
But this isn't the Java version (tcpser4j), it's the Linux version (tcpser-1.0rc9), written in C. I compiled from source.
The fact that you're seeing a message (presumably triggered by a SIGIO event) means that something is catching and handling that event. Why it doesn't do anything else ... I have no idea. /Per Jessen, Zürich -- http://www.spamchek.com/ - your spam is our business. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Anders Johansson
-
Glenn Holmer
-
Per Jessen