linux-mips
[Top] [All Lists]

Re: how to emdedded ramdisk.gz in vmlinux for linux-2.6.14?

To: Marc Karasek <marckarasek@ivivity.com>
Subject: Re: how to emdedded ramdisk.gz in vmlinux for linux-2.6.14?
From: "P. Christeas" <p_christ@hol.gr>
Date: Fri, 20 Jan 2006 23:02:28 +0200
In-reply-to: <1137790053.22994.58.camel@localhost.localdomain>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <0F31272A2BCBBE4FA01344C6E69DBF501EAB1B@thoth.ivivity.com> <200601202203.14325.p_christ@hol.gr> <1137790053.22994.58.camel@localhost.localdomain>
Resent-date: Fri, 20 Jan 2006 23:03:43 +0200
Resent-from: P. Christeas <p_christ@hol.gr>
Resent-message-id: <200601202303.43365.p_christ@hol.gr>
Resent-to: linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
User-agent: KMail/1.9
On Friday 20 January 2006 10:47 pm, you wrote:
> Basically due to design issues and cost issues having a flash based
> system is not possible.  Currently we have only 16MB total of flash and
> the biggest contiguous block avail in this is only 12MB.  Our current
> ramdisk (uncompressed) is running at 30MB.  Basically, memory is cheaper
> than flash.  When you have designs that are very cost sensitive (to put
> it lightly), for example adding a 50 cent part is a major event.  You
> cannot just say we need more flash...  If we are to continue to support
> the embedded market for Linux,  every decision we make as too what
> feature gets put in, which ones get dropped have to be made with
> everyone in mind.  What is good for the desktop market, may not be the
> best solution for the embedded market.  BTW: When I mean embedded I do
> not mean Ipaq or Palm.  These are small computers with a completely
> different set of requirements than a 1U pizza box headless storage
> controller/switch/etc.
>

Our discussion is quite general, I don't mean to interfere with your hardware 
design anyway. My point was just that the filesystem you mention would be 
stored in some kind of ROM anyway (either inside the kernel ELF or outside 
it). So, you wouldn't need to copy it to your RAM. That's the main feature of 
squashfs/cromfs. You can still have tmpfs for some kind of read/write 
storage.
One drawback, however, would be that the access to the ROM (in the form of 
mtd) could cost you some extra code that need to go into the kernel.

<Prev in Thread] Current Thread [Next in Thread>