From: Amos Waterland Subject: Re: [PATCH] Paravirt framebuffer use xvc as console [4/5] Date: Mon, 23 Oct 2006 16:36:45 -0400 Message-ID: <20061023203645.GA8283@kvasir.watson.ibm.com> References: <1157227130.11059.44.camel@aglarond.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1157227130.11059.44.camel@aglarond.local> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Katz Cc: Jimi Xenidis , xen-devel , Markus Armbruster , Hollis Blanchard List-Id: xen-devel@lists.xenproject.org Hi Jeremy. The latest LANANA device list did not pick up my request for 204/187, giving that combination to Xilinx uartlite instead. I am just wondering if I should try again or if you are going to go with the experimental range? On Sat, Sep 02, 2006 at 03:58:50PM -0400, Jeremy Katz wrote: > This is the patch from Amos Waterland for the xenconsole to > use /dev/xvc0 instead of taking over ttys. I've fixed a few places > which needed to check for XVC mode in addition to serial mode. Also, > until LANANA responds with an official minor, I've adjusted it to use > char 250/187 (in the experimental range) as opposed to 204/187. > > (Should be identical to this patch from last time) > > Signed-off-by: Jeremy Katz > Cc: Amos Waterland