linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chris Love <love@ccpu.com>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux PCI support on Ocotea
Date: Wed, 08 Dec 2004 18:20:29 -0800	[thread overview]
Message-ID: <41B7B66D.2000409@ccpu.com> (raw)
In-Reply-To: <20041208184958.A22430@home.com>



Matt Porter wrote:
> 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?

Hi Matt,

PIBS version text is "Version 1.80 JUNE/17/2004".
Ocotea rev appears to be rev 5.

Changing the settings for the U80 switches did the trick, at
least as far as silencing the PIBS warning and enumerating the bus
by Linux.

Thanks for the suggestion; this was lurking on the board schematics.

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

      reply	other threads:[~2004-12-09  2:21 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
2004-12-09  2:20   ` Chris Love [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=41B7B66D.2000409@ccpu.com \
    --to=love@ccpu.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mporter@kernel.crashing.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 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).