[Qemu-devel] [Bug 1086745] Re: serial port data THRE comes too early

2018-03-11 Thread Launchpad Bug Tracker
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1086745 Title: serial

[Qemu-devel] [Bug 1086745] Re: serial port data THRE comes too early

2018-01-10 Thread Thomas Huth
Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? ** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

Re: [Qemu-devel] [Bug 1086745] Re: serial port data THRE comes too early

2012-12-09 Thread Kees Schoenmakers
Hello Friend, I don't think so. He is referring to a normal modem with an AT command set not responding to incoming call, which is probably a setup issue. I am referring to how the _hardware handshake_ signals from the guest environment are passed to the host. best regards Kees On 12/9/12,

Re: [Qemu-devel] [Bug 1086745] Re: serial port data THRE comes too early

2012-12-09 Thread Kees Schoenmakers
Hello, The scope traces that I sent are from 2 sources yes, the one with the 'short' RTS time is taken when the port was driven by the (Linux) guest . The trace with the correct RTS length was taken when the port was driven by the (Linux) host. Both times the same application. I looked in the

[Qemu-devel] [Bug 1086745] Re: serial port data THRE comes too early

2012-12-09 Thread Koen Hendrix
could this be related? https://bugs.launchpad.net/ubuntu/+bug/1087519 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1086745 Title: serial port data THRE comes too early Status in QEMU: New Bug

[Qemu-devel] [Bug 1086745] Re: serial port data THRE comes too early

2012-12-09 Thread Koen Hendrix
I don't think so. He is referring to a normal modem with an AT command set not responding to incoming call, which is probably a setup issue. no. please read further on; i described another oddity in the same bugreport. I am referring to how the _hardware handshake_ signals from the guest

Re: [Qemu-devel] [Bug 1086745] Re: serial port data THRE comes too early

2012-12-06 Thread Kees Schoenmakers
Hello, I have attached 2 scope shots, SCR0002.BMP shows a failing communication cycle, the upper trace is the RTS signal on the port, the lower trace shows the databytes wriiten. SCR4.BMP show how it had to be, RTS is active during the whole databytes. In general an application will issue

[Qemu-devel] [Bug 1086745] Re: serial port data THRE comes too early

2012-12-05 Thread Lei Li
Could you please give more details, like the steps to reproduce this problems. Thanks. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1086745 Title: serial port data THRE comes too early Status