DRM/KMS troubles on Jetson Orin Nano

I am trying to get access to a framebuffer using DRM/KMS ioctl requests. I can’t get it to work.

What works:

  1. CREATE_DUMB / MAP_DUMB — buffer allocation works
  2. Read-only DRM queries — connector, mode, resource enumeration all work

What doesn’t work:

  1. DRM_IOCTL_SET_CLIENT_CAP returns ENOTSUP for both DRM_CLIENT_CAP_UNIVERSAL_PLANES and DRM_CLIENT_CAP_ATOMIC, even after acquiring DRM master. Yet DRM_IOCTL_GET_CAP reports DRM_CAP_ATOMIC=1. This is contradictory — advertising atomic support but refusing to enable it.
  2. Zero planes visible to any client regardless of master status, because SET_CLIENT_CAP UNIVERSAL_PLANES fails.
  3. DRM_CAP_ATOMIC=1 is misleading — the driver cannot actually perform atomic modesetting from userspace via standard KMS interfaces.

Fortunately i found out that the good old /dev/fb0 works, so i’ll focus on that for the time being.

Has there been any progress in DRM/KMS in the later jetpacks? Why is the Jetson system so non-standard?

Jetson Orin Nano

JetPack 6.1 / L4T R36.4.

Hi,
For developing DRM use-cases on Orin, please refer to the sample:

/usr/src/jetson_multimedia_api/samples/08_video_dec_drm/

Would suggest base on the sample to developer your use-case. And please note dual-plane mode is supported:
Two independent apps displaying on separate DRM planes on Jetson Orin Nano (L4T R39.2) - #5 by DaneLLL

Thanks DaneLLL,

after some more experimentation i got things to work. I am not using libdrm, instead i use low-level kernel ioctl API. It turned out that one of my ioctl operation codes (DRM_IOCTL_SET_CLIENT_CAP) was not right. I have seen my memory mapped pixels on screen today, so cool!