Message ID | 20200323163431.7678-1-digetx@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Introduce NVIDIA Tegra Partition Table | expand |
23.03.2020 19:34, Dmitry Osipenko пишет: > Some NVIDIA Tegra devices have GPT entry at a wrong location and others may > even not have it at all. So either a custom workaround for GPT parsing or > TegraPT support is needed for those devices if we want to support them in > upstream kernel. The former solution was already rejected [1], let's try > the latter. > > [1] https://patchwork.ozlabs.org/patch/1240809/ > > Big thanks to everyone who helped with figuring out the TegraPT format! > > Changelog: > > v3: - Fixed "BUG: KASAN: slab-out-of-bounds in tegra_partition". Thanks to > Peter Geis for noticing the problem. > > - The MMC boot partitions scanning is now opt-in. See this patch: > > mmc: block: Support partition-table scanning on boot partitions > > - The found MMC boot partitions won't be assigned to the MMC boot > block device ever due to the new GENHD_FL_PART_SCAN_ONCE flag. > > This makes us to ensure that the old behavior of the MMC core is > preserved for a non-Tegra MMC-block users. > > New patches in v3: > > block: Introduce GENHD_FL_PART_SCAN_ONCE > mmc: sdhci-tegra: Enable boot partitions scanning on Tegra20 and Tegra30 I forgot to mention that the TegraPT Kconfig entry now depends on MMC, which was suggested by Randy Dunlap in the review comment to the v2.
On Mon, Mar 23, 2020 at 07:34:21PM +0300, Dmitry Osipenko wrote: > Some NVIDIA Tegra devices have GPT entry at a wrong location and others may > even not have it at all. So either a custom workaround for GPT parsing or > TegraPT support is needed for those devices if we want to support them in > upstream kernel. The former solution was already rejected [1], let's try > the latter. [...] Hi Dmitry, This amusing use of whole-device offsets in the TegraPT makes it take a lot of hacks to support it. Have you considered to first join the MMC hardware partitions using DM and its linear target and only then processing the partition table dividing just the merged device? Best Regards, Michał Mirosław
23.03.2020 21:07, Michał Mirosław пишет: > On Mon, Mar 23, 2020 at 07:34:21PM +0300, Dmitry Osipenko wrote: >> Some NVIDIA Tegra devices have GPT entry at a wrong location and others may >> even not have it at all. So either a custom workaround for GPT parsing or >> TegraPT support is needed for those devices if we want to support them in >> upstream kernel. The former solution was already rejected [1], let's try >> the latter. > [...] > > Hi Dmitry, > > This amusing use of whole-device offsets in the TegraPT makes it take > a lot of hacks to support it. Have you considered to first join the MMC > hardware partitions using DM and its linear target and only then processing > the partition table dividing just the merged device? Hello Michał, Thank you very much for the suggestion! I had a thought about that and it's not apparent to me how to determine when the joining needs to be done and when not. The joining shouldn't be done for devices that aren't booting from eMMC because then the alt GPT entry will be found on a joined block device and this shouldn't happen. Actually, maybe we could create a new MMC device-tree property, telling that the joining needs to be performed. Perhaps this indeed could result in a less hackery, I'll give it a try and see how it goes.