So it seems like this innocuous-looking arm64 defconfig change has
accidentally (?) demoted CONFIG_RESET_RASPBERRYPI=y to
CONFIG_RESET_RASPBERRYPI=m in the arm64 defconfig.
Was this intentional? If not, I’d be happy if you could send a fix for
this change.
Thank you!
Best regards
Michael
PS: I’m building the Linux kernel using this config addition to the
arm64 defconfig:
https://github.com/gokrazy/kernel/blob/master/cmd/gokr-build-kernel/build.go#L19,
just in case it matters…
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
So it seems like this innocuous-looking arm64 defconfig change has
accidentally (?) demoted CONFIG_RESET_RASPBERRYPI=y to
CONFIG_RESET_RASPBERRYPI=m in the arm64 defconfig.
Was this intentional? If not, I’d be happy if you could send a fix for
this change.
From a running system, can you see if reset-raspberry.ko is included in
your root filesystem? If not, this would definitively be an issue since
that driver is needed in order for xHCI to work on the Pi 4. There does
not appear to be any explicit dependency between reset-raspberry and
xhci-pci.ko, so without manually "front" loading the former before the
latter, I don't think we can have automatic dependencies.
From: Michael Stapelberg <hidden> Date: 2021-09-15 06:36:23
Thanks for your mail.
My system does not use any Linux kernel modules (=m), all required
code is compiled into the kernel itself (=y).
The root file system does not contain any .ko files.
On Tue, 14 Sept 2021 at 23:47, Florian Fainelli [off-list ref] wrote:
+Nicolas, Stefan,
On 9/14/21 2:28 PM, Michael Stapelberg wrote:
So it seems like this innocuous-looking arm64 defconfig change has
accidentally (?) demoted CONFIG_RESET_RASPBERRYPI=y to
CONFIG_RESET_RASPBERRYPI=m in the arm64 defconfig.
Was this intentional? If not, I’d be happy if you could send a fix for
this change.
From a running system, can you see if reset-raspberry.ko is included in
your root filesystem? If not, this would definitively be an issue since
that driver is needed in order for xHCI to work on the Pi 4. There does
not appear to be any explicit dependency between reset-raspberry and
xhci-pci.ko, so without manually "front" loading the former before the
latter, I don't think we can have automatic dependencies.
From: nicolas saenz julienne <nsaenz@kernel.org> Date: 2021-09-15 07:44:24
Hi Michael,
On Wed, 2021-09-15 at 08:33 +0200, Michael Stapelberg wrote:
Thanks for your mail.
My system does not use any Linux kernel modules (=m), all required
code is compiled into the kernel itself (=y).
The root file system does not contain any .ko files.
Are you building your own kernels? Then I suggest to configure the
raspberrypi-reset driver as builtin (=y) so it's available in your kernel
image.
Could you provide more information on how your system/rootfs is built and
setup?
Regards,
Nicolas
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Michael Stapelberg <hidden> Date: 2021-09-15 07:58:22
Hey Nicolas
On Wed, 15 Sept 2021 at 09:42, nicolas saenz julienne [off-list ref] wrote:
Hi Michael,
On Wed, 2021-09-15 at 08:33 +0200, Michael Stapelberg wrote:
quoted
Thanks for your mail.
My system does not use any Linux kernel modules (=m), all required
code is compiled into the kernel itself (=y).
The root file system does not contain any .ko files.
Are you building your own kernels? Then I suggest to configure the
raspberrypi-reset driver as builtin (=y) so it's available in your kernel
image.
Yes, I have already done that. I was more interested in fixing this
problem for others, and/or avoiding similar problems in the future.
Could you provide more information on how your system/rootfs is built and
setup?
From: nicolas saenz julienne <nsaenz@kernel.org> Date: 2021-09-15 08:56:40
On Wed, 2021-09-15 at 09:55 +0200, Michael Stapelberg wrote:
Hey Nicolas
On Wed, 15 Sept 2021 at 09:42, nicolas saenz julienne [off-list ref] wrote:
quoted
Hi Michael,
On Wed, 2021-09-15 at 08:33 +0200, Michael Stapelberg wrote:
quoted
Thanks for your mail.
My system does not use any Linux kernel modules (=m), all required
code is compiled into the kernel itself (=y).
The root file system does not contain any .ko files.
Are you building your own kernels? Then I suggest to configure the
raspberrypi-reset driver as builtin (=y) so it's available in your kernel
image.
Yes, I have already done that. I was more interested in fixing this
problem for others, and/or avoiding similar problems in the future.
quoted
Could you provide more information on how your system/rootfs is built and
setup?
Thanks for the info.
IMO the solution is to maintain your own configuration. The decision not to use
kernel modules, even if reasonable given the scope of gokrazy, is a big
deviation from how the kernel is regularly consumed. The majority of the arm64
defconfig users need the kernel image to be as small as possible to avoid
bloating the boot partition, and allowing for reasonable boot speeds (imagine
having to load a 1GB kernel image from the SD card).
Regards,
Nicolas
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Michael Stapelberg <hidden> Date: 2021-09-18 09:31:09
On Wed, 15 Sept 2021 at 10:54, nicolas saenz julienne [off-list ref] wrote:
On Wed, 2021-09-15 at 09:55 +0200, Michael Stapelberg wrote:
quoted
Hey Nicolas
On Wed, 15 Sept 2021 at 09:42, nicolas saenz julienne [off-list ref] wrote:
quoted
Hi Michael,
On Wed, 2021-09-15 at 08:33 +0200, Michael Stapelberg wrote:
quoted
Thanks for your mail.
My system does not use any Linux kernel modules (=m), all required
code is compiled into the kernel itself (=y).
The root file system does not contain any .ko files.
Are you building your own kernels? Then I suggest to configure the
raspberrypi-reset driver as builtin (=y) so it's available in your kernel
image.
Yes, I have already done that. I was more interested in fixing this
problem for others, and/or avoiding similar problems in the future.
quoted
Could you provide more information on how your system/rootfs is built and
setup?
Thanks for the info.
IMO the solution is to maintain your own configuration. The decision not to use
kernel modules, even if reasonable given the scope of gokrazy, is a big
deviation from how the kernel is regularly consumed. The majority of the arm64
defconfig users need the kernel image to be as small as possible to avoid
bloating the boot partition, and allowing for reasonable boot speeds (imagine
having to load a 1GB kernel image from the SD card).
Yep, effectively I am maintaining my own configuration, but I still
run defconfig before applying my own additions to .config.
I think that in general I do want the changes that defconfig brings,
so defconfig+additions is the only way I see, and I thought this was
best practice?
Are you saying there might be a better option? Or perhaps the best
move is to just support modules in gokrazy after all.
Thanks for your advice,