Enable J1939 support by default in agl-service-can-low-level
Won't Fix
Description
As described in SPEC-3765, J1939 support is not enabled by default in the agl-service-can-low-level CAN binding, and is only enabled specifically for the qemu platforms when building via the full image build. The restriction on enabling it by default comes from needing a >= 5.4 kernel to have J1939 support. In Koi, currently only the RaspberryPi is using a kernel too old to have it, and this should hopefully be resolved soon with a fix for SPEC-3702. Once that happens, flipping the default for J1939 support and potentially reverting changes done for SPEC-3765 should be investigated.
Environment
None
Activity
Show:
Scott Murray
December 7, 2021 at 4:56 PM
Closing this since there's not much point doing it on the now deprecated binding.
As described in SPEC-3765, J1939 support is not enabled by default in the agl-service-can-low-level CAN binding, and is only enabled specifically for the qemu platforms when building via the full image build. The restriction on enabling it by default comes from needing a >= 5.4 kernel to have J1939 support. In Koi, currently only the RaspberryPi is using a kernel too old to have it, and this should hopefully be resolved soon with a fix for SPEC-3702. Once that happens, flipping the default for J1939 support and potentially reverting changes done for SPEC-3765 should be investigated.