From: Dan Taylor <danieltaylor@we.mediaone.net>
To: Kevin Fry <kevin@carts.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PCI support
Date: Fri, 12 Oct 2001 12:09:15 -0700 [thread overview]
Message-ID: <3BC73FDB.8E6F6672@we.mediaone.net> (raw)
In-Reply-To: 3BC7388E.CEBF1416@carts.com
The code would have to be added in one or two places. First, update
the PCI code in .../linux/arch/ppc/kernel; your hardware may be like
a sandpoint, but could be chrp. If, as I suspect, the PowerSPAN is
NOT a transparent PCI-PCI bridge, you will also need to modify the
.../linux/drivers/pci/pci.c code that handles child busses. I usually
put an "else if" inside the "for" loop after "pcibios_fixup_bus()".
That way the existing code handles any transparent bridges, then I can
specify an implementation-dependent bridge, either by bus & device, by
checking checking the vendor and device IDs, or both. You have to do
all of the same things that the transparent bridge does, so just copy,
paste, and edit the code inside that "if". You need to have the kernel
code done first, since that will have the config cycle handling and
memory/io space mapping.
Kevin Fry wrote:
>
> I'm trying to setup a PCI bridge on our 8260 board here, and was
> wondering if a driver exists for the Tundra Powerspan. We're using Hard
> Hat Linux 2.0 JE
>
> If I write my own drivers, where would the board-specific PCI routines
> go in the kernel code? I found the function prototypes in linux/pci.h,
> but couldn't find any pci code itself. Does HHL 2.0 JE support PCI?
>
> Thanks!
> Kevin Fry
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-10-12 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 18:38 PCI support Kevin Fry
2001-10-12 19:09 ` Dan Taylor [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=3BC73FDB.8E6F6672@we.mediaone.net \
--to=danieltaylor@we.mediaone.net \
--cc=danieltaylor@acm.org \
--cc=kevin@carts.com \
--cc=linuxppc-embedded@lists.linuxppc.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).