All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Moles <cubicool@gmail.com>
To: yocto@yoctoproject.org
Subject: Minimalist Initrd
Date: Sat, 05 Jul 2014 23:57:54 -0400	[thread overview]
Message-ID: <53B8C942.6010405@gmail.com> (raw)

Hey guys! I've been using Yocto for a while now and it's quite 
phenomenal; I really appreciate the hard work and effort the community 
puts into this project, and I hope I can (with the approcal of my 
clients) return some of my own Yocto/OE (and specifically, Angstrom) 
work back for everyone to use!

I've encountered a scenario wherein I have only (and this constraint 
can't be worked around) 13MB of space into which I can place a JFFS2 
image which can be used to continue the system startup (which is 
initially started by an older version of uboot).

I'm having trouble finding a clean solution within the Yocto/OE world 
for this issue. Thus far, I've been using an old, generic, super-tiny 
ARM-based initrd I made years ago which just does a few (proprietary) 
things in the linux and then fires off /sbin/init in the "real" filesystem.

What I need now, however, is a recipe (or perhaps hints on where to 
start when rolling my own recipe) for generating little more than an 
image (JFFS2 or cpio.gz) with busybox in it. I can handle the rest view 
function overrides, I just need the base startup.

Can anyone give me any hints on this? I'm using Poky mostly, which some 
forrays into Angstrom 2016. Any hints on existing bitbake recipes I can 
inherit/adapt would be amazingly useful. Thanks!


             reply	other threads:[~2014-07-06  3:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-06  3:57 Jeremy Moles [this message]
2014-07-08 21:03 ` Minimalist Initrd Burton, Ross

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=53B8C942.6010405@gmail.com \
    --to=cubicool@gmail.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.