-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Add CAN_J1939 as module to default build configs #4346
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
Conversation
Abstract: There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4 Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not build for kernel v5.10.y due to the missing flag. Therefore set it to build as module. CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
Cross-compile-tested on X86_64, currently running a native build on a pi0w, that is my test device for CAN related stuff. |
These new settings have been added in the wrong place - they work as is, but using |
Signed-off-by: Patrick Menschel <[email protected]>
Signed-off-by: Patrick Menschel <[email protected]>
ACK |
Native build complete and verified to be working.
|
kernel: Add CAN_J1939 as module to default build configs See: raspberrypi/linux#4346 kernel: add sensirion sgp30 to i2c-sensor overlay See: raspberrypi/linux#4355 kernel: Updated H265 V4L2 decoder plus V4L2 stability fixes See: raspberrypi/linux#4343 firmware: platform: Remove build-time constant for MICROVOLTS_PER_PIP
kernel: Add CAN_J1939 as module to default build configs See: raspberrypi/linux#4346 kernel: add sensirion sgp30 to i2c-sensor overlay See: raspberrypi/linux#4355 kernel: Updated H265 V4L2 decoder plus V4L2 stability fixes See: raspberrypi/linux#4343 firmware: platform: Remove build-time constant for MICROVOLTS_PER_PIP
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
There is a CAN protocol named J1939 which is supported by Linux Kernel since v5.4. Recently J1939 header file turned up in raspberrypi-kernel-headers but the module is not built for kernel v5.10.y due to the missing flag. Therefore set it to build as module: CONFIG_CAN_J1939=m Signed-off-by: Patrick Menschel <[email protected]>
This PR adds the Kconfig flag CONFIG_CAN_J1939=m
Abstract:
Problem:
After building Python3.9.5 , the module turns out to be missing in
regular raspberrypi-kernel
Solution:
Reference: