From 70d26c75473e917714d3207d3baea82cbb58c05f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Wed, 21 Nov 2018 00:00:02 +0000 Subject: [PATCH] CONFIG_HAVE_KERNEL_UNCOMPRESSED=y is s390 only --- README.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.adoc b/README.adoc index 7249100..110a135 100644 --- a/README.adoc +++ b/README.adoc @@ -1344,7 +1344,7 @@ See also: https://stackoverflow.com/questions/2589845/what-are-the-first-operati <> with `--debug-flags=Exec` does show the right symbols however! So in the worst case, we can just read their source. Amazing. -TODO: try out `CONFIG_HAVE_KERNEL_UNCOMPRESSED=y` from Linux v4.19 and see if it gives us any extra visibility. +v4.19 also added a `CONFIG_HAVE_KERNEL_UNCOMPRESSED=y` option for having the kernel uncompressed which could make following the startup easier, but it is only available on s390. `aarch64` however is already uncompressed by default, so might be the easiest one: https://unix.stackexchange.com/questions/5518/what-is-the-difference-between-the-following-kernel-makefile-terms-vmlinux-vml/482978#482978 ==== GDB step debug early boot by address