Great to see progress on mainlining more support for common and powerful chips. The work required to get this one piece into mainline over 5-6 years reveals why most chip vendors aren’t aiming for mainline by default: > A few iterations of the rkcif driver later, the basic driver providing support for the PX30 VIP and the RK3568 VICAP was accepted (October 2025). After more than five years of development, including 2…
I really feel like that should be table stakes if your entire business is making chips to run Linux, though after working professionally with their stuff I'm really not a fan of Rockchip
Initial mainline video capture and camera support for Rockchip RK3588
21–30 of 30 posts
Re: Initial mainline video capture and camera support for Rockchip RK3588
#22Re: Initial mainline video capture and camera support for Rockchip RK3588
#23Worth noting that, well, alas, camera support is incredibly incredibly incredibly cursed, period. It feels like, broadly, with all the image blocks, everyone makes really neat really good hardware thats chock-a-block full of capabilities that are un- or poorly documented or really hard to support for reasons, etc. Its a pretty bespoke high throughput pipeline with a lot of special domain knowledge very unlike anythin…
Wait is IPU6 working now? My work laptop has it and the only thing I know is it might work provided I use some user space relay driver and a bunch of other things. Has this situation improved?
Re: Initial mainline video capture and camera support for Rockchip RK3588
#24I guess I don't understand... why would the SOC manufacturer spend the money on integrating this stuff if they don't intend on also spending the money to enable it on the software side?
They did, jut not mainline. People forget these are embedded chips - they are intended to go inside of something and do one thing. These chips lack auto hardware discovery because the manufacturer assumes the customer will only turn on the hardware peripherals they need for their specific use case and build a static kernel image to meet that requirement. They ship a product that will likely see few, if any software u…
Desktop computer was a reach. Even for BeagleBone.
I am surprised RK3566 and RK3568 still don't have good UEFI-EDK2 support.
RK3588 has great UEFI-EDK2 support. I wish somebody would backport RK356x and RK3399 boards....
The pace of development is too fast. We don't need more aarch64 CPU but better support. RISC-V adds to the mayhem.
Like we need that...
The Open Source Hardware Dream.
Re: Initial mainline video capture and camera support for Rockchip RK3588
#25Great to see progress on mainlining more support for common and powerful chips. The work required to get this one piece into mainline over 5-6 years reveals why most chip vendors aren’t aiming for mainline by default: > A few iterations of the rkcif driver later, the basic driver providing support for the PX30 VIP and the RK3568 VICAP was accepted (October 2025). After more than five years of development, including 2…
Re: Initial mainline video capture and camera support for Rockchip RK3588
#26Its always IP. Afair even Raspberry Pi didnt open ISP, and support for MIPI took yeaaaaars.
Re: Initial mainline video capture and camera support for Rockchip RK3588
#27Earlier quoted context omitted.
They did, jut not mainline. People forget these are embedded chips - they are intended to go inside of something and do one thing. These chips lack auto hardware discovery because the manufacturer assumes the customer will only turn on the hardware peripherals they need for their specific use case and build a static kernel image to meet that requirement. They ship a product that will likely see few, if any software u…
I agree with much of what you say. Adding a second display port was not something anybody needed. Desktop computer was a reach. Even for BeagleBone. I am surprised RK3566 and RK3568 still don't have good UEFI-EDK2 support. RK3588 has great UEFI-EDK2 support. I wish somebody would backport RK356x and RK3399 boards.... The pace of development is too fast. We don't need more aarch64 CPU but better support. RISC-V adds t…
Re: Initial mainline video capture and camera support for Rockchip RK3588
#28Re: Initial mainline video capture and camera support for Rockchip RK3588
#29Great to see progress on mainlining more support for common and powerful chips. The work required to get this one piece into mainline over 5-6 years reveals why most chip vendors aren’t aiming for mainline by default: > A few iterations of the rkcif driver later, the basic driver providing support for the PX30 VIP and the RK3568 VICAP was accepted (October 2025). After more than five years of development, including 2…
> why most chip vendors aren’t aiming for mainline by default: > It’s never as simple as submitting existing work upstream and making a few changes. If they had started by working with upstream, then they wouldn't have to go through unnecessary revisions trying to adapt the thing they already wrote.
LOL. It simply doesn't work that way.
It's all about time to market. A BSP with a custom fork of the Linux kernel that barely works can be done concurrent with hardware development.
But if you say as a manufacturer, we'll first get it upstream-supported by Linux and then release the hardware... by the time the quality is good enough for the proper upstream Linux kernel, the hardware is multiple generations outdated.
And often enough, the software side is an afterthought. The BSP teams get thrown the hardware and told to "make it work", which all too often means having to do horrible hacks to the Linux kernel that would be completely unacceptable upstream. Even if they'd hire Greg KH himself, the fundamental problem remains that the BSP teams aren't asked if the HW designers can make the life of the BSP team easier.
The one notable exception to this unholy mess, however, is Apple. And that is why Apple hardware seamlessly integrates within the ecosystem, why it is so performant and why it is so energy efficient.
Re: Initial mainline video capture and camera support for Rockchip RK3588
#30Earlier quoted context omitted.
I work in this field and this is 100 percent true. It's really hard to learn about too. A lot of textbooks go over the algorithms in the chips in an idealized form. The actual versions are so messy and different that the textbooks aren't even useful sometimes, especially if you work on custom ISPs. It's cursed, but it's fun.
Are there any resources you would recommend for learning about real implementations?