All of lore.kernel.org
 help / color / mirror / Atom feed
From: Himanshu Raj <rhim@cc.gatech.edu>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: using com2 from dom 0 ....
Date: Tue, 13 Sep 2005 13:53:58 -0400	[thread overview]
Message-ID: <20050913175358.GG25239@cc.gatech.edu> (raw)
In-Reply-To: <0d9ef38f495a1066ddd666b0135fd1c1@cl.cam.ac.uk>

I need to use minicom in dom0 to connect to a device connected at serial port
1. I also wanted to be able to switch back and forth between xen and dom0 console,
hence I liked the console connected to serial port 0.

-Himanshu
On Tue, Sep 13, 2005 at 06:42:13PM +0100, Keir Fraser wrote:
> 
> On 13 Sep 2005, at 16:45, Himanshu Raj wrote:
> 
> >Is there a way to attach xenconsole to ttyS0 in dom0 as usual and 
> >still be able
> >to use ttyS1 (com port 2) from linux. I simply tried to use the 8250 
> >driver,
> >but loading that module fails. I don't want to use xenconsole=tty 
> >since I access
> >this machine via serial console from other machine.
> 
> I doubt it, since the native serial driver expects to grab both ports 
> and will fail completely if it fails on either one. What is wrong with 
> binding to tty instead? It's just a name -- the I/O will still go thru 
> com1 in Xen.
> 
>  -- Keir

-- 
-------------------------------------------------------------------------
Himanshu Raj
PhD Student, GaTech (www.cc.gatech.edu/~rhim)
I prefer to receive attachments in an open, non-proprietary format.
-------------------------------------------------------------------------

  reply	other threads:[~2005-09-13 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 15:45 using com2 from dom 0 Himanshu Raj
2005-09-13 17:42 ` Keir Fraser
2005-09-13 17:53   ` Himanshu Raj [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-13 19:37 Ian Pratt

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=20050913175358.GG25239@cc.gatech.edu \
    --to=rhim@cc.gatech.edu \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /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.