New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined symbol failures if CONFIG_USB=m
#6059
Comments
USB
built as module
USB
built as moduleCONFIG_USB=m
Similarly, with
|
Why are you singling out 6.1 for the USB_DWCOTG dependency problem? For me, the 6.6 kernel is the same. |
Make USB_DWCOTG depend on USB=y to fix potential build failures. See: raspberrypi#6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: raspberrypi#6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
See #6112. Note that this fixes the rpi-6.6.y tree. rpi-6.1.y is not being developed on, but these patches could be back-ported as being low risk. |
I've not tested (When I first filed the bug, I was trying to build a 6.1 kernel. The 6.6 kernel sources still aren't tagged by the looks of things (see #6063), but I've moved on to using them regardless.) |
Make USB_DWCOTG depend on USB=y to fix potential build failures. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make USB_DWCOTG depend on USB=y to fix potential build failures. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make USB_DWCOTG depend on USB=y to fix potential build failures. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Make CONFIG_FB_BCM2708 select CONFIG_FB_DEVICE, to avoid potential build problems. See: #6059 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Describe the bug
If
CONFIG_USB_DWCOTG=y
is set butCONFIG_USB=m
, building the6.1.73
/stable_20240124
(and likely previous) kernel(s) fails with:Steps to reproduce the behaviour
Device (s)
Raspberry Pi CM4
System
Kernel
6.1.73
Logs
No response
Additional context
The easy fix would be to make
CONFIG_USB_DWCOTG
depend onCONFIG_USB=y
, but might it be possible to fix the DWC driver code to be able to be built as a module itself, or integrated in such a way that it works if USB support overall is a module?The text was updated successfully, but these errors were encountered: