All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gmane Admin" <gley-yocto@m.gmane-mx.org>
To: yocto@lists.yoctoproject.org
Subject: Re: How to include initrd.cpio to image
Date: Sun, 3 May 2020 13:42:19 +0200	[thread overview]
Message-ID: <aa82f1d0-b792-873f-94ba-a2719e813904@gmail.com> (raw)
In-Reply-To: <160AB66D41D34D89.15432@lists.yoctoproject.org>

Op 30-04-2020 om 23:33 schreef Gmane Admin:
> I am generating core-image-minimal-initramfs-edison.cpio.gz which is 
> found in the deploy-core-image-minimal-initramfs-image-complete/ directory.
> 
> When I build my image edison-image initrd gets included and deployed in 
> edison-image-edison.hddimg. But I am not using that.
> 
> I also generate edison-image-edison.ext4 which has bzImage kernel in 
> /boot. But by Zeus, I have no idea how to get edison-image to install a 
> file from the other recipe's deploy.
> 
> To me it doesn't make sense to include bzImage without initrd, kernel 
> will not be able to load the rootfs without.
> 
> I know I can bundle the initramfs, and that has worked fine before. 
> Until kernel + initrd grew above 15MB, now U-Boot won't load it. I have 
> now kernel = 10MB + initrd = 10MB which boot fine when I copy initrd to 
> /boot manually.

Gmane is crazy. It's me, Ferry.

I'm still stick here. Any ideas?


       reply	other threads:[~2020-05-03 11:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <160AB66D41D34D89.15432@lists.yoctoproject.org>
2020-05-03 11:42 ` Gmane Admin [this message]
     [not found] ` <160B81ECB7BC9386.1783@lists.yoctoproject.org>
2020-05-24 12:38   ` How to include initrd.cpio to image Gmane Admin
2020-04-30 21:33 Gmane Admin

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=aa82f1d0-b792-873f-94ba-a2719e813904@gmail.com \
    --to=gley-yocto@m.gmane-mx.org \
    --cc=yocto@lists.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.