From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: [PATCH] make c/s 21089 work again with c/s 21092 Date: Tue, 13 Apr 2010 12:11:16 -0400 Message-ID: <20100413161116.GA32695@phenom.dumpdata.com> References: <4BC48F97020000780003A003@vpn.id2.novell.com> <20100413151034.GA32631@wavehammer.waldi.eu.org> <4BC4AF9F020000780003A085@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4BC4AF9F020000780003A085@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: Bastian Blank , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Apr 13, 2010 at 04:53:35PM +0100, Jan Beulich wrote: > >>> Bastian Blank 13.04.10 17:10 >>> > >On Tue, Apr 13, 2010 at 02:36:55PM +0100, Jan Beulich wrote: > >> Unfortunately the latter c/s' change to mpparse.c yielded the former > >> patch non-functional - Xen's serial port IRQ is not in IQR_DISABLED > >> state, yet must be allowed to get its trigger mode and polarity set > >> up in order for it to be usable. > > > >This looks not right. The original patch was designed to keep this > >function away from the irqs of the serial port. This patch adds another > >check for disallowing access but does not touch the IQR_DISABLED check. > > > >Please explain which machines have non-legacy configured interrupts for > >the first two serial ports. > > I'm talking about PCI serial cards - in the one case I'm working with, Can't you use polling for it? For example this is what I do for my PCI serial card: com1=115200,8n1,0xd800,0