From: Jeff Angielski <jeff@theptrgroup.com>
To: jonathan@jonmasters.org
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] xsa_use_interrupts flag [WAS: xilinx_sysace]
Date: Thu, 23 Sep 2004 09:36:00 -0400 [thread overview]
Message-ID: <1095946560.13705.7.camel@nighteyes.localdomain> (raw)
In-Reply-To: <35fb2e59040922181249d18af6@mail.gmail.com>
On Wed, 2004-09-22 at 21:12, Jon Masters wrote:
> On Sun, 19 Sep 2004 21:18:14 +0100, Jon Masters <jonmasters@gmail.com> wrote:
>
> > It's as I thought on and off and then on again - the code checks out
> > ok (it's not pretty but it works) - and I seem to be getting unwanted
> > extra unhandled interrupts from the hardware. This driver needs a lot
> > of cleanup anyway - it doesn't handle these kinds of error state, nor
> > does it handle the removal of a mounted CompactFlash, and a dozen
> > other typical problems. I'll post a patch when I've solved the main
> > problem - moan at me by private mail if you're using this, having
> > similar issues, and feel like helping.
>
> Hi all,
>
> I have spoken to a number of people about this ongoing issue with the
> Xilinx System ACE hardware that I am using (I have a Memec board - not
> the Xilinx one) and the fact that the hardware insists on generating
> an extra interrupt on SectorWrite operations which is neither
> documented nor otherwise explainable (but I'd love it if someone would
> enlighten me).
We are using the SystemACE on our custom MPC8260 platform and I do not
recall seeing extra interrupts on the sector writes.
However, we did uncover some general interrupt issues with interrupt
handling in the PPC kernel. We were seeing a large number of BAD
interrupts in /proc/interrupts. Unfortunately, the only information I
have on the work around is this email snippet that I saved:
<begin snippet>
> > This problem was discussed on mailing list before also and you can
> > eliminate this problem by inserting a sync instruction at a
> certainplace in the 8260 interrupt handling code. See, for example,
> > http://www.geocrawler.com/archives/3/8358/2002/11/100/10173445/
> >
> > Add a __asm__ volatile("sync"); at the end of the m8260_mask_and_ack
> > function in arch/ppc/kernel/ppc8260_pic.c to fix it.
<end snippet>
Jeff Angielski
The PTR Group
next prev parent reply other threads:[~2004-09-23 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35fb2e5904090607241087442d@mail.gmail.com>
[not found] ` <35fb2e59040919131864c26952@mail.gmail.com>
2004-09-23 1:12 ` [PATCH] xsa_use_interrupts flag [WAS: xilinx_sysace] Jon Masters
2004-09-23 13:36 ` Jeff Angielski [this message]
2004-09-23 13:43 ` Jon Masters
[not found] ` <20040923045114.GF6889@thundrix.ch>
2004-09-23 13:40 ` Jon Masters
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=1095946560.13705.7.camel@nighteyes.localdomain \
--to=jeff@theptrgroup.com \
--cc=jonathan@jonmasters.org \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).