qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Ahern" <daahern@cisco.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: more about serial ports: do they even work?
Date: Mon, 02 Feb 2009 14:36:14 -0700	[thread overview]
Message-ID: <4987674E.9050201@cisco.com> (raw)
In-Reply-To: <49876678.4090808@msgid.tls.msk.ru>



Michael Tokarev wrote:
> David S. Ahern wrote:
>> I don't recall seeing a followup to this post.
>>
>> To put Michael's second suggestion into patch form, the following fixes
>> the problem for me:
>>
>> --- kvm-81.orig/qemu/qemu-char.c        2008-12-14 06:16:27.000000000 -0700
>> +++ kvm-81/qemu/qemu-char.c     2009-02-02 14:12:20.000000000 -0700
>> @@ -1078,20 +1078,21 @@
>>              if (sarg | TIOCM_DTR)
>>                  *targ |= CHR_TIOCM_DTR;
>>              if (sarg | TIOCM_RTS)
>>                  *targ |= CHR_TIOCM_RTS;
>>          }
>>          break;
>>      case CHR_IOCTL_SERIAL_SET_TIOCM:
>>          {
>>              int sarg = *(int *)arg;
>>              int targ = 0;
>> +            ioctl(s->fd_in, TIOCMGET, &targ);
> 
> here, one more operation is necessary:
>                targ &= ~(TIOCM_DTR|TIOCM_RTS);
> 


Interesting. that change was not needed to fix my problem.

david


>>              if (sarg | CHR_TIOCM_DTR)
>>                  targ |= TIOCM_DTR;
>>              if (sarg | CHR_TIOCM_RTS)
>>                  targ |= TIOCM_RTS;
>>              ioctl(s->fd_in, TIOCMSET, &targ);
>>          }
>>          break;
>>      default:
>>          return -ENOTSUP;
>>      }
>>
>> Is this approach palatable to folks?
>>
>> david
> 
> /mjt

  reply	other threads:[~2009-02-02 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <497E1B15.2090908@msgid.tls.msk.ru>
     [not found] ` <497E1F7D.90300@msgid.tls.msk.ru>
2009-02-02 21:27   ` [Qemu-devel] Re: more about serial ports: do they even work? David S. Ahern
2009-02-02 21:32     ` Michael Tokarev
2009-02-02 21:36       ` David S. Ahern [this message]
2009-02-03  8:13         ` Michael Tokarev
2009-02-03  8:41           ` Mark Marshall
2009-02-04  8:09             ` Marcelo Tosatti
2009-02-04  8:37               ` Michael Tokarev
2009-02-04  8:52                 ` Marcelo Tosatti
2009-02-04  8:56                   ` Michael Tokarev
2009-02-04 11:09                 ` Stefano Stabellini
2009-02-05 18:36                   ` David S. Ahern
2009-02-05 20:50                     ` Stefano Stabellini
2009-02-04 11:17           ` Stefano Stabellini

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=4987674E.9050201@cisco.com \
    --to=daahern@cisco.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --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).