From: Sven Luther <sven.luther@wanadoo.fr>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Board based on MPC7447 and MV64462
Date: Thu, 27 Oct 2005 22:38:43 +0200 [thread overview]
Message-ID: <20051027203843.GB13787@localhost.localdomain> (raw)
In-Reply-To: <20051027201105.GD13847@mag.az.mvista.com>
On Thu, Oct 27, 2005 at 01:11:05PM -0700, Mark A. Greer wrote:
> Actually, I guess this is more to hide the bridge from the pci_auto when
> it walks the pci buses. If the pci resources are already allocated
> correctly (as in pegasos?) it may not confuse the generic pci code.
> Even if it doesn't get confused, its by luck. The bridge's pci regs
> are NOT pci compliant and, IMHO, its iffy to assume that things woun't
> get messed up.
As said, the pci access rtas functions will stop any access to the non-pci
compliant regs.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-10-27 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 13:17 Board based on MPC7447 and MV64462 Ashish Bijlani
2005-10-27 18:17 ` Mark A. Greer
2005-10-27 18:49 ` Sven Luther
2005-10-27 20:04 ` Mark A. Greer
2005-10-27 20:11 ` Mark A. Greer
2005-10-27 20:38 ` Sven Luther [this message]
2005-10-27 20:30 ` Sven Luther
2005-10-27 20:47 ` Mark A. Greer
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=20051027203843.GB13787@localhost.localdomain \
--to=sven.luther@wanadoo.fr \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgreer@mvista.com \
/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).