From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6927512860892332032 X-Received: by 2002:a05:651c:503:: with SMTP id o3mr1656284ljp.2.1612953767598; Wed, 10 Feb 2021 02:42:47 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6512:3993:: with SMTP id j19ls1039553lfu.3.gmail; Wed, 10 Feb 2021 02:42:46 -0800 (PST) X-Google-Smtp-Source: ABdhPJwGo3D+XBtN0KAxJex5MYAZ++/I+NGZWKFDKKVEUNj8IJkwjhMzlgXRXuyIKYo1SimTzf9b X-Received: by 2002:a05:6512:143:: with SMTP id m3mr1414840lfo.46.1612953766573; Wed, 10 Feb 2021 02:42:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612953766; cv=none; d=google.com; s=arc-20160816; b=nLL9i4DTa9sQZErnDbnvRQrERg2hwczKAo9gX9YLU3tS3VCiNaT0hgAQ0x8mchkuo8 qW6v9hMxBLM0GGbAjMqHtYt5J3XkqZ2pbJQ9yPaX17enptW3cUYrPg4ea1r1jRrkmA4k LN7wd+TgVcpten2BA3oWhrQyDh9uwJp/uEBZcZrdc8MQE5x2/MKYPmG78lSEGv7T/tHO eD5BF807Gj2kkG/cuVPVWgc7gzzUPXBWlEWz5bqpiomFplfPbj2KmaxsXcWmwx50Z/G0 fYmzu7bJ6Co3OaWo5sPu+nAWcIb3l+MURWWNxaC1b6RlubIEZDbiOACElciW5um+IrXT 6Gzw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=ZIp7yQRBxeJ9q4YhbZ8jQX0BXu8sHd19K2w5oMRFiqA=; b=gxhdkoeF5qRgV/NfJapQJ5DFQtHTU1h7kYxwYMrm0aArnUMZGkknCAumeJXqqfJ/ym BUQ83RUUStMo7nB4gWnEurC5COWj5AbwFh4ypc9spIU5sRdUoZH64s+h+0ChvhtsFx05 jed7X9jzI9N85idlng7POrgCBxMfx7dHmCdtRtOyCfwvrT2V+W9gza+DcIpwkrGLEFiA spYjm/5kRRVm802UexbBp/mqC5YSgmgE3jnBLtv30+OVt9Ub2mh0xb3+sG5SFbHgHPFV yo77viZMw+7PeQIXOgHp/3tDYVMZSSlwTb6LWYRS7yjeKGGBWVSurPTYg9IByqki2soI DSoQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id o5si91205lfg.10.2021.02.10.02.42.46 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Feb 2021 02:42:46 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id 11AAgjeE005327 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 10 Feb 2021 11:42:45 +0100 Received: from md1za8fc.ad001.siemens.net ([139.22.126.201]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 11AAgjii017597; Wed, 10 Feb 2021 11:42:45 +0100 Date: Wed, 10 Feb 2021 11:42:44 +0100 From: Henning Schild To: Baurzhan Ismagulov Cc: "isar-users@googlegroups.com" Subject: Re: Support for generating bootx64.efi when distro arch is i386 Message-ID: <20210210114244.439de40a@md1za8fc.ad001.siemens.net> In-Reply-To: <20210210085616.GU20742@yssyq.m.ilbers.de> References: <86fa58d19dba43d2950b99d6d25067a3@universal-robots.com> <20210210085616.GU20742@yssyq.m.ilbers.de> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: XFv+fL//nZp8 Am Wed, 10 Feb 2021 09:56:16 +0100 schrieb Baurzhan Ismagulov : > 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. >