qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Drlik Zbynek <drlik.zbynek@domviery.sk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] serial control DTR/DSR RTS/CTS
Date: Wed, 15 Mar 2006 10:51:08 +0100	[thread overview]
Message-ID: <4417E38C.7070205@domviery.sk> (raw)
In-Reply-To: <000801c64748$7fa7d240$0464a8c0@athlon>

Kazu wrote:

>Sent: Tuesday, March 14, 2006 4:23 PM Drlik Zbynek wrote:
>
>  
>
>>Hello.
>>My external device is connected with serial port and use hardware flow
>>control - it can switch beetwen DTR/DSR or RTS/CTS. I have instaled
>>winxp and win98 for multiplatform testing in qemu but my aplication - if
>>i wont to communicate must by set to "no flow control". In that case it
>>could by read from device without lost data, write isn't funcional -
>>much data lost.
>>When I set up some control - state of DTR or RTS are still down and
>>communication isn't allowed.
>>Qemu run under linux. When I run application in normaly installed
>>windows without qemu, the application run perfectly with any of that
>>conntrols.
>>Is there any possibility to correct this?
>>Thanks. Drlik Zbynek.
>>
>>    
>>
>
>It is a quck hack for it.
>http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060311-serial-win2kxp.patch
>  
>
It seems that it only set dtr, rts to always on but still doesn't 
reflect state on real port - now I can put hw flow control ON but the 
data is still loosing and it is not possible to write to device

>Regards,
>Kazu
>
>
>
>_______________________________________________
>Qemu-devel mailing list
>Qemu-devel@nongnu.org
>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>  
>

      reply	other threads:[~2006-03-15  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14  7:23 [Qemu-devel] serial control DTR/DSR RTS/CTS Drlik Zbynek
2006-03-14  9:20 ` Kazu
2006-03-15  9:51   ` Drlik Zbynek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4417E38C.7070205@domviery.sk \
    --to=drlik.zbynek@domviery.sk \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).