[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] RE: [PATCH] fixed serial console support


  • To: "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Tue, 6 Dec 2005 08:39:33 -0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 06 Dec 2005 16:39:55 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcX5UYLNfVnuCPPtQc+3y+lxtWCYfwBMfnnA
  • Thread-topic: [Xen-ia64-devel] RE: [PATCH] fixed serial console support

 >    I looked a little bit at how 8250 can be left enabled and not
> interfere w/ xen console.  I don't think it's as trivial as I was
> hoping.  Even if we were to hide the specific UART xen is 
> using, I think
> there would still be a naming conflict for ttyS0 for any of the other
> UARTs.  Does anybody know why xen tries to make a fake serial line for
> dom0?  Seems like it would be easier if we did something like 
> USB serial
> devices and made up something like ttyXEN0.  I suppose it's 
> probably for
> compatibility, but unfortunately the xen console is setup 
> after the real
> serial ports are enumerated, and even if that is corrected, 
> ttyS0 isn't
> properly reserved and the serial layer blows up trying to 
> overwrite it.

It might be good to post these questions to xen-devel.

Dan

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.