linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lee <tony.p.lee@gmail.com>
To: jonathan@jonmasters.org
Cc: Andrei Konovalov <akonovalov@ru.mvista.com>,
	Luca Giuliani <l.giuliani@tiscali.it>,
	linuxppc-embedded@ozlabs.org
Subject: Re: Linux on Memec Virtex II Pro V4P7 Rev. 3
Date: Sat, 9 Oct 2004 21:26:37 -0700	[thread overview]
Message-ID: <470b6397041009212664b9c80e@mail.gmail.com> (raw)
In-Reply-To: <35fb2e59041009122710ab6d53@mail.gmail.com>

On Sat, 9 Oct 2004 20:27:15 +0100, Jon Masters <jonmasters@gmail.com> wrote:
> On Thu, 7 Oct 2004 19:53:52 -0700, Tony Lee <tony.p.lee@gmail.com> wrote:
> 
> > The problem I saw was that I can't turn off the interrupt at all.
> 
> On the Memec board? really?
> 

No, not on Memec,  just on our own HW.    I have the memec board, but
I don't have time to play on that one.   I got to debug the HW one week after
I was hired.    As far as I can tell, our linux for memec board doesn't load
the sysace driver.


> > Once I start one write command, the ISR keep coming in.
> 
> Ouch.

Tell me about it.  It tooks me 3+ days to id this.

> Perhaps. But that's down to your hardware guys to check the error
> output from your synthesis tool to see if this weirdly has happened.
> Our board doesn't have lines hard tied together, if that was the
> notion you were offering.

I tried to synthesize chipscope into into our VP20.  But don't have
much time for it now.  It is less of a priority since the sysace is working 
now for 1.5 months (without ISR).  Also, we use linux as Xilinux dev environment
but the chipscope only work in Windows platform.  Our HW folks
don't have time to touch Windows side of Xilinx tools.  It make it
more difficult to debug SW/HW integration issue.


> 
> > I try turn off the ISR on write with SYSACE register and
> > the ppc interrupt control register.  None of them worked.
> 
> Did you do it as per my patch, or what?

No, where can I find your patch?

> 
> Yes. We come up in 8 seconds to my firmware, and total boot time is
> around 20 seconds, without any effort to make it less. That includes
> cunning DHCP+ZeroConf scripts I wrote.
> 

That's about right,  We don't do DHCP, it comes up a bit faster.

-- 
-Tony
Having a lot of fun with Xilinx Virtex Pro II reconfigurable HW + ppc + Linux

  reply	other threads:[~2004-10-10  4:26 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
2004-10-09 19:27               ` Jon Masters
2004-10-10  4:26                 ` Tony Lee [this message]
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=470b6397041009212664b9c80e@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).