From: Matthew Locke <mlocke@onemain.com>
To: Dan Malek <dan@mvista.com>, Brett Carswell <BrettC@nulec.com.au>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: RPX Lite w MontaVista 1.2
Date: Tue, 19 Dec 2000 14:18:18 -0500 (EST) [thread overview]
Message-ID: <383010226.977253498093.JavaMail.root@web621-wrb.mail.com> (raw)
no that works too. The old bootloader (RPX-Utility) always setup the BR/OR
for NVRAM even if the board did not have NVRAM populated. In the new
bootloader NVRAM is not mapped by default. if you enable NVRAM in its config
it will setup the BR/OR and then the kernel can access that area of memory.
Obviously, if you acutally try to do something with that area...
------Original Message------
From: Dan Malek <dan@mvista.com>
To: Brett Carswell <BrettC@nulec.com.au>
Sent: December 18, 2000 3:02:12 AM GMT
Subject: Re: RPX Lite w MontaVista 1.2
Brett Carswell wrote:
>
> I enabled the NVRAM in the config and everything works great now.
That's weird. Something else is wrong. The NVRAM config is irrelevant
on the RPX-lite (and I think all 8xx boards). The code I suggested you
remove is run long before the kernel, and the information you sent
earlier indicated the actual NVRAM was not mapped in the memory
controller.
-- Dan
_____________________________________
OneMain.com, Your Hometown Internet.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-12-19 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 19:18 Matthew Locke [this message]
2000-12-20 3:52 ` RPX Lite w MontaVista 1.2 Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-12-17 22:03 Brett Carswell
2000-12-18 3:02 ` Dan Malek
2000-12-14 8:10 Brett Carswell
2000-12-14 17:20 ` Dan Malek
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=383010226.977253498093.JavaMail.root@web621-wrb.mail.com \
--to=mlocke@onemain.com \
--cc=BrettC@nulec.com.au \
--cc=dan@mvista.com \
--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).