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 X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 042B6C43331 for ; Mon, 23 Mar 2020 21:35:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CEB9C2076E for ; Mon, 23 Mar 2020 21:35:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=rere.qmqm.pl header.i=@rere.qmqm.pl header.b="Fv7ozbGf" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726962AbgCWVf1 (ORCPT ); Mon, 23 Mar 2020 17:35:27 -0400 Received: from rere.qmqm.pl ([91.227.64.183]:14178 "EHLO rere.qmqm.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725897AbgCWVf1 (ORCPT ); Mon, 23 Mar 2020 17:35:27 -0400 Received: from remote.user (localhost [127.0.0.1]) by rere.qmqm.pl (Postfix) with ESMTPSA id 48mSNB3H8BzWS; Mon, 23 Mar 2020 22:35:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=rere.qmqm.pl; s=1; t=1584999324; bh=pV85d3OblMJ7RfsZIWWNkfwMsTCzcwys5+ldfE8oyZw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Fv7ozbGfqk4BAVi284jvwufI0hVjijArO/XOUuhWlDD89PPjHCarTiS4+vK1mLWmF DVrJtYAOhraUK5SWlXX3puKkx7cHu9Izmlao4fdzra6GVS4GRsOt2PtTR9LBtUeuew ISMmmXeSeKf+pTj3r3pby2kz6gewBNTXjM+g72iTo3c+cQs2JdYYSDjU7N7mT4mzt8 gYfJddytE23BcOX0fnhr2zdaDfp5E7D9lwz0M4MYIh/ZxqHo2ixHNnfkY+tI06YcS6 CbjH7zDW0pQXVzQZ3yGdyqN0HUQc7h5dEw5eUDAbbIa4/zfuuWUSXQ6CVwyT8vS0oo xwY0W70E5c50g== X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.2 at mail Date: Mon, 23 Mar 2020 22:35:20 +0100 From: =?iso-8859-2?Q?Micha=B3_Miros=B3aw?= To: Dmitry Osipenko Cc: Jens Axboe , Thierry Reding , Jonathan Hunter , David Heidelberg , Peter Geis , Stephen Warren , Nicolas Chauvet , Ulf Hansson , Adrian Hunter , Billy Laws , linux-tegra@vger.kernel.org, linux-block@vger.kernel.org, Andrey Danin , Gilles Grandou , Ryan Grachek , linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 03/10] partitions: Introduce NVIDIA Tegra Partition Table Message-ID: <20200323213520.GA16587@qmqm.qmqm.pl> References: <20200323163431.7678-1-digetx@gmail.com> <20200323163431.7678-4-digetx@gmail.com> <20200323191748.GB30585@qmqm.qmqm.pl> <67140755-c829-5c58-3fbf-efd496e225df@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <67140755-c829-5c58-3fbf-efd496e225df@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-mmc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-mmc@vger.kernel.org On Mon, Mar 23, 2020 at 10:59:52PM +0300, Dmitry Osipenko wrote: > 23.03.2020 22:17, Michał Mirosław пишет: > > On Mon, Mar 23, 2020 at 07:34:24PM +0300, Dmitry Osipenko wrote: > >> All NVIDIA Tegra devices use a special partition table format for the > >> internal storage partitioning. Most of Tegra devices have GPT partition > >> in addition to TegraPT, but some older Android consumer-grade devices do > >> not or GPT is placed in a wrong sector, and thus, the TegraPT is needed > >> in order to support these devices properly in the upstream kernel. This > >> patch adds support for NVIDIA Tegra Partition Table format that is used > >> at least by all NVIDIA Tegra20 and Tegra30 devices. > >> > >> Signed-off-by: Dmitry Osipenko > >> --- > >> arch/arm/mach-tegra/tegra.c | 54 ++++ > > [...] > > > > Please split off this part and make the information available to > > userspace (pt_addr + pt_size) if found. This would make it easier > > to support use the partition table later in initrd instead. > > Please clarify what do you mean by "use the partition table later in > initrd instead". Configure device-mapper to span eMMC boot+data partitions and then ask (modified) kpartx to partition the resulting device. All before rootfs is mounted and switched to in initrd. Best Regards Michał Mirosław