From: Jon Loeliger <jdl@freescale.com>
To: Johan Borkhuis <j.borkhuis@dutchspace.nl>
Cc: Linuxppc-dev@ozlabs.org, Linuxppc-embedded@ozlabs.org
Subject: Re: Moving from 2.6.14 (ppc) to 2.6.20 (powerpc): problems with PCI-PCI bridge
Date: Mon, 04 Feb 2008 11:34:36 -0600 [thread overview]
Message-ID: <47A74CAC.2010006@freescale.com> (raw)
In-Reply-To: <47A6D72D.4050100@dutchspace.nl>
Johan Borkhuis wrote:
> Hello,
>
> I was using kernel version 2.6.14 (ppc) on a MVME3100 board (MPC8540
> processor). We are planning to move to 2.6.20 (powerpc), but I have some
> problems with the initialization of a PCI-PCI bridge.
> Connected to the MVME3100 board is a PCI-PCI bridge (HiNT, PCI6150,
> 3388:0022). When using the 2.6.14 kernel this bridge is initialized
> correctly: it is setup as bus-master, memory and IO are configured, and
> the memory allocation on the PCI-bus is correct.
> When I use 2.6.20 (powerpc) the device is not configured correctly:
> bus-master, memory and IO are not set, and the memory space of the
> bridge on the PCI bus is set to the minimum value (0xfffff).
> I can correct these settings by modifying the PCI_COMMAND register to
> set the bus-master, memory and IO. I change the size of the memory space
> in pci_32.c, by forcing the size to the required setting in
> pci_relocate_bridge_resource. But to be honest, I don't like this very
> much: modifying registers like this should not be needed, so I guess
> there is something wrong in my configuration or setup.
>
> How can I fix this problem in a better way? What could be wrong with my
> configuration?
There has been a fair amount of PCI setup reworking done
somewhat recently. (.22 and .23, IIRC, and even .24).
It might be best if you can try 2.6.24.
jdl
prev parent reply other threads:[~2008-02-04 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 9:13 Moving from 2.6.14 (ppc) to 2.6.20 (powerpc): problems with PCI-PCI bridge Johan Borkhuis
2008-02-04 17:34 ` Jon Loeliger [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=47A74CAC.2010006@freescale.com \
--to=jdl@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=j.borkhuis@dutchspace.nl \
/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).