LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell McGuire" <rmcguire@videopresence.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: 8360E - PCI - BRIDGE
Date: Fri, 2 Mar 2007 14:59:58 -0800	[thread overview]
Message-ID: <000c01c75d1e$80abe720$6405a8c0@absolut> (raw)
In-Reply-To: <mailman.1048.1172865151.21008.linuxppc-embedded@ozlabs.org>

I was wondering if anyone had a small suggestion of PCI cards to begin
testing Linux with for debugging a PCI bus / software / setup.

Basically I am looking for a couple of cards that are known to have good
working PPC drivers for PCI, hopefully built-in into the kernel. Preferable
that somebody has first has experience with.

I seem to be having issues with Linux only, and getting my PCI stuff to
work. Still not sure if these are DTV blob issues, or incompatibility with
the PCI-PCI bridge chip I have in the PPC system.

Questions:

1) Can somebody provide the names of just a few cards that have been tested
with these 82xx 83xx PCI busses that have worked in Linux 2.6.xx? I hope to
not be fighting endian issues in the drivers at first.

2) What is available / known about PCI bridge compatibility / enumeration
when it comes to PPC architecture? I know Linux sees the bridge, but are
there mapping compatibility issues introduced if an extra bridge is in
place?

3) Directly related to Question 2, is there any special options have to be
enabled in the Linux 2.6.xx kernel <2.6.20 specifically> to make this
happen? PreP compliance, G5 support, no idea I am just throwing ideas.


Any help appreciated, I was hoping originally that once the PCI was happy
inside U-boot that Linux wouldn't be such a far target.

       reply	other threads:[~2007-03-02 22:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1048.1172865151.21008.linuxppc-embedded@ozlabs.org>
2007-03-02 22:59 ` Russell McGuire [this message]
2007-03-02 23:23   ` 8360E - PCI - BRIDGE Kumar Gala

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='000c01c75d1e$80abe720$6405a8c0@absolut' \
    --to=rmcguire@videopresence.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox