From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andre Heider Date: Thu, 27 Aug 2020 18:29:48 +0200 Subject: [PATCH 2/2] arm: mvebu: Espressobin: Setup MTD partitions when booting kernel In-Reply-To: <20200819142417.15771-2-pali@kernel.org> References: <20200819142417.15771-1-pali@kernel.org> <20200819142417.15771-2-pali@kernel.org> Message-ID: <7d34df2b-b7d2-facd-ae2a-487470340b83@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 19/08/2020 16:24, Pali Roh?r wrote: > Due to different partition layouts in different U-Boot versions, DTS for > Espressobin in Linux does not contain any definition of MTD partitions. > See commit https://git.kernel.org/stable/c/00954566464a4 for more details. > > This patch via ft_board_setup() hook fills current partition layout used by > U-Boot, so booted kernel would see correct MTD partitions layout. > > U-Boot env partition is calculated from CONFIG_ENV_OFFSET option. > > First partition contains secure firmware, ARM trusted firmware and U-Boot > with checksums. So it is not possible to replace just one image (e.g. > U-Boot) without updating other parts where is stored checksum of U-Boot. > Therefore there is no extra partition defined for U-Boot and first > partition is called just 'firmware'. > > Signed-off-by: Pali Roh?r Tested-by: Andre Heider