From: Steve Longerbeam <stevel@mvista.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: new special filesystem for consideration in 2.6/2.7
Date: Wed, 03 Mar 2004 10:57:37 -0800 [thread overview]
Message-ID: <40462AA1.7010807@mvista.com> (raw)
MontaVista Software has developed a new filesystem
targeted for embedded systems that we would like to
have considered for inclusion in 2.6 or 2.7. It is
called the Protected and Persistent RAM Special Filesystem
(PRAMFS). It was originally developed for three major consumer
electronics companies for use in their smart cell phones
and other consumer devices.
An intro to PRAMFS along with a technical specification
is at the SourceForge project web page at
http://pramfs.sourceforge.net/. A patch for 2.6.3 has
been released at the SF project site.
PRAMFS can be tested on a desktop by reserving some portion
of physical memory with "mem=". For example, a machine with
512M could reserve the top 32M with "mem=480M". PRAMFS would
then be mounted with:
mount -t pramfs -o physaddr=0x1e000000,init=0x2000000 none /mnt/pramfs
Thanks for your comments and consideration.
Steve
next reply other threads:[~2004-03-03 18:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 18:57 Steve Longerbeam [this message]
2004-03-05 18:09 ` new special filesystem for consideration in 2.6/2.7 Steve Longerbeam
2004-03-05 18:42 ` Dave Jones
2004-03-05 18:59 ` Steve Longerbeam
2004-03-07 3:06 ` Mike Fedyk
2004-03-18 19:28 ` Tim Bird
2004-03-05 22:09 ` Pavel Machek
2004-03-08 17:57 ` Steve Longerbeam
2004-03-08 22:35 ` Pavel Machek
2004-03-07 9:49 ` Christoph Hellwig
2004-03-07 10:10 ` Willy Tarreau
2004-03-08 18:42 ` Steve Longerbeam
2004-03-11 12:34 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-03-05 18:53 Steve Kenton
2004-03-07 3:07 ` Mike Fedyk
2004-03-08 0:07 Stephen M. Kenton
2004-03-08 18:37 ` Steve Longerbeam
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=40462AA1.7010807@mvista.com \
--to=stevel@mvista.com \
--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