| To: | Ralf Baechle <ralf@linux-mips.org> |
|---|---|
| Subject: | Re: Setting the physical RAM map |
| From: | Adam Nielsen <a.nielsen@shikadi.net> |
| Date: | Tue, 01 Dec 2009 08:38:39 +1000 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <20091130214118.GB27721@linux-mips.org> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <4B1135FF.9050908@shikadi.net> <20091130214118.GB27721@linux-mips.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.8.1.22) Gecko/20090809 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0 |
Are you sure it's a R4600, not R4640 or R4650? It's like a decade that I last read up on these but afair they have a fixed mapping starting at 0x40000000. It would make perfect sense to use such a CPU in an X terminal. Hmm, I'm not sure. I'd have to peel off the heatsink to be sure I guess. The very first kernel messages print this: CPU revision is: 00002020 (R4600) FPU revision is: 00002020So I guess these values would be more specific if the CPU was indeed one of those revisions. Cheers, Adam. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Setting the physical RAM map, Adam Nielsen |
|---|---|
| Previous by Thread: | Re: Setting the physical RAM map, Ralf Baechle |
| Next by Thread: | Re: [PATCH 1/1] MIPS: Wire up recvmmsg syscall, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |