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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 87388C38A2D for ; Wed, 26 Oct 2022 14:03:58 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 2A1D585054; Wed, 26 Oct 2022 16:03:56 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=denx.de Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denx.de; s=phobos-20191101; t=1666793036; bh=Cl9bDKid6p+wCNx3CgTmViBqnyk0awKXviqbngeh79A=; h=Date:Subject:To:Cc:References:From:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=MRMm/5aA/J5nkfkevDCOmsi7/jZ+Qn8GGgCJM1M1jhAA2c7G9S86Z3gCYYbZ1S9vr sa1nSdaUc0bnoSqLCEtkDLPV2Ev1RJtSqfjdbSRpptgB43tvgc7O5CJUhpa13DhwPI d4a6h6H12BTnEbFvguvBLWo2k6teiZ68FNyUoiHzGd8XL2YwgksHc4Rbob6K8H3a1p Dr8Nas4jo1skIoZfFMF0nAUQJZ9JGQ0y+jJZonHFC9yWnh9iamD7MPxejFHp1Hxnj+ UObmeTGhGAk/rYVcVYCBuQPxCOjn2wjMgxv/ic290KBek5jCsuNXb8lB8cYnF75gsk 9Grr5xplCobwA== Received: from [127.0.0.1] (p578adb1c.dip0.t-ipconnect.de [87.138.219.28]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: marex@denx.de) by phobos.denx.de (Postfix) with ESMTPSA id 24A6F80716; Wed, 26 Oct 2022 16:03:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denx.de; s=phobos-20191101; t=1666793034; bh=Cl9bDKid6p+wCNx3CgTmViBqnyk0awKXviqbngeh79A=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=e2YH2TmjtfKBh6SECgepenR23K/JKErBNdiLLKSdHNMwwYDIYZdzS9MbjEzzSI3ca bhBwtHQ0DfCC59K3rUcvKOHmj1FlPEPRuA4RSiHg7jMjZp4da2Kf98te1cTFSwrWy1 mcDK9Pr3Z2I4ujnPy1Q9LbHP9gmMuOpDi2coeJ0VUddT3YYC1AJms7Tzmp5iyjRalW OWReAsNRuMM8LK3KA1+HHjVrCmTVnQ9JWD2+5G03ZobWRF3k30dF+DK8wVaXDfq2r4 S02wF9wT4m/6tiFHrnpUYVcQ6n4TFBhw6jgO55QWJHu/p5GaFEOZcLlk37QTQZfc0P yzccBMZjLPa7Q== Message-ID: <9496de55-e88f-68f0-d4b6-10deef5c7953@denx.de> Date: Wed, 26 Oct 2022 16:03:53 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.3 Subject: Re: [PATCH V2 00/13] IOT2050-related enhancements Content-Language: en-US To: Tom Rini , Jan Kiszka Cc: U-Boot Mailing List , chao zeng , Su Baocheng , Joe Hershberger , Simon Glass References: <20221026135458.GT2020586@bill-the-cat> From: Marek Vasut In-Reply-To: <20221026135458.GT2020586@bill-the-cat> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 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.6 at phobos.denx.de X-Virus-Status: Clean On 10/26/22 15:54, Tom Rini wrote: > On Wed, Oct 26, 2022 at 09:28:09AM +0200, Jan Kiszka wrote: >> On 05.10.22 10:33, Jan Kiszka wrote: >>> (Almost) flushing our upstream queue for the IOT2050 device, this mostly >>> brings board-specific changes such as: >>> >>> - updated build process and firmware layout for PG1 vs. PG2 devices >>> - more watchdog preparations >>> - preparations for verified boot on IOT2050 Advanced devices >>> >>> There are also some generic extensions in this series which are >>> dependencies for the above: >>> >>> - env: Complete generic support for writable list >>> - env: Couple networking-related variable flags to CONFIG_NET (repost) >>> - tools: Add script for converting public key into device tree include >>> >>> Changes in v2: >>> - rebased over latest master >>> - reworked patch 1 to be less invasive to the code >>> - added "iot2050: use the named gpio to control the user-button" >>> >>> Still in our backlog is support for a new variant that comes with M.2 >>> slots. But that requires some more rework first. >> >> Any remaining questions/remarks for this series? Asking also as we would >> like to move forward with upstreaming that M.2 support which depends on >> this one here. > > Marek, I believe you had concerns about the environment side of v1 here, > is v2 more to your liking? Thanks! Nothing changed in V2 in that aspect as far as I can tell.