From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Problems with PCI on 8280
Date: Thu, 17 Jan 2008 16:02:14 -0600 [thread overview]
Message-ID: <478FD066.5000803@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B039BA0D4@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
> Our problem is that we can only access the first 128MB of the
> prefetchable area.
> an access to 0x87ff_ffff works (after ioremap), while an access to
> 0x8800_0000 causes an bus error.
>
> trying to access 0x87FFFFFC -> 0x00000000
> trying to access 0x88000000 ->Machine check in kernel mode.
> Caused by (from SRR1=49030): Transfer error ack signal
>
> It is like the prefetch area is not set up correctly for ioremap.
>
> The PCI registers are set up correctly in u-boot, and we can access the
> whole prefetch area in u-boot without any problems.
Are you using cuImage, or a regular uImage with a device-tree-aware
u-boot? If the former, try commenting out the call to fixup_pci() in
arch/powerpc/boot/cuboot-pq2.c and let me know if that changes anything.
Otherwise, are you sure the kernel didn't move BARs around such that
there's no longer a PCI device mapped at 0x88000000 (or that the device
that is there has been disabled)?
Can you show the contents of the following big endian registers:
TESCR1 (0x10040), TESCR2 (0x10044), PCIBRx (0x101ac, 0x101b0), and
PCIMSKx (0x101c4, 0x101c8)
and the following little endian registers:
POTARx (0x10800, 0x10818, 0x10830), POBARx (0x10808, 0x10820, 0x10838),
POCMRx (0x10810, 0x10828, 0x10840), POESR (0x10084), PCI_EACR (0x10890),
and PCI_ECCR (0x108a0)
after the machine check happens?
-Scott
next prev parent reply other threads:[~2008-01-17 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 21:33 Problems with PCI on 8280 Rune Torgersen
2008-01-17 22:02 ` Scott Wood [this message]
2008-01-17 23:05 ` Rune Torgersen
2008-01-17 23:18 ` Scott Wood
2008-01-18 0:27 ` Rune Torgersen
2008-01-18 17:07 ` Scott Wood
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=478FD066.5000803@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=runet@innovsys.com \
/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.