linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jacky Lam" <jackylam@astri.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Walnut PCI bridge can't be detected
Date: Mon, 13 Oct 2003 15:13:06 +0800	[thread overview]
Message-ID: <004101c39159$73381d00$2803050a@JackyLam> (raw)
In-Reply-To: 5.1.0.14.2.20031012235137.02e9d9a8@mail.ebshome.net


>
> Well, simple answer is "yes". But usually such misconfiguration will
> completely disable kernel access to PCI peripherals or lockup the box
> (which is not your case). This is why I think it's unlikely.
>
> 4xx bridges are quite simple to configure and default setup should be OK,
> especially on reference platform like Walnut.
>
> Broken (on PPC) driver is more probable cause for your problems.
>

    I agree to your point. So, I want to make sure if it is the kernel's PCI
code having problem running on Walnut recently. Is there any maintainer for
walnut platform? Or someone is using PPC kernel on walnut can successfully
using the PCI without any modification?

Regards,
Jacky


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-13  7:13 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 [this message]
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
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='004101c39159$73381d00$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).