Uncompress debug for multiplatform
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 Latest posting 2/20 of 2 patches 0 repliesNew
- v4 posting 1/20 of 2 patches 0 repliesSuperseded
Patches in v4 posting 2/2 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.
Cover letter [PATCH v4 0/2] Uncompress debug for multiplatform
Quoted 21 lines · Shawn Guo
Quoted 20 lines · Stephen Warren
Quoted 18 lines · Russell King - ARM Linux
Quoted 10 lines · Shawn Guo
Instead of giving zero support of uncompress debug for multiplatform build, the series turns uncompress debug into one part of
DEBUG_LLsupport. WhenDEBUG_LLis turned on for a particular platform, uncompress debug works too for that platform.OMAP is an exception here. OMAP low-level debug code places data in the .data section, and that is allowed in decompressor. That's why
KconfigsymbolDEBUG_UNCOMPRESSthat controls multiplatform uncompress debug support is defined with !DEBUG_OMAP2PLUS_UART.Quoted 5 lines
Changes since v3:
- CreateKconfigsymbolDEBUG_UNCOMPRESSfor building in multiplatform uncompress debug support, so that we can leave out the platform which is part of multiplatform but not ready for being part of uncompress debug like OMAP example.Wasn't Tegra also having problems with this as well?
Quoted 8 lines
Quoted 1 line
Tegra isn't converted to multi-platform yet. I hope to in 3.10.
Yeah, that's why I did not touch Tegra as the series is based on v3.9-rc1 where Tegra hasn't been part of multi-platform yet.
But I just noticed that
debug-macro.Sfor Tegra has been renamed todebug/tegra.S, and we already know it will be broken when multi-platform is enabled together with this series for Tegra.
Was that because the code touches .data? Perhaps I can get away with using some hard-coded IRAM location or something.