>>>>> "Mike" == Mike Touloumtzis <miket@bluemug.com> writes:
[snip]
Mike> Hmmm, maybe we need ramfs-backed-by-romfs :-). But a lot of
Mike> people in the embedded/consumer electronics space could get by
Mike> just fine with a read-only / and a ramfs or ramdisk on /tmp.
I am not so sure about this. Typical flash access times are rather
long compared to SDRAM. StrataFlash and other bursting flash are
rather new and require specific CPUs or custom logic to access the
flash in a sequential mode.
In my personal experience, code is usually compressed in flash (or
ROM) and expanded into SDRAM. You can always use an MMU to achieve
the RO effects of flash/ROM. The big win for flash execution is that
the power numbers are typically lower... but since it takes longer to
execute, it washes out to the same. But some paranoid hardware people
don't like `peak drains' on a battery so they might prefer Flash
execution. The flexibility is nice whatever the case; it might become
more of an issue if bursting/sequential flash devices become more
common. I don't know if there is a big push for this though. The cost
of burst flash is still greater than SDRAM afiak.
fwiw,
Bill Pringlemeir.
-
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/
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 21:00:47 EST