From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: AMCC yosemite 440ep PCI slot doesn't work.
Date: Tue, 25 Sep 2007 15:21:07 +0200 [thread overview]
Message-ID: <200709251521.07500.sr@denx.de> (raw)
In-Reply-To: <200709250718.51824.sr@denx.de>
On Tuesday 25 September 2007, Stefan Roese wrote:
> On Tuesday 25 September 2007, Andrew Liu wrote:
> > I have tested it on linux-2.6.19 which is from AMCC website , linux
> > 2.6.21.7 which is from linux mainline and linux-2.6.23.rc7 which is
> > from git://www.denx.de/git/linux-2.6-denx.git
> > Have the same problem.
> > I don't understand, why after enabling this PCI interrupts. in so
> > short time, produce 100,000 interrupt request (25: 100000 UIC0
> > Level eth2).
>
> Because the interrupt is somehow not acknowledged in the PCI device.
>
> I will test this on my Yosemite and let you know.
I just tested on my Yellowstone, which is nearly identical to the Yosemite.
And it works just fine with an Intel EEPRO/100.
Could you test another PCI board (ethernet, IDE, USB...)? Or do you have
access to another Yosemite or Yellowstone board?
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de
=====================================================================
prev parent reply other threads:[~2007-09-25 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 10:53 AMCC yosemite 440ep PCI slot doesn't work Andrew Liu
2007-09-21 15:14 ` Valentine Barshak
2007-09-24 9:34 ` Andrew Liu
2007-09-24 11:14 ` Stefan Roese
2007-09-24 11:20 ` Valentine Barshak
2007-09-25 2:05 ` Andrew Liu
2007-09-25 2:02 ` Andrew Liu
2007-09-25 5:18 ` Stefan Roese
2007-09-25 13:21 ` Stefan Roese [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=200709251521.07500.sr@denx.de \
--to=sr@denx.de \
--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).