From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BEA5AC433F5 for ; Fri, 22 Oct 2021 17:11:16 +0000 (UTC) Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C4E8A611CB for ; Fri, 22 Oct 2021 17:11:15 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org C4E8A611CB Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.denx.de Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 561D483458; Fri, 22 Oct 2021 19:11:13 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.b="ldhBjmT7"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 885F8834A9; Fri, 22 Oct 2021 19:11:12 +0200 (CEST) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id A694F8327C for ; Fri, 22 Oct 2021 19:11:09 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=pali@kernel.org Received: by mail.kernel.org (Postfix) with ESMTPSA id 02519611CB; Fri, 22 Oct 2021 17:11:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1634922668; bh=eNZddcMNbtomYcEmFm6zaMnZtK1yoMdFjkjObNF0B+o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ldhBjmT7iwsZ6EaO6axS67Nfw/FeH16sFFFZU0EFteJp5kDJLBF/IGEKuwpCkjara X0l/eah9ABLgNypRJn8epjLt35PUyiLJ1Obf5BtixpVxLUKFwaESGLATDsCNxU/zxT L6Kdfq1IQuiKaLSftOhtxGRM3KBjSJCCUi7BJjGn17lXofilBwsm7pc7nC3+mVYorY TSiR8xVTZUlBML7rIrNy7wNKpoFbTkGeutDr9oIwEs2/kHpGc74ypAV4x5L32ULMz5 mgGx+ppCDU71b5bn7sHNiL/4P5mA+2OvPbpeQYXXP63+rpHMPuAsgMUrXVKwmfrVHD inUQJpWZVITWA== Received: by pali.im (Postfix) id 9EDF27F6; Fri, 22 Oct 2021 19:11:05 +0200 (CEST) Date: Fri, 22 Oct 2021 19:11:05 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Vagrant Cascadian Cc: Tom Rini , Andre Przywara , Marek =?utf-8?B?QmVow7pu?= , Peter Robinson , Matthias Brugger , Heinrich Schuchardt , Samuel Holland , u-boot@lists.denx.de, Jagan Teki , "Alex G ." , Artem Lapkin , Priyanka Jain , Sughosh Ganu Subject: Re: [PATCH v4 1/4] tools: Separate image types which depend on OpenSSL Message-ID: <20211022171105.zlhmxvhtstr6vao2@pali> References: <20211020142902.12219c45@donnerap.cambridge.arm.com> <20211020134752.62k4fxukucj5rodh@pali> <20211021150048.59bb90d6@thinkpad> <20211022165922.22164ef8@thinkpad> <20211022150927.GJ3577824@bill-the-cat> <20211022165609.1725e93b@donnerap.cambridge.arm.com> <20211022162219.GK3577824@bill-the-cat> <87v91pnh08.fsf@yucca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87v91pnh08.fsf@yucca> User-Agent: NeoMutt/20180716 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.34 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean On Friday 22 October 2021 09:47:35 Vagrant Cascadian wrote: > do some boards use board-specific tools as part of their build processes? Lot of boards are using mkimage for generating final U-Boot binary. Prior U-Boot 2021.10 all 32-bit mvebu boards used own specific version of mkimage to generate final U-Boot binary. mkimage had own compile time options (defined in board include header files) which generated unique ./tools/mkimage binary, specific for just one board. Since U-Boot 2021.10 now all 32-bit mvebu boards are using one common mkimage binary. So you can even do defconfig for some x86 board, build mkimage binary and then you can use this mkimage binary also for building final mvebu (arm) U-Boot binary. Side effect of this change was hard dependency on openssl, but we are discussing how to solve and remove that hard dependency. I do not know if there are any processors, SoCs or boards which require board-specific version of some tool (e.g. mkimage) in U-Boot 2021.10.