Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: joe seb <joe.seb8@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: linux porting - doubts
Date: Fri, 26 Jun 2009 08:26:46 -0700	[thread overview]
Message-ID: <4A44E8B6.8010107@caviumnetworks.com> (raw)
In-Reply-To: <4f9abdc70906260030q3cefba63tb2fd30245a7015df@mail.gmail.com>

joe seb wrote:
> Hi,
> 
> We are trying to port linux to our new platform based on MIPS32 24Kc.
> 
> In our platform we have physical RAM of 256M mapped from 0x90000000
> to 0xa0000000( KSEG0 - cached) and 0xb0000000 to 0xc0000000(KSEG1- 
> uncached).
> 
> We made the following changes for our platform,
> 
> CAC_BASE to  0x90000000 in spaces.h
> KSEG0 to 0x90000000 and KSEG1 to 0xb0000000 in addrspace.h
> CKSEG0 to 0x90000000 and CKSEG1 to 0xb0000000 in addrspace.h
> loadaddr to 0x90000000 in the Makefile under arch/mips folder.
> 
> Are these changes sufficient??
> Is there any other platform port with such variations which we can refer to
> make sure about the changes made.
> 

That seems mostly wrong.

The CAC_BASE, KSEG0, and CKSEG0 should probably be left unchanged.  You 
the load-y in arch/mips/Makefile for your target to the load address of 
the kernel.  Then when registering memory call  add_memory_region() only 
for the physical memory that you want the kernel to use.  In your case 
physical addresses from 0 to fffffff would seem to have no RAM, so you 
would do something like:

  add_memory_region(0x10000000, 0x10000000, BOOT_MEM_RAM);

David Daney

  reply	other threads:[~2009-06-26 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  7:30 linux porting - doubts joe seb
2009-06-26 15:26 ` David Daney [this message]
2009-06-27  7:35   ` joe seb

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=4A44E8B6.8010107@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=joe.seb8@gmail.com \
    --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