From: Daniel Machon <dama@universal-robots.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Support for generating bootx64.efi when distro arch is i386
Date: Tue, 9 Feb 2021 20:45:06 +0000 [thread overview]
Message-ID: <86fa58d19dba43d2950b99d6d25067a3@universal-robots.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1754 bytes --]
Hi,
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.
Best regards,
Daniel
Med venlig hilsen / Best regards
Daniel Machon
Embedded Linux Engineer
R&D Department
[cid:UR_New_Logo_266cf885-8c99-4fe9-bae0-ff88fedf0005.png]
Universal Robots A/S
Energivej 25
5260 Odense S
Phone: +45 89 93 89 89
Cell: +45 27 99 72 32
dama@universal-robots.com<mailto:dama@universal-robots.com>
www.universal-robots.com<http://www.universal-robots.com>
Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.
If Universal Robots A/S processes personal data relating to physical persons, such processing will meet the requirements of applicable data protection legislation.Please see our Privacy Policy here.<https://www.universal-robots.com/about-universal-robots/privacy-policy/>
[-- Attachment #1.2: Type: text/html, Size: 4884 bytes --]
[-- Attachment #2: UR_New_Logo_266cf885-8c99-4fe9-bae0-ff88fedf0005.png --]
[-- Type: image/png, Size: 3508 bytes --]
next reply other threads:[~2021-02-10 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 20:45 Daniel Machon [this message]
2021-02-10 8:56 ` Baurzhan Ismagulov
2021-02-10 10:42 ` Henning Schild
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=86fa58d19dba43d2950b99d6d25067a3@universal-robots.com \
--to=dama@universal-robots.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