public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Machon <dmachon.dev@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com, Daniel Machon <dama@universal-robots.com>
Subject: Re: [PATCH] bootimg-efi-isar: add support for squashfs
Date: Fri, 1 Apr 2022 09:24:02 +0200	[thread overview]
Message-ID: <20220401072402.GA2792945@ur-li-s4qm6889.unirobotts.local> (raw)
In-Reply-To: <20220330114821.07b42600@md1za8fc.ad001.siemens.net>

On Wed, Mar 30, 2022 at 11:48:21AM +0200, Henning Schild wrote:
> Am Wed, 30 Mar 2022 09:50:01 +0200
> schrieb Daniel Machon <dmachon.dev@gmail.com>:
> 
> > This patch adds support for squashfs in grub, when using grub loader
> > for EFI images. This is needed when the linux- or initrd image is
> > located in a squashfs filesystem.
> 
> Out of curiosity, did you try systemd boot as well? And in fact did you
> confirm it is actually needed with recent isar?
> 
> With
> https://github.com/ilbers/isar/commit/9d0a7012be2217c77f85d54ba8aac0839bc847fb
> we should have all files living in the EFI partition which IMHO is
> always FAT32. But maybe you are using "custom_cfg".
>

I think you have a point here. We recently bumped the isar layer, and I might
have missed this change. I like the consistency of having the boot files in
the EFI partition across all bootloaders.

This should indeed make this patch redundant. Thanks for poitning this out!
 
> > Signed-off-by: Daniel Machon <dama@universal-robots.com>
> > ---
> >  meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py
> > b/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py index
> > d971254..78fabb8 100644 ---
> > a/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py +++
> > b/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py @@ -355,7
> > +355,7 @@ class BootimgEFIPlugin(SourcePlugin): grub_cmd += "terminal
> > minicmd test loadenv echo help " grub_cmd += "reboot serial terminfo
> > iso9660 loopback tar " grub_cmd += "memdisk ls search_fs_uuid udf
> > btrfs xfs lvm "
> > -                    grub_cmd += "reiserfs regexp " + grub_modules
> > +                    grub_cmd += "reiserfs regexp squash4 " +
> > grub_modules exec_cmd(grub_cmd)
> 
> While it is usually "not allowed" to touch this file without checking
> OE first, this is touching our forked bits and therefore fine.
> 
> It would be interesting to see if we could drop that list and say "all"
> or "all defaults", but that is another topic.

Agreed.

> 
> Henning
> 
> >              elif source_params['loader'] == 'systemd-boot':
> >                  kernel_dir = os.path.join(rootfs_dir['ROOTFS_DIR'],
> > "usr/lib/systemd/boot/efi/")
> 

  reply	other threads:[~2022-04-01  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30  7:50 Daniel Machon
2022-03-30  9:48 ` Henning Schild
2022-04-01  7:24   ` Daniel Machon [this message]
2022-04-01  7:33     ` Henning Schild

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=20220401072402.GA2792945@ur-li-s4qm6889.unirobotts.local \
    --to=dmachon.dev@gmail.com \
    --cc=dama@universal-robots.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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