From: torsten.rissel@t-online.de (Torsten Rissel)
To: "'Gabriel Paubert'" <paubert@iram.es>, Matt Porter <mporter@mvista.com>
Cc: Torsten Rissel <torsten.rissel@t-online.de>,
"Linuxppc-Embedded (E-Mail)"
<linuxppc-embedded@lists.linuxppc.org>
Subject: AW: MVME 5100
Date: Mon, 18 Dec 2000 19:44:49 +0100 [thread overview]
Message-ID: <01C0692A.FCFDAC80@NB1> (raw)
???
So would it be better to use the CHRP settings to build a kernel for the MVME5100 ?
Torsten
-----Ursprungliche Nachricht-----
Von: Gabriel Paubert [SMTP:paubert@iram.es]
Gesendet am: Montag, 18. Dezember 2000 19:08
An: Matt Porter
Cc: Torsten Rissel; Linuxppc-Embedded (E-Mail)
Betreff: Re: MVME 5100
On Mon, 18 Dec 2000, Matt Porter wrote:
> > On the MVME2400 (and older Raven/Falcon based boards) the config space by
> > default is at 0x80000cf8 and 0x8000cfc. Does it mean that on the MVME5100,
> > the Hawk is reprogrammed by PPCBUG to look like a CHRP system ?
>
> Yes...and Yes. :) The only thing the newer MCG boards really do
> (correctly) that looks like a PReP system is the disk booting
> mechanism.
>
> BTW, the MVME2100 (8240/Universe II board) is put in map B for a CHRP
> map as well.
Ok, fine. It means that my code to reprogram the Raven/Hawk on 2[467]xx
just makes things more uniform. I still don't like the fact that the DMA
is offset, though (unless it's a residual data bug, and map B on 106/107
does not have this DMA offset).
Regards,
Gabriel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-12-18 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-18 18:44 Torsten Rissel [this message]
2000-12-18 19:07 ` AW: MVME 5100 Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2000-12-18 16:50 Torsten Rissel
2000-12-18 18:24 ` Gabriel Paubert
2000-12-18 12:19 Torsten Rissel
2000-12-14 15:25 Torsten Rissel
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=01C0692A.FCFDAC80@NB1 \
--to=torsten.rissel@t-online.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mporter@mvista.com \
--cc=paubert@iram.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.