Hi,
I see this link:
"
The full source code to the NVIDIA implementation of Weston is in:
drive-t186ref-linux/samples/wayland/weston
"
But that is for drive.
Can I get the same for Jetson?
I hope to figure out how to use DRM correctly.
Thank you
Hi,
On Jetson we use gstreamer. Please check
There is a known issue and a user shares a fix:
Cannot use gst-nveglglessink with Wayland on L4T 36.4.0 - #6 by steve.wilkins
Please apply it if you would like to use nveglglessink
For DRM you can use nvdrmvideosink. Source code of the gstreamer plugins is in
Jetson Linux | NVIDIA Developer
Driver Package (BSP) Sources
I looked at nvdrmvideosink at https://nv-tegra.nvidia.com/r/tegra/gst-src/libgstnvdrmvideosink.git
and it apears to be relatively small and primitive code, similar to 08_video_dec_drm,
and does not handle basic use cases, such as display plug/unplug,
(I already reported this few months ago).
But weston, according to the doc at
handles Hot-Plugging.
Also, as I reported in another post today, drm (including 08_video_dec_drm and nvdrmvideosink) does cause more than 10 times slowing down of VIC operations, but weston does not.
DRM has multiple API calls which appear to do the same thing, like submitting frame buffers to planes,
but have different performance implications.
And weston appears to call the right APIs, unlike nvdrmvideosink and 08_video_dec_drm.
But I cannot find weston sources in your links.
Hi,
Hotplug in DRM is not validated, so it may not work properly. As mentioned in
How to reinitialize DRM after display re-plug?
You may see if you can use nveglglessink with winsys=wayland in your use-case. The nveglglessink plugin is open source and low-level Wayland/weston stacks are not.
According to the Jetson/Weston doc linked above: " Weston monitors events sent by the Direct Rendering Manager (DRM) subsystem using udev. When the display configuration changes, udev receives a HOTPLUG event. It calls drmModeGetResources() to identify connectors that have been added or removed, and takes actions accordingly."
And there are 4 " Verified Use Cases"
So, it was validated.
I see that it does appear to recover after unplug/replug,
unlike nvdrmvideosink which shows garbage or, eventually, the whole system crashes.
I just need to know how Weston does it.
Original Weston was open source
and it appears that Nvidial also released its sources for Drive,
I wonder why not for Jetson.