From: Tony Lee <tony.p.lee@gmail.com>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Andrei Konovalov <akonovalov@ru.mvista.com>,
linuxppc-embedded@ozlabs.org,
Luca Giuliani <l.giuliani@tiscali.it>
Subject: Re: Linux on Memec Virtex II Pro V4P7 Rev. 3
Date: Thu, 7 Oct 2004 19:53:52 -0700 [thread overview]
Message-ID: <470b6397041007195371655afb@mail.gmail.com> (raw)
In-Reply-To: <4165DB83.8080001@jonmasters.org>
On Fri, 08 Oct 2004 01:12:51 +0100, Jon Masters <jonathan@jonmasters.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> >
> The polled approach is worse IMO although I agree that there is very
> little overhead in the actual ISR. Where the author went wrong (well
> perhaps not wrong per se but didn't provide enough protection) was in
> the unlikely case that the hardware is braindead and generates
> interrupts that you didn't ask it to - the xsysace driver should also
> catch interrupts when we're QUEUE_EMPTY and should not try to manipulate
> an empty request queue.
>
> Jon.
The problem I saw was that I can't turn off the interrupt at all.
Once I start one write command, the ISR keep coming in.
I review the verilog code and schematic multiple times with the
HW group but can't figure out what went wrong. My best
guess was the BUFRDY line is mix up with the ISR line some
how when write cmd and when IDEN drive command is issued.
I try turn off the ISR on write with SYSACE register and
the ppc interrupt control register. None of them worked.
Jon,
Do you think if we add a small DMA engine would help
the performance or the performance problem is caused
by the sysace firmware + the CF disk?
The sysace controller IS VERY fast on loading the bitstream
and linux boot image.
--
-Tony
Having a lot of fun with Xilinx Virtex Pro II reconfigurable HW + ppc + Linux
next prev parent reply other threads:[~2004-10-08 2:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 11:26 Linux on Memec Virtex II Pro V4P7 Rev. 3 Luca Giuliani
2004-10-05 14:12 ` Matt Porter
2004-10-05 15:15 ` Jon Masters
2004-10-05 16:05 ` Andrei Konovalov
2004-10-05 22:07 ` Jon Masters
2004-10-06 15:41 ` Andrei Konovalov
2004-10-07 1:03 ` Jon Masters
2004-10-07 22:34 ` Tony Lee
2004-10-08 0:12 ` Jon Masters
2004-10-08 2:53 ` Tony Lee [this message]
2004-10-09 19:27 ` Jon Masters
2004-10-10 4:26 ` Tony Lee
2004-10-10 22:20 ` Jon Masters
-- strict thread matches above, loose matches on Subject: below --
2004-10-05 16:34 [MailServer Resend]Resending quarantined email -- use caution when opening.Re: " Administrator
2004-10-05 17:00 ` Ralph Siemsen
2005-03-24 19:01 Nguyen, Tony (US SSA)
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=470b6397041007195371655afb@mail.gmail.com \
--to=tony.p.lee@gmail.com \
--cc=akonovalov@ru.mvista.com \
--cc=jonathan@jonmasters.org \
--cc=l.giuliani@tiscali.it \
--cc=linuxppc-embedded@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).