| To: | Andi <opencode@gmx.net> |
|---|---|
| Subject: | Re: memory dump on mips |
| From: | Thiemo Seufer <ths@networkno.de> |
| Date: | Tue, 8 Jan 2008 14:54:49 +0000 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <4783754D.8010007@gmx.net> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <4783754D.8010007@gmx.net> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
Andi wrote: > Hi list, > > we are working on an embedded Linux device with a Sigma SMP8634 (MIPS > 4KEc 300MHz CPU) mounted on it. Unfortunately we don't have access to > the kernel running on the system. > > We figured out, that the bootloader loads the kernel image to 0x90020000 > (physical address). 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. So the physical address you are looking for would be 0x10020000. Thiemo |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | memory dump on mips, Andi |
|---|---|
| Next by Date: | kseg1 uncache access issue, lovecentry |
| Previous by Thread: | memory dump on mips, Andi |
| Next by Thread: | Re: memory dump on mips, Andi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |