home.social

#rk3399 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rk3399, aggregated by home.social.

fetched live
  1. Vivid Unit is RK3399 based embedded computer with 5.5" screen. You can find it here vividunit.com/ and here is my buildroot image for it: codeberg.org/resiliencetheatre
    Pictured here with RAK Wisblock Meshtastic radio.
    #rk3399 #embeddedLinux #meshtastic #rakwireless

  2. Vivid Unit is RK3399 based embedded computer with 5.5" screen. You can find it here vividunit.com/ and here is my buildroot image for it: codeberg.org/resiliencetheatre
    Pictured here with RAK Wisblock Meshtastic radio.
    #rk3399 #embeddedLinux #meshtastic #rakwireless

  3. Vivid Unit is RK3399 based embedded computer with 5.5" screen. You can find it here vividunit.com/ and here is my buildroot image for it: codeberg.org/resiliencetheatre
    Pictured here with RAK Wisblock Meshtastic radio.
    #rk3399 #embeddedLinux #meshtastic #rakwireless

  4. Vivid Unit is RK3399 based embedded computer with 5.5" screen. You can find it here vividunit.com/ and here is my buildroot image for it: codeberg.org/resiliencetheatre
    Pictured here with RAK Wisblock Meshtastic radio.
    #rk3399 #embeddedLinux #meshtastic #rakwireless

  5. This single-board computer has a 5.5 inch touchscreen display

    Most so-called single-board computers feature a processor, memory, and other core features soldered directly to the mainboard. But if you want to actually use the computers, you typically have to plug in a few more things like a keyboard, mouse, and display.
    That’s not an issue with UUGear’s Vivid Unit, because this single-board PC […]

    https://liliputing.com/?p=166574

    #devBoard #rk3399 #sbc #uugear #vivdUnit

  6. This single-board computer has a 5.5 inch touchscreen display

    Most so-called single-board computers feature a processor, memory, and other core features soldered directly to the mainboard. But if you want to actually use the computers, you typically have to plug in a few more things like a keyboard, mouse, and display.
    That’s not an issue with UUGear’s Vivid Unit, because this single-board PC […]

    https://liliputing.com/?p=166574

    #devBoard #rk3399 #sbc #uugear #vivdUnit

  7. After some more debugging, here are two videos proving that #gtk4 / #GStreamer video playback with fullscreen GL/VK overlay works on a #RaspberryPi4 and #PinebookPro / #rk3399 on #weston / #Wayland, each maxing out their video decoders with 1080p@60 and 4k@60 respectively.

    The message here is: no matter what hardware - if you want to make a video/camera app that needs to be highly efficient, you can do it with a proper, yet still lightweight toolkit now. No need for a custom kms/drm backend.

  8. After some more debugging, here are two videos proving that #gtk4 / #GStreamer video playback with fullscreen GL/VK overlay works on a #RaspberryPi4 and #PinebookPro / #rk3399 on #weston / #Wayland, each maxing out their video decoders with 1080p@60 and 4k@60 respectively.

    The message here is: no matter what hardware - if you want to make a video/camera app that needs to be highly efficient, you can do it with a proper, yet still lightweight toolkit now. No need for a custom kms/drm backend.

  9. After some more debugging, here are two videos proving that #gtk4 / #GStreamer video playback with fullscreen GL/VK overlay works on a #RaspberryPi4 and #PinebookPro / #rk3399 on #weston / #Wayland, each maxing out their video decoders with 1080p@60 and 4k@60 respectively.

    The message here is: no matter what hardware - if you want to make a video/camera app that needs to be highly efficient, you can do it with a proper, yet still lightweight toolkit now. No need for a custom kms/drm backend.

  10. After some more debugging, here are two videos proving that #gtk4 / #GStreamer video playback with fullscreen GL/VK overlay works on a #RaspberryPi4 and #PinebookPro / #rk3399 on #weston / #Wayland, each maxing out their video decoders with 1080p@60 and 4k@60 respectively.

    The message here is: no matter what hardware - if you want to make a video/camera app that needs to be highly efficient, you can do it with a proper, yet still lightweight toolkit now. No need for a custom kms/drm backend.

  11. After some more debugging, here are two videos proving that #gtk4 / #GStreamer video playback with fullscreen GL/VK overlay works on a #RaspberryPi4 and #PinebookPro / #rk3399 on #weston / #Wayland, each maxing out their video decoders with 1080p@60 and 4k@60 respectively.

    The message here is: no matter what hardware - if you want to make a video/camera app that needs to be highly efficient, you can do it with a proper, yet still lightweight toolkit now. No need for a custom kms/drm backend.

  12. I seriously have like 20 #rockchip #rk3399 #sbc devices that need a workload.

    I'm good at provisioning computing I just not good at having problems that can be solved with computing.

  13. I seriously have like 20 #rockchip #rk3399 #sbc devices that need a workload.

    I'm good at provisioning computing I just not good at having problems that can be solved with computing.

  14. I seriously have like 20 #rockchip #rk3399 #sbc devices that need a workload.

    I'm good at provisioning computing I just not good at having problems that can be solved with computing.

  15. I seriously have like 20 #rockchip #rk3399 #sbc devices that need a workload.

    I'm good at provisioning computing I just not good at having problems that can be solved with computing.

  16. I seriously have like 20 #rockchip #rk3399 #sbc devices that need a workload.

    I'm good at provisioning computing I just not good at having problems that can be solved with computing.

  17. We once had a dream about a #Rockchip #RK3399 compute cluster module. Now I want that again... but with #rk3588.
    Not sure though if the S version would be sufficient...

  18. We once had a dream about a #Rockchip #RK3399 compute cluster module. Now I want that again... but with #rk3588.
    Not sure though if the S version would be sufficient...

  19. We once had a dream about a #Rockchip #RK3399 compute cluster module. Now I want that again... but with #rk3588.
    Not sure though if the S version would be sufficient...

  20. Update regarding #wayland zero-copy video playback (using hardware planes): with a few small patches it works with #Chromium, both with #vaapi (Intel/AMD) and #v4l2 stateless.

    Here a short video using a #rk3399 - the #PINE64 #PinebookPro - playing a 4k 60fps video - only possible with hardware plane offloading. Playback is *almost* smooth already (~50fps), the goal is to catch up with #GStreamer where we get stable 60.

    I hope this will all get upstreamed in the coming months.

  21. Update regarding #wayland zero-copy video playback (using hardware planes): with a few small patches it works with #Chromium, both with #vaapi (Intel/AMD) and #v4l2 stateless.

    Here a short video using a #rk3399 - the #PINE64 #PinebookPro - playing a 4k 60fps video - only possible with hardware plane offloading. Playback is *almost* smooth already (~50fps), the goal is to catch up with #GStreamer where we get stable 60.

    I hope this will all get upstreamed in the coming months.

  22. Update regarding #wayland zero-copy video playback (using hardware planes): with a few small patches it works with #Chromium, both with #vaapi (Intel/AMD) and #v4l2 stateless.

    Here a short video using a #rk3399 - the #PINE64 #PinebookPro - playing a 4k 60fps video - only possible with hardware plane offloading. Playback is *almost* smooth already (~50fps), the goal is to catch up with #GStreamer where we get stable 60.

    I hope this will all get upstreamed in the coming months.

  23. Update regarding #wayland zero-copy video playback (using hardware planes): with a few small patches it works with #Chromium, both with #vaapi (Intel/AMD) and #v4l2 stateless.

    Here a short video using a #rk3399 - the #PINE64 #PinebookPro - playing a 4k 60fps video - only possible with hardware plane offloading. Playback is *almost* smooth already (~50fps), the goal is to catch up with #GStreamer where we get stable 60.

    I hope this will all get upstreamed in the coming months.

  24. Update regarding #wayland zero-copy video playback (using hardware planes): with a few small patches it works with #Chromium, both with #vaapi (Intel/AMD) and #v4l2 stateless.

    Here a short video using a #rk3399 - the #PINE64 #PinebookPro - playing a 4k 60fps video - only possible with hardware plane offloading. Playback is *almost* smooth already (~50fps), the goal is to catch up with #GStreamer where we get stable 60.

    I hope this will all get upstreamed in the coming months.

  25. Playing 4K@30FPS content on a #PinebookPro ( #rk3399 ) on #gnomeshell with #GStreamer. Looks quite promising already - it's zero-copy from the decoder to the display hardware, which does the downscaling in fixed-function hardware. Just need to fix the jumps/glitches - IIUC it's a kernel issue.

    The relevant part here is that this device struggles to render at 60fps for almost everything on the FullHD screen, including scrolling simple web pages.

  26. Playing 4K@30FPS content on a #PinebookPro ( #rk3399 ) on #gnomeshell with #GStreamer. Looks quite promising already - it's zero-copy from the decoder to the display hardware, which does the downscaling in fixed-function hardware. Just need to fix the jumps/glitches - IIUC it's a kernel issue.

    The relevant part here is that this device struggles to render at 60fps for almost everything on the FullHD screen, including scrolling simple web pages.

  27. Playing 4K@30FPS content on a #PinebookPro ( #rk3399 ) on #gnomeshell with #GStreamer. Looks quite promising already - it's zero-copy from the decoder to the display hardware, which does the downscaling in fixed-function hardware. Just need to fix the jumps/glitches - IIUC it's a kernel issue.

    The relevant part here is that this device struggles to render at 60fps for almost everything on the FullHD screen, including scrolling simple web pages.

  28. Playing 4K@30FPS content on a #PinebookPro ( #rk3399 ) on #gnomeshell with #GStreamer. Looks quite promising already - it's zero-copy from the decoder to the display hardware, which does the downscaling in fixed-function hardware. Just need to fix the jumps/glitches - IIUC it's a kernel issue.

    The relevant part here is that this device struggles to render at 60fps for almost everything on the FullHD screen, including scrolling simple web pages.

  29. Playing 4K@30FPS content on a #PinebookPro ( #rk3399 ) on #gnomeshell with #GStreamer. Looks quite promising already - it's zero-copy from the decoder to the display hardware, which does the downscaling in fixed-function hardware. Just need to fix the jumps/glitches - IIUC it's a kernel issue.

    The relevant part here is that this device struggles to render at 60fps for almost everything on the FullHD screen, including scrolling simple web pages.

  30. Starting to build a based on the n10 chipset soon. can't wait for the parts to arrive :)

  31. BTW: Usually I use my / powered ASUS Chromebook C101p that runs from microSDXC for compile tasks like that, but I sadly don't have it with me right now.

  32. BTW: Usually I use my #GoogleOP1 / #RK3399 powered ASUS Chromebook C101p that runs #ArchLinuxARM from microSDXC for compile tasks like that, but I sadly don't have it with me right now.

  33. New year, new kernel: A look at Collabora's contributions to #Linux 5.11, including the new #Syscall User Dispatch mechanism, the destaging of both the #H264 stateless decoding interface & the #Rockchip ISP driver. col.la/lk511 #OpenSource #RK3399

  34. New year, new kernel: A look at Collabora's contributions to #Linux 5.11, including the new #Syscall User Dispatch mechanism, the destaging of both the #H264 stateless decoding interface & the #Rockchip ISP driver. col.la/lk511 #OpenSource #RK3399

  35. Arm Frame Buffer Compression (AFBC) support for #Rockchip, coming soon to mainline #Linux! Learn more: col.la/afbc #OpenSource #RK3399

  36. Just pushed out a small 20.02.1 bugfix #release for #rk3399 based devices.

    This fixes the issue of #Pamac crashing the #xorg session on #panfrost drivers.

  37. Just pushed out a small 20.02.1 bugfix #release for #rk3399 based devices.

    This fixes the issue of #Pamac crashing the #xorg session on #panfrost drivers.

  38. #Pine64 has some pre #FOSDEM announcements.

    Biggest one is the #PinebookPro.

    14" 1080p display
    **usb-c**, with power input and video output
    #Rockchip #RK3399

    and the usual laptop features. target price, US$199! I look forward to getting #OpenBSD running well on this #arm64 system.

    forum.pine64.org/showthread.ph