Thread (17 messages) 17 messages, 5 authors, 2020-03-06

Re: [PATCH v1 3/3] partitions: Introduce NVIDIA Tegra Partition Table

From: Dmitry Osipenko <digetx@gmail.com>
Date: 2020-02-25 01:35:28
Also in: linux-block, linux-mmc, lkml

25.02.2020 03:20, Stephen Warren пишет:
On 2/24/20 4:18 PM, Dmitry Osipenko wrote:
quoted
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.
quoted
diff --git a/arch/arm/mach-tegra/tegra.c b/arch/arm/mach-tegra/tegra.c
quoted
+static void __init tegra_boot_config_table_init(void)
+{
+    void __iomem *bct_base;
+    u16 pt_addr, pt_size;
+
+    bct_base = IO_ADDRESS(TEGRA_IRAM_BASE) + TEGRA_IRAM_BCT_OFFSET;
This shouldn't be hard-coded. IIRC, the boot ROM writes a BIT (Boot
Information Table) to a fixed location in IRAM, and there's some value
in the BIT that points to where the BCT is in IRAM. In practice, it
might work out that the BCT is always at the same place in IRAM, but
this certainly isn't guaranteed. I think there's code in U-Boot which
extracts the BCT location from the BIT? Yes, see
arch/arm/mach-tegra/ap.c:get_odmdata().
Thank you very much, I didn't know about that.

I checked whether Nexus 7 and A500 have a correct pointer in the BIT and
they have it. I'll take it into account in v2, thank you again.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help