From: Michael Stumpf <michaelstumpf@yahoo.com>
To: mtd@infradead.org
Subject: MTD, generic physmap memory, MTD_BLOCK
Date: Wed, 13 Dec 2000 08:48:07 -0800 (PST) [thread overview]
Message-ID: <20001213164807.18924.qmail@web2104.mail.yahoo.com> (raw)
I'm working in embedded LinuxPPC on a system with low RAM and ROM -- 6 meg RAM,
8 meg flash ROM. It seems like that MTD may provide (or almost so) a method
for mapping memory space in as a block device. It already appears to sort-of
do that, but I was wondering if full support for booting off of non-CFI
compliant, but transparently mapped in, memories is either in place now
(doesn't seem to be there) or is planned for the future.
It's a trivial driver, and I'll write it / modify existing MTD code if
desired/needed, but it really seems important to have so that I can
execute-in-place from a cramfs partition in ROM (and also have this as my root
partition).
Thoughts? Am I way off the mark here?
Regards-
Michael Stumpf
=====
=====================================================================
Michael J. Stumpf
LinuxPPC enablement
IBM-Austin, TX 512.838.1524 [lab] 512.838.5335 [work]
http://www.pobox.com/~mstumpf
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-12-13 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 16:48 Michael Stumpf [this message]
2000-12-13 19:02 ` MTD, generic physmap memory, MTD_BLOCK Nicolas Pitre
2000-12-16 1:04 ` Shane Nay
2000-12-17 22:24 ` David Woodhouse
2000-12-18 21:31 ` Shane Nay
2000-12-19 9:24 ` David Woodhouse
2000-12-18 22:35 ` Shane Nay
-- strict thread matches above, loose matches on Subject: below --
2000-12-19 13:32 Michael Stumpf
2000-12-19 2:51 ` Shane Nay
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=20001213164807.18924.qmail@web2104.mail.yahoo.com \
--to=michaelstumpf@yahoo.com \
--cc=mstumpf@pobox.com \
--cc=mtd@infradead.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