From: "Mark A. Greer" <mgreer@mvista•com>
To: Zhaobin Zhu <zzhu@emc•com>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: pci_read_config_byte in Hardhat CDK1.2 for powerpc
Date: Thu, 19 Oct 2000 12:55:14 -0700 [thread overview]
Message-ID: <39EF51A2.F9A1DF80@mvista.com> (raw)
In-Reply-To: 39EF3BF3.19194E4A@emc.com
Zhaobin Zhu wrote:
> "Mark A. Greer" wrote:
>
> > The definitions of pci_xxx_config_yyy and pcibios_xxx_config_yyy are hard to
> > find.
> >
> > pci_xxx_config_yyy are defined by the PCI_OP() macro in drivers/pci/pci.c
> > pcibios_xxx_config_yyy are defined by the PCI_OP() macro in
> > drivers/pci/compat.c
> >
>
> Thanks, Mark.
>
> Here is what I found:
>
> pci_read_config_byte = generic_pcibios_read_byte =
> ppc_md.pcibios_read_config_byte = indirect_pcibios_read_config_byte
> in arch/ppc/kernel/indirect_pci.c
Yes, that is true because of the "set_config_access_method(indirect)" call in the
*_setup.c or *_pci.c routine for your platform (if you're looking at the
sandpoint, its in sandpoint_setup.c). Other access methods are supported too.
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-19 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 21:02 MBX kernel compile error Yiran Duan
2000-10-17 23:46 ` Jamie Guinan
2000-10-18 17:09 ` LIST_HEAD Zhaobin Zhu
2000-10-18 17:52 ` LIST_HEAD Tod E. Kurt
2000-10-18 17:56 ` LIST_HEAD Tod E. Kurt
2000-10-18 21:11 ` pci_read_config_byte in Hardhat CDK1.2 for powerpc Zhaobin Zhu
2000-10-18 22:54 ` Cal Erickson
2000-10-18 22:56 ` Grant Erickson
2000-10-19 0:19 ` Graham Stoney
[not found] ` <39EE147B.B79A2837@blastoff.com>
2000-10-19 17:15 ` Zhaobin Zhu
2000-10-19 17:41 ` Mark A. Greer
2000-10-19 18:22 ` Zhaobin Zhu
2000-10-19 19:55 ` Mark A. Greer [this message]
2000-10-19 17:48 ` Tod E. Kurt
2000-10-18 0:08 ` MBX kernel compile error Wolfgang Denk
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=39EF51A2.F9A1DF80@mvista.com \
--to=mgreer@mvista$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=zzhu@emc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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