WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] [PATCH] Cleanup to irq.c

To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH] Cleanup to irq.c
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Tue, 11 Apr 2006 15:07:36 -0700
Delivery-date: Tue, 11 Apr 2006 15:08:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZdWyEXr1wr2JW/Rd6m7radQzG7QwAWQMyA
Thread-topic: [Xen-ia64-devel] [PATCH] Cleanup to irq.c
> > BTW, one confusing point here is serial_input_init() which
> > hard coded a vector (0x30), which happens to conflict with
> > eth0 vector on my tiger box. What's the purpose of this
> > registration? Actually the registration here is bogus which
> > never severs the purpose. Before my patch, previous logic
> > simply injects that vector (0x30) into guest since it's not
> > timer/ipi. Even xen wants to handle this vector, the
> > hw_interrupt_type assocated with this vector is no_irq_type
> > which is also bogus. Since it doesn't work as the code wants,
> > I simply disabled the serial_input_init to avoid unnecessary
> > warnings like " Unexpected irq vector 0x30 on cpu 0".
>
> Never understood its purpose!
> 
> Tristan.

Hardcoding 0x30 for keyboard input is very old code that goes
back to vBlades.   It's possible that it is necessary for
running Xen on ski... I'm not sure.

Dan

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

<Prev in Thread] Current Thread [Next in Thread>