All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Love <love@ccpu.com>
To: linuxppc-embedded@ozlabs.org
Subject: Linux PCI support on Ocotea
Date: Wed, 08 Dec 2004 17:10:54 -0800	[thread overview]
Message-ID: <41B7A61E.9000602@ccpu.com> (raw)

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.

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?

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?

Thanks in advance for any suggestions,

	Chris
-- 
Chris Love      // Continuous Computing Corporation
love@ccpu.com  // http://www.ccpu.com

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09  1:10 Chris Love [this message]
2004-12-09  1:49 ` Linux PCI support on Ocotea Matt Porter
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=41B7A61E.9000602@ccpu.com \
    --to=love@ccpu.com \
    --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.