public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Miles Bader <miles@gnu.org>
Cc: andersen@codepoet.org, Dave Cinege <dcinege@psychosis.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list.
Date: Wed, 30 Oct 2002 04:26:31 -0500	[thread overview]
Message-ID: <3DBFA5C7.1080603@pobox.com> (raw)
In-Reply-To: buobs5cgu7o.fsf@mcspd15.ucom.lsi.nec.co.jp

Miles Bader wrote:

>Jeff Garzik <jgarzik@pobox.com> writes:
>  
>
>>>[Well, OK, actually it'd be nice to have something like initramfs + some
>>>other sort of fetch-the-bits-directly-from-ROM FS which I could
>>>mix-n-match; anyway initramfs has got to be better than initrd...]
>>>      
>>>
>>It should be pretty easy to populate initramfs from ROM...
>>    
>>
>
>Actually what I was trying to say was that often I don't want to copy
>from ROM to RAM, I just want to have file reads get the bits directly
>from ROM (to avoid using, um, RAM).
>  
>

Yep, that was my assumption.

If your ROM is directly addressable, i.e. not read over a single-bit bus 
or anything, it should be doable.  I'm not saying that initramfs will do 
this out of the box :) but going from initramfs to "initromfs" should 
not be a huge leap...

However, that said, things also depend on what proggies you are running 
in your initramfs.  You may be running code that only runs at startup 
when the kernel boots, in which case the best space utilization would be 
to uncompress a compressed image out of ROM to RAM, use it to bootstrap, 
and then free [unlink] all the initramfs files that are no longer needed.

    Jeff





  reply	other threads:[~2002-10-30  9:20 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28  2:17 Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Rob Landley
2002-10-28  8:25 ` Vamsi Krishna S .
2002-10-28  9:55   ` Skip Ford
2002-10-28 10:35     ` Vamsi Krishna S .
2002-10-28 10:29 ` Andrew Walrond
2002-10-28 10:40   ` Rob Landley
2002-10-28 12:15   ` Nicholas Wourms
2002-10-28 13:31   ` Dave Jones
2002-10-28 14:05     ` Andrew Walrond
2002-10-28 14:42       ` Andrew Walrond
2002-10-28 15:02       ` Alan Cox
2002-10-30  7:29 ` Dave Cinege
2002-10-30  7:40   ` Jeff Garzik
2002-10-30  8:22     ` Dave Cinege
2002-10-30  8:37       ` Russell King
2002-10-30  9:32         ` Dave Cinege
2002-10-30  8:41       ` Jeff Garzik
2002-10-30  8:51       ` Erik Andersen
2002-10-30  9:00         ` Miles Bader
2002-10-30  9:06           ` Jeff Garzik
2002-10-30  9:19             ` Miles Bader
2002-10-30  9:26               ` Jeff Garzik [this message]
2002-10-30  9:38                 ` Miles Bader
2002-10-30  9:42                   ` Erik Andersen
2002-10-30 10:50                   ` Jeff Garzik
2002-10-30  9:34             ` Russell King
2002-10-30 10:07               ` Dave Cinege
2002-10-30  9:36             ` Erik Andersen
2002-10-30 10:52               ` Jeff Garzik
2002-10-30  9:55           ` Dave Cinege
2002-10-30  9:59             ` Miles Bader
2002-10-30 10:24               ` Dave Cinege
2002-10-30 10:05             ` Jeff Garzik
2002-10-30 10:14               ` Dave Cinege
2002-10-30 10:24                 ` Jeff Garzik
2002-10-30 10:42                   ` Dave Cinege
2002-10-30 11:06                     ` Jeff Garzik
2002-10-30  9:55         ` Dave Cinege
2002-10-30 10:29           ` Jeff Garzik
2002-11-04  2:13           ` Rob Landley
2002-11-04  7:39             ` Help needed with IRQ on Ali chipset Jacek Pliszka
2002-11-04 13:10             ` Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Alan Cox
2002-11-04 22:52             ` Werner Almesberger
2002-11-04 23:02               ` Jeff Garzik
2002-11-04 18:16                 ` Rob Landley
2002-11-04 23:22                 ` Werner Almesberger
2002-10-30 14:32       ` Alan Cox

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=3DBFA5C7.1080603@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=andersen@codepoet.org \
    --cc=dcinege@psychosis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.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