From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Support for generating bootx64.efi when distro arch is i386
Date: Wed, 10 Feb 2021 11:42:44 +0100 [thread overview]
Message-ID: <20210210114244.439de40a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20210210085616.GU20742@yssyq.m.ilbers.de>
Am Wed, 10 Feb 2021 09:56:16 +0100
schrieb Baurzhan Ismagulov <ibr@radix50.net>:
> Hello Daniel,
>
> On Tue, Feb 09, 2021 at 08:45:06PM +0000, Daniel Machon wrote:
> > Would you consider a patch series that adds support for separating
> > the DISTRO_ARCH from the generation of the grub image?
> >
> > We have a use case where target userland is i386, but firmware only
> > supports loading of 64bit EFI executables. Currently the
> > DISTRO_ARCH is also used to generate the grub image - if distro
> > arch is i386, then grub image is bootia32.efi.
> >
> > We fixed this by introducing a new variable used (in
> > bootimg-efi-isar.py) to separately decide the grub image.
>
> IIRC, we've already had a similar use case (mixing i386 and amd64
> userland), so this one could be interesting as well. In any case, I'm
> looking forward to the patches and discussion.
I would not be against it but maybe as a more generic mixing pattern
than just that one.
For your current hack you should be able to do all that in a layer
instead of touching isar ... in case you are patching it.
> Why do you want to have i386 userland on amd64?
My guess would be legacy applications. And my suggestion would be ...
full on 64bit and just have the problematic applications be 32bit
Isar has support for this via ISAR_ENABLE_COMPAT_ARCH where "i386" is
the little brother of "amd64". Similar for arm32 and 64.
Henning
> With kind regards,
> Baurzhan.
>
next prev parent reply other threads:[~2021-02-10 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 20:45 Daniel Machon
2021-02-10 8:56 ` Baurzhan Ismagulov
2021-02-10 10:42 ` Henning Schild [this message]
2021-02-10 13:14 ` Daniel Machon
2021-02-10 14:23 ` Henning Schild
2021-02-17 10:41 ` Baurzhan Ismagulov
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=20210210114244.439de40a@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--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