From: Matt Porter <mporter@mvista.com>
To: Torsten Rissel <torsten.rissel@t-online.de>
Cc: "Linuxppc-Embedded (E-Mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MVME 5100
Date: Fri, 15 Dec 2000 15:38:05 -0700 [thread overview]
Message-ID: <20001215153805.E691@beef.az.mvista.com> (raw)
In-Reply-To: <01C065EA.89787760@NB2>; from torsten.rissel@t-online.de on Thu, Dec 14, 2000 at 04:25:55PM +0100
On Thu, Dec 14, 2000 at 04:25:55PM +0100, Torsten Rissel wrote:
> Thanks, but I have already set up a BAT to cover the area from 0xf0000000 - 0xffffffff
> because everything is there on the MVME5100 - the serial ports (via the Hawk external
> registers) [fef88000+], the MPIC [f3f80000+] and the PHC PCI registers [fe000000+].
Right, I have one as well as a similar Hawk-based board that has Linux
on it.
> The CONFIG_ADDRESS and CONFIG_DATA registers are on fe000cf8 and fe00cfc,
> and still writing to the CONFIG_ADDRESS and then reading the CONFIG_DATA sometime
> works and sometimes not !!!??
I can consistently read from and write to config space on my 5100 board
via PPCBUG. The only thing I can think of is that you have somehow
locked up the Hawk bridge. I've managaged this on other host bridges
only by getting a PIB locked up and squatting on the bus.
What kernel version are you using as a basis for your port? Are you
basing the port off the existing prep_*.c support?
--
Matt Porter
MontaVista Software, Inc.
mporter@mvista.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-15 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 15:25 AW: MVME 5100 Torsten Rissel
2000-12-15 22:38 ` Matt Porter [this message]
2000-12-18 15:34 ` Gabriel Paubert
2000-12-18 17:58 ` Matt Porter
2000-12-18 18:07 ` Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2000-12-13 21:39 Torsten Rissel
2000-12-13 20:41 ` Matt Porter
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=20001215153805.E691@beef.az.mvista.com \
--to=mporter@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=torsten.rissel@t-online.de \
/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).