From: Mark Brown <broonie@sirena.org.uk>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: Platform devices on MPC8245
Date: Wed, 7 Sep 2005 17:58:26 +0100 [thread overview]
Message-ID: <20050907165825.GB8522@projectcolo.org.uk> (raw)
In-Reply-To: <431F187E.4070006@ru.mvista.com>
On Wed, Sep 07, 2005 at 08:42:38PM +0400, Vitaly Bordug wrote:
> Yes, that's right. The proper solution (I guess) will be reconfiguration
> in mpc10x_bridge_init() so that memory covered by the bridge do not
> intercept anything what pdevs request. Or (less probably) there's
> something odd in pdevs descriptions - if so you need to find out what
> exactly is intercepted with the bridge area.
Setting the parent for the on-chip devices to be the PCI bridge ought to
do the trick, I think. The thing that's worrying me is that I can't see
how existing users of this code manage to do so successfully.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
prev parent reply other threads:[~2005-09-07 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 12:26 Platform devices on MPC8245 Mark Brown
2005-09-07 16:34 ` Mark Brown
2005-09-07 16:42 ` Vitaly Bordug
2005-09-07 16:58 ` Mark Brown [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=20050907165825.GB8522@projectcolo.org.uk \
--to=broonie@sirena.org.uk \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@ru.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).