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: Wed, 14 Apr 2010 09:25:57 -0400 Message-ID: <20100414132557.GD17171@phenom.dumpdata.com> References: <4BC571AB020000780005C48C@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4BC571AB020000780005C48C@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: waldi@debian.org, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Wed, Apr 14, 2010 at 07:41:30AM +0100, Jan Beulich wrote: > >>> Konrad Rzeszutek Wilk 04/13/10 6:12 PM >>> > >On Tue, Apr 13, 2010 at 04:53:35PM +0100, Jan Beulich wrote: > >> 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 > > It works with low rates of output, but in order to not use sync_console and still be able to reliably get through high rate bursts of output, interrupt driven communication seems to be the only reliable way (other than using unreasonably high values with "serial_tx_buffer="). > > And also from a more general perspective - why should legacy IRQs work, but not PCI ones? You have a good point. I actually had the darnest time getting these cards to work with Linux so was quite happy to see Xen working so well with them. I will take a look at your patch. > > Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel