From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: waldi@debian.org, xen-devel@lists.xensource.com
Subject: Re: Re: [PATCH] make c/s 21089 work again with c/s 21092
Date: Wed, 14 Apr 2010 09:25:57 -0400 [thread overview]
Message-ID: <20100414132557.GD17171@phenom.dumpdata.com> (raw)
In-Reply-To: <4BC571AB020000780005C48C@vpn.id2.novell.com>
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
next prev parent reply other threads:[~2010-04-14 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 6:41 Re: [PATCH] make c/s 21089 work again with c/s 21092 Jan Beulich
2010-04-14 13:25 ` Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-13 13:36 Jan Beulich
2010-04-13 15:10 ` Bastian Blank
2010-04-13 15:53 ` Jan Beulich
2010-04-13 16:11 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100414132557.GD17171@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jbeulich@novell.com \
--cc=waldi@debian.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.