All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: qemu-devel@nongnu.org
Cc: "David S. Ahern" <daahern@cisco.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: more about serial ports: do they even work?
Date: Wed, 04 Feb 2009 11:17:11 +0000	[thread overview]
Message-ID: <49897937.8000203@eu.citrix.com> (raw)
In-Reply-To: <4987FCBA.7020104@msgid.tls.msk.ru>

Michael Tokarev wrote:

> David S. Ahern wrote:
>> Michael Tokarev wrote:
>>> David S. Ahern wrote:
>>>>      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.
> 
> It just means you (or, rather, your guests) never really needed to
> DROP those signal lines, only to raise them.
> 
>>>>              if (sarg | CHR_TIOCM_DTR)
>>>>                  targ |= TIOCM_DTR;
>>>>              if (sarg | CHR_TIOCM_RTS)
>>>>                  targ |= TIOCM_RTS;
> 
> Without that line above, the code never drops the two bits, once
> set they can't be "removed" anymore.
> 
> By the way, this is upstream qemu issue, not kvm one, and has to be
> pushed as such.  Good you CC'd qemu list.
> 


Either the two lines above or we could parse the whole set of possible
flags, like we do in the CHR_IOCTL_SERIAL_GET_TIOCM case.

WARNING: multiple messages have this Message-ID (diff)
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: qemu-devel@nongnu.org
Cc: KVM list <kvm@vger.kernel.org>, "David S. Ahern" <daahern@cisco.com>
Subject: Re: [Qemu-devel] Re: more about serial ports: do they even work?
Date: Wed, 04 Feb 2009 11:17:11 +0000	[thread overview]
Message-ID: <49897937.8000203@eu.citrix.com> (raw)
In-Reply-To: <4987FCBA.7020104@msgid.tls.msk.ru>

Michael Tokarev wrote:

> David S. Ahern wrote:
>> Michael Tokarev wrote:
>>> David S. Ahern wrote:
>>>>      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.
> 
> It just means you (or, rather, your guests) never really needed to
> DROP those signal lines, only to raise them.
> 
>>>>              if (sarg | CHR_TIOCM_DTR)
>>>>                  targ |= TIOCM_DTR;
>>>>              if (sarg | CHR_TIOCM_RTS)
>>>>                  targ |= TIOCM_RTS;
> 
> Without that line above, the code never drops the two bits, once
> set they can't be "removed" anymore.
> 
> By the way, this is upstream qemu issue, not kvm one, and has to be
> pushed as such.  Good you CC'd qemu list.
> 


Either the two lines above or we could parse the whole set of possible
flags, like we do in the CHR_IOCTL_SERIAL_GET_TIOCM case.

  parent reply	other threads:[~2009-02-04 11:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 20:20 more about serial ports: do they even work? Michael Tokarev
2009-01-26 20:39 ` Michael Tokarev
2009-02-02 21:27   ` David S. Ahern
2009-02-02 21:27     ` [Qemu-devel] " David S. Ahern
2009-02-02 21:32     ` Michael Tokarev
2009-02-02 21:32       ` [Qemu-devel] " Michael Tokarev
2009-02-02 21:36       ` David S. Ahern
2009-02-02 21:36         ` [Qemu-devel] " David S. Ahern
2009-02-03  8:13         ` Michael Tokarev
2009-02-03  8:13           ` [Qemu-devel] " Michael Tokarev
2009-02-03  8:41           ` Mark Marshall
2009-02-03  8:41             ` [Qemu-devel] " Mark Marshall
2009-02-04  8:09             ` Marcelo Tosatti
2009-02-04  8:09               ` [Qemu-devel] " Marcelo Tosatti
2009-02-04  8:37               ` Michael Tokarev
2009-02-04  8:37                 ` [Qemu-devel] " Michael Tokarev
2009-02-04  8:52                 ` Marcelo Tosatti
2009-02-04  8:52                   ` [Qemu-devel] " Marcelo Tosatti
2009-02-04  8:56                   ` Michael Tokarev
2009-02-04  8:56                     ` [Qemu-devel] " Michael Tokarev
2009-02-04 11:09                 ` Stefano Stabellini
2009-02-04 11:09                   ` [Qemu-devel] " Stefano Stabellini
2009-02-05 18:36                   ` David S. Ahern
2009-02-05 18:36                     ` [Qemu-devel] " David S. Ahern
2009-02-05 20:50                     ` Stefano Stabellini
2009-02-05 20:50                       ` [Qemu-devel] " Stefano Stabellini
2009-02-04 11:17           ` Stefano Stabellini [this message]
2009-02-04 11:17             ` Stefano Stabellini
2009-02-05 18:33 ` [PATCH, finally]: " Michael Tokarev

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=49897937.8000203@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=daahern@cisco.com \
    --cc=kvm@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.