From: "Jacky Lam" <jackylam@astri.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Walnut PCI bridge can't be detected
Date: Tue, 14 Oct 2003 13:51:50 +0800 [thread overview]
Message-ID: <004e01c39217$4446ce60$2803050a@JackyLam> (raw)
In-Reply-To: 3F8B7B3B.60302@vinesystech.com
> I was puzzled by this for a while. Then I saw this code while debugging
> PCI on my custom board:
> In ppc405_pci.c, there is ppc4xx_exclude_device function:
>
> static int
> ppc4xx_exclude_device(unsigned char bus, unsigned char devfn)
> {
> /* We prevent us from seeing ourselves to avoid having
> * the kernel try to remap our BAR #1 and fuck up bus
> * master from external PCI devices
> */
> return (bus == 0 && devfn == 0);
> }
>
> With this function there, there is no way you are going to see the
> bridge, even your driver does the scan itself. I had to write my own
> pci_read_config_<size> function to just to be able to read the bridge
> configration.
>
> Cheers,
>
> Xiaoshan
Would you made any PCI card working on Walnut before? Do you know any
code modification is needed before? Could you please give me some direction?
Thanks.
Best regards,
Jacky
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-14 5:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 2:38 Walnut PCI bridge can't be detected Jacky Lam
2003-10-13 3:05 ` Jacky Lam
2003-10-13 3:50 ` Eugene Surovegin
2003-10-13 6:33 ` Jacky Lam
2003-10-13 7:03 ` Eugene Surovegin
2003-10-13 7:13 ` Jacky Lam
2003-10-14 4:27 ` Xiaoshan Zuo
2003-10-14 5:41 ` Eugene Surovegin
2003-10-14 7:27 ` Xiaoshan Zuo
2003-10-14 5:51 ` Jacky Lam [this message]
2003-10-15 17:36 ` Xiaoshan Zuo
2003-10-16 1:07 ` Jacky Lam
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='004e01c39217$4446ce60$2803050a@JackyLam' \
--to=jackylam@astri.org \
--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).