public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erez Doron <erez@savan.com>
To: linux kernel <linux-kernel@vger.kernel.org>,
	ilug <linux-il@linux.org.il>
Subject: solved: ( was Re: non volatile ram disk)
Date: 22 Jan 2002 15:53:45 +0200	[thread overview]
Message-ID: <1011707625.1835.3.camel@hal.savan.com> (raw)
In-Reply-To: <1011618928.2825.5.camel@hal.savan.com>
In-Reply-To: <1011618928.2825.5.camel@hal.savan.com>

well, i finanly managed to make a ramdisk which will not earsed by
reboot.

the solution is to give mem=32m, and use ioremap to map the rest of the
32m to virtual adresses

now it works !!!

thanks anyway
erez.



On Mon, 2002-01-21 at 15:15, Erez Doron wrote:
> hi
> 
> I'm looking for a way to make a ramdisk which is not erased on reboot
> this is for use with ipaq/linux.
> 
> i tought of booting with mem=32m and map a block device to the rest of
> the 32M ram i have.
> 
> the probelm is that giving mem=32m to the kernel will cause the kernel
> to map only the first 32m of physical memory to virtual one, so using
> __pa(ptr) on the top 32m causes a kernel oops.
> 
> any idea ?
> 
> 
> regards
> erez.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


      parent reply	other threads:[~2002-01-22 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 13:15 non volatile ram disk Erez Doron
2002-01-21 13:41 ` Peter Wächtler
2002-01-21 13:42   ` Erez Doron
2002-01-21 14:10     ` Erez Doron
2002-01-21 15:21       ` Peter Wächtler
2002-01-22  9:39         ` Erez Doron
2002-01-21 23:54     ` David Woodhouse
2002-01-22 13:53 ` Erez Doron [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=1011707625.1835.3.camel@hal.savan.com \
    --to=erez@savan.com \
    --cc=linux-il@linux.org.il \
    --cc=linux-kernel@vger.kernel.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