public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Franck <vagabon.xyz@gmail.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to add a new ram region ?
Date: Mon, 26 Sep 2005 10:08:47 +0200	[thread overview]
Message-ID: <cda58cb805092601082ccda43b@mail.gmail.com> (raw)
In-Reply-To: <20050923155914.0e13e0e5.rdunlap@xenotime.net>

Hi Randy,

2005/9/24, Randy.Dunlap <rdunlap@xenotime.net>:
> On Fri, 23 Sep 2005 09:49:43 +0200 Franck wrote:
>
> > Hi,
> >
> > I'm working on port of linux 2.6.13. The target is a custom board
> > based on a MIPS cpu. There are several RAMs on this board whose
> > address are not contiguous and don't start to 0 . I currently succeed
> > to make linux detect one of these RAM (the biggest one) but I'd like
> > to make linux able to use the others...I'd like to use the other in a
> > particular way: I would like to be able to allocate memory only on a
> > single RAM when needed in kernel space, and in userspace I would be
> > able to export a RAM disk that uses memory on a single RAM.
> >
> > Could someone tell me how to do that or give me some pointers  ?
>
> You can try the "memmap=" kernel boot options, although I don't
> know if or how well they apply to MIPS.  Some of them apparently
> do apply, according to Documentation/kernel-parameters.txt .
>

I looked at this kernel boot option and it seems that every given RAM
regions cannot be used separetly: once they're registered, I can't
allocate a page for a given region. Is that correct ?

Thanks
--
               Franck

      reply	other threads:[~2005-09-26  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  7:49 How to add a new ram region ? Franck
2005-09-23 22:59 ` Randy.Dunlap
2005-09-26  8:08   ` Franck [this message]

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=cda58cb805092601082ccda43b@mail.gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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