From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Bastian Blank <waldi@debian.org>, xen-devel@lists.xensource.com
Subject: Re: Re: [PATCH] make c/s 21089 work again with c/s 21092
Date: Tue, 13 Apr 2010 12:11:16 -0400 [thread overview]
Message-ID: <20100413161116.GA32695@phenom.dumpdata.com> (raw)
In-Reply-To: <4BC4AF9F020000780003A085@vpn.id2.novell.com>
On Tue, Apr 13, 2010 at 04:53:35PM +0100, Jan Beulich wrote:
> >>> Bastian Blank <waldi@debian.org> 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
next prev parent reply other threads:[~2010-04-13 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 13:36 [PATCH] make c/s 21089 work again with c/s 21092 Jan Beulich
2010-04-13 15:10 ` Bastian Blank
2010-04-13 15:53 ` Jan Beulich
2010-04-13 16:11 ` Konrad Rzeszutek Wilk [this message]
2010-04-14 7:15 ` Bastian Blank
-- strict thread matches above, loose matches on Subject: below --
2010-04-14 6:41 Jan Beulich
2010-04-14 13:25 ` 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=20100413161116.GA32695@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.