From: Alex Ivanov <gnidorah@p0n4ik.tk>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] Fix interrupt routing for C8000 serial ports
Date: Wed, 04 Sep 2013 22:51:02 +0400 [thread overview]
Message-ID: <165661378320662@web27g.yandex.ru> (raw)
In-Reply-To: <20130730000216.94DB91D232@solo.franken.de>
30.07.2013, 05:00, "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>:
> We can't use dev->mod_index for selecting the interrupt routing entry,
> because it's not an index into interrupt routing table. It will be even
> wrong on a machine with 2 CPUs (4 cores). But all needed information is
> contained in the PAT entries for the serial ports. mod[0] contains the iosapic
> address and mod_info has some indications for the interrupt input (at least
> it looks like it). This patch implements the searching for the right iosapic
> and uses this interrupt input information.
Thomas,
Thanks for the fix! This indeed fixed serial on my c8000. Now, there is no
need to use PDC_CONSOLE on this machine anymore.
prev parent reply other threads:[~2013-09-04 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 0:02 [PATCH] Fix interrupt routing for C8000 serial ports Thomas Bogendoerfer
2013-09-04 18:51 ` Alex Ivanov [this message]
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=165661378320662@web27g.yandex.ru \
--to=gnidorah@p0n4ik.tk \
--cc=linux-parisc@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox