qcom-rtss-can: add recipe for RTSS CAN userspace deamon - #3104
qcom-rtss-can: add recipe for RTSS CAN userspace deamon#3104q-AnupKulkarni wants to merge 1 commit into
Conversation
Dmitry Baryshkov (lumag)
left a comment
Dmitry Baryshkov (lumag)
left a comment
There was a problem hiding this comment.
What was the decision during the RTSS meeting regarding CAN daemon?
Dmitry Baryshkov (lumag)
left a comment
Dmitry Baryshkov (lumag)
left a comment
There was a problem hiding this comment.
qcom-rtss-can: align recipe with Yocto conventions
No. Squash your commits. Fix your git setup.
bffbbb1 to
d10f1db
Compare
daemon The RTSS subsystem on Qualcomm SoCs includes a dedicated CAN controller that is not directly accessible from the Linux CAN stack. This recipe builds rtss_can, a userspace daemon that bridges that gap by routing traffic between Linux SocketCAN virtual interfaces and RTSS mailbox channels, allowing standard SocketCAN applications to communicate with CAN hardware managed by RTSS. The daemon depends on qcom-rtss-mailbox-umd for the librtss_mailbox interface and on linux-libc-headers for the SocketCAN kernel UAPI headers (linux/can.h, linux/can/raw.h). Signed-off-by: Anup Kulkarni <anup.kulkarni@oss.qualcomm.com>
d10f1db to
5689383
Compare
Done |
Part of phase-1 deliveries Phase 1 | Tracked here - #3123 |
| DEPENDS = "glib-2.0 qcom-rtss-mailbox-umd linux-libc-headers" | ||
|
|
||
| SRC_URI = "git://github.com/qualcomm/rtss-can.git;branch=rtss-can.le.1.0;protocol=https;tag=v${PV}" | ||
| SRCREV = "50c719138277f8e1135e04fd4e9137446823e726" |
There was a problem hiding this comment.
This commit hash is not the tag, it should be qualcomm/rtss-can@78ba248.
| LICENSE = "BSD-3-Clause" | ||
| LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=223037c4be0bfc6cf757035432adf983" | ||
|
|
||
| DEPENDS = "glib-2.0 qcom-rtss-mailbox-umd linux-libc-headers" |
There was a problem hiding this comment.
qcom-rtss-mailbox-umd not yet available, moving PR to draft.
| -DSYSROOT_INCLUDEDIR=${STAGING_INCDIR} \ | ||
| -DSTAGING_LIBDIR=${STAGING_LIBDIR}" | ||
|
|
||
| RDEPENDS:${PN} = "can-utils qcom-rtss-mailbox-umd can-utils-access" |
There was a problem hiding this comment.
can-utils is from meta-oe, needs to move to dynamic layers.
| DESCRIPTION = "Userspace daemon acting as a gateway between SocketCAN \ | ||
| applications and RTSS using the RTSS mailbox UMD libraries." | ||
|
|
||
| HOMEPAGE = "https://github.com/qualcomm/rtss-can" |
There was a problem hiding this comment.
Is it aarch64 only? If so, needs a compatible machine line.
|
Functional gaps at runtime:
Cleanups:
|
That's not what I meant. What is the agreed ETA for the in-kernel replacement driver? |
4 participants
Target milestone: qli-2.1 pull-request freeze
Background
The RTSS subsystem on Qualcomm SoCs includes a dedicated CAN controller that is not directly accessible from the Linux CAN stack. This recipe builds rtss_can, a userspace daemon that bridges that gap by routing traffic between Linux SocketCAN virtual interfaces and RTSS mailbox channels, allowing standard SocketCAN applications to communicate with CAN hardware managed by RTSS. The daemon depends on qcom-rtss-mailbox-umd for the librtss_mailbox interface and on linux-libc-headers for the SocketCAN kernel UAPI headers (linux/can.h, linux/can/raw.h).
PR dependency
#3084
Tracking
#3123
Testing
Default bootup verified on lemans and monaco targets.