From: Wolfgang Denk <wd@denx.de>
To: David Hawkins <dwh@ovro.caltech.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux on PPC
Date: Fri, 03 Mar 2006 17:04:34 +0100 [thread overview]
Message-ID: <20060303160434.3886335261F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 02 Mar 2006 21:10:43 PST." <4407CFD3.4060206@ovro.caltech.edu>
In message <4407CFD3.4060206@ovro.caltech.edu> you wrote:
>
> If the vendor provided the VxWorks BSP, then hopefully they
> also provided you with the physical memory map of the board.
> This is what you really need to get another bootloader (eg. U-Boot)
This is *NOT* corect, and actually dangerous.
> Step 1. Get the memory map of the board.
Never use any given memory map unreflected. At least *check* if it's
usable with Linux.
Many memory maps (especially those provides with some eval boards for
demonstration purpose) will NOT work with Linux. Remember that the
memory map is usually not cast in silicon, but implemented in
software, so you can change it as needed.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
C++ was an interesting and valuable experiment, but we've learned its
lessons and it's time to move on.
- Peter Curran in <DCqM4z.BxB@isgtec.com>
next prev parent reply other threads:[~2006-03-03 16:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 2:01 Linux on PPC rtos
2006-03-03 2:23 ` Frank
2006-03-03 5:09 ` nreddy
2006-03-03 16:00 ` Wolfgang Denk
2006-03-03 5:10 ` David Hawkins
2006-03-03 9:33 ` Adrian Cox
2006-03-03 16:04 ` Wolfgang Denk [this message]
2006-03-03 16:53 ` David Hawkins
2006-03-04 2:05 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2006-03-03 19:39 Rune Torgersen
2006-03-03 20:06 ` David Hawkins
2006-03-04 2:09 ` Wolfgang Denk
2006-03-04 2:51 ` David Hawkins
2006-03-03 20:28 Steve Strublic
2006-03-03 20:31 Rune Torgersen
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=20060303160434.3886335261F@atlas.denx.de \
--to=wd@denx.de \
--cc=dwh@ovro.caltech.edu \
--cc=linuxppc-embedded@ozlabs.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).