From: Stefan Roese <sr@denx.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: PPC440EP/Yosemite PCI misbehavior
Date: Sun, 15 Jan 2006 10:21:13 +0100 [thread overview]
Message-ID: <200601151021.13798.sr@denx.de> (raw)
In-Reply-To: <43C88013.40800@ovro.caltech.edu>
Hi David,
On Saturday 14 January 2006 05:37, David Hawkins wrote:
> I'll go and play with the 440EP DMA controller and see if I can get
> that to burst to the PCI bus.
>
> > access to PCI I/O space causes a machine check exception.
>
> I still get this in 2.6.15, but Wolfgang Denx indicated that
> they'd tested PCI I/O pretty thoroughly, so I'm inclined to
> believe that its my driver that is at fault. I'll do a little
> more digging on that one.
I have to admit, that PCI I/O can't have worked until now on
Yosemite/Yellowstone. I just found a bug in
arch/ppc/platforms/4xx/yosemite.h:
-#define YOSEMITE_PCI_IO_BASE 0x00000000e0000000ULL
+#define YOSEMITE_PCI_IO_BASE 0x00000000e8000000ULL
Please give it a try and let me know if the problem is fixed.
Best regards,
Stefan
next prev parent reply other threads:[~2006-01-15 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 4:14 PPC440EP/Yosemite PCI misbehavior David Hawkins
2006-01-14 4:37 ` David Hawkins
2006-01-15 9:21 ` Stefan Roese [this message]
2006-01-16 16:56 ` David Hawkins
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=200601151021.13798.sr@denx.de \
--to=sr@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.