arm4 non-cloud 6.6 kernel now has CONFIG_REMOTEPROC=y enabled. This…

… gets explicitly disabled for cloud kernels.


Debian commit that enabled this: https://salsa.debian.org/kernel-team/linux/-/commit/f994ffb127c90e04fd8252b79a021b60cb5e4507#fc973071e6f4da49be1ec7a17e00635dd41dcaf1_1392_1420

We can safely set `CONFIG_REMOTEPROC=n` to disable it again.
* our 6.1 kernel also has it disabled
* other configs defined in drivers/remoteproc/Kconfig can be ignored because of https://github.com/torvalds/linux/blob/b401b621758e46812da61fa58a67c3fd8d91de0d/drivers/remoteproc/Kconfig#L15 
    * were not in 6.1 before
    * will also be disabled if CONFIG_REMOTEPROC is false or not set

We have tests in gardenlinux/gardenlinux repo that check if /proc is empty. This test has detected that CONFIG_REMOTEPROC got enabled

debian/config/config.gardenlinux

@@ -22,3 +22,7 @@ CONFIG_X86_SGX=y
 CONFIG_X86_SGX_KVM=y
 
 CONFIG_MAGIC_SYSRQ=n
+
+# Disable it for all architectures
+# 6.6 kernel implicitly enabled this via https://salsa.debian.org/kernel-team/linux/-/commit/f994ffb127c90e04fd8252b79a021b60cb5e4507#fc973071e6f4da49be1ec7a17e00635dd41dcaf1_1392_1420
+CONFIG_REMOTEPROC=n