public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Stumpf <michaelstumpf@yahoo.com>
To: David Woodhouse <dwmw2@infradead.org>, shane@agendacomputing.com
Cc: Nicolas Pitre <nico@cam.org>, mstumpf@pobox.com, mtd@infradead.org
Subject: Re: MTD, generic physmap memory, MTD_BLOCK
Date: Tue, 19 Dec 2000 05:32:39 -0800 (PST)	[thread overview]
Message-ID: <20001219133239.24180.qmail@web2103.mail.yahoo.com> (raw)


> >  But we are working on XIP for cramfs.  But this requires either
> > expanding the  inode, or stealing a bit or two away from GIDS, or
> > UIDs.  This is only a  "linear addressing" patch. 
> 
> I was looking at doing it in romfs. You can't have compression anyway, for 
> obvious reasons, and it looked a little easier. But I suppose that wouldn't 
> allow you to mix XIP-able and compressed files in the same fs.

I did some work in the direction suggested by (thanks!) Nicolas--modified
mtdram.c to act as a conduit device for plain memory.  I did get a successful
boot from a cramfs rootdisk.  

When I said XIP, I didn't realize that this crowd had a very "serious"
definition of it.  I simply meant I was trying to get around the initrd
buffering issue:  As far as I can tell, up until now the only mechanism that a
CPU (with only RAM and ROM visibility) has at its disposal to boot from is
initrd, that would copy all the ROM image into RAM buffer cache.. and only
understand three file systems (cramfs is not one of them).  I don't mind cramfs
using a buffer page (4k, LinuxPPC) or two to do its work--I was trying to slay
the complete-image-copy daemon.  (My embedded system is 6 meg RAM, 8 meg ROM..
and I want shared libraries, etc)

It seems to me that for the time being and the immediate future, XIP as we're
talking about it would be overkill.  The streamlining and elegance gained in
the operation of XIP is probably offset by the ugliness of implementation and
the potential loss of compression that seems so crucial in embedded devices,
the primary target (right?) of MTD.  I like XIP but I don't think I'd ever use
it.

One very relevant topic that I'd like to discuss is where a generic memory
conduit device belongs.  I would suspect it belongs as a fallback default if
CFI devices can't be probed (I forget the file), but it also might make sense
to give it a separate file for "neatness" sake.  

Cheers,
Michael




=====
=====================================================================
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

             reply	other threads:[~2000-12-19 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-19 13:32 Michael Stumpf [this message]
2000-12-19  2:51 ` MTD, generic physmap memory, MTD_BLOCK Shane Nay
  -- strict thread matches above, loose matches on Subject: below --
2000-12-13 16:48 Michael Stumpf
2000-12-13 19:02 ` 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

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=20001219133239.24180.qmail@web2103.mail.yahoo.com \
    --to=michaelstumpf@yahoo.com \
    --cc=dwmw2@infradead.org \
    --cc=mstumpf@pobox.com \
    --cc=mtd@infradead.org \
    --cc=nico@cam.org \
    --cc=shane@agendacomputing.com \
    /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