From: Andi <opencode@gmx.net>
To: linux-mips@linux-mips.org
Subject: Re: memory dump on mips
Date: Wed, 09 Jan 2008 15:49:07 +0100 [thread overview]
Message-ID: <4784DEE3.90709@gmx.net> (raw)
Hello,
Thiemo Seufer wrote:
> > This sounds like you are confusing physical and virtual addresses.
> > Typically the kernel is loaded to the direct-mapped KSEG0 segment,
> > which starts at physical 0x00000000 / virtual 0x80000000.
Thank you for pointing on that. I was not sure if this was virtual or
physical since i grabbed this address from a serial-debug output. But if
one thinks about that the device has around 128mb it should be clear
that this can't be a physical address if ram starts at 0x00000000.
We'll check this ..
Regards,
Andi
next reply other threads:[~2008-01-09 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 14:49 Andi [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-08 13:06 memory dump on mips Andi
2008-01-08 14:54 ` Thiemo Seufer
2008-01-11 12:30 ` Andi
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=4784DEE3.90709@gmx.net \
--to=opencode@gmx.net \
--cc=linux-mips@linux-mips.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