linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Chris Love <love@ccpu.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux PCI support on Ocotea
Date: Wed, 8 Dec 2004 18:49:58 -0700	[thread overview]
Message-ID: <20041208184958.A22430@home.com> (raw)
In-Reply-To: <41B7A61E.9000602@ccpu.com>; from love@ccpu.com on Wed, Dec 08, 2004 at 05:10:54PM -0800

On Wed, Dec 08, 2004 at 05:10:54PM -0800, Chris Love wrote:
> Hi folks,
> 
> We have an Ocotea reference board (PPC 440GX) w/256M and have
> tried running both stable 2.4.26 and 2.6.10-rc3 kernels from
> penguinppc.org.  For now the bootloader is still PIBS, though
> we'll get U-Boot installed shortly.
> 
> As a first experiment we've tried installing a legacy card
> with an Intel 82559 device on it.  The warning seen from
> pci_setup_device() suggests that PCI config space wasn't
> read cleanly: a header type of 0x7f is encountered.  Nothing
> shows up under /proc/bus/pci. The card we'd actually like to
> install has a transparent bridge (Intel 21152) and other devices
> behind the bridge.  Both cards are PCI-33 versus PCI-X.

Sounds like something is wrong with your hardware configuration.

> To ask some really stupid questions first: what is the state of
> PCI support with linux on this board?  Have others tried to do
> something like this with 33/66 Mhz PCI devices or am I in
> uncharted waters?

No, this works fine for many other people, so don't get too worried.
Do verify that you have jumpered for 33Mhz operation since you
are using a 33Mhz device. PIBS should warn you about this and
advise to make the change, but maybe you have a different
version than I've seen. What rev. ocotea board and version of
PIBS do you have?

> Of the PCI #defines in platforms/ocotea.h I can correlate most
> with data from the user's manual, but not the following:
> 
> #define OCOTEA_PCI_LOWER_IO     0x00000000
> #define OCOTEA_PCI_UPPER_IO     0x0000ffff
> #define OCOTEA_PCI_LOWER_MEM    0x80000000
> #define OCOTEA_PCI_UPPER_MEM    0xffffefff
> 
> Is there some documentation I'm missing on these values?

The code is self-documenting as they say. :) These are the address
ranges used by the pci_auto code to assign base addresses to each
BAR that is encountered.

-Matt

  reply	other threads:[~2004-12-09  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09  1:10 Linux PCI support on Ocotea Chris Love
2004-12-09  1:49 ` Matt Porter [this message]
2004-12-09  2:20   ` Chris Love

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=20041208184958.A22430@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=love@ccpu.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 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).