RSS Bot Posted August 1, 2022 Share Posted August 1, 2022 Description I copy the patches from rockchip64-5.18 to rockchip64-5.19 and make these changes: 1, rk3328-dtsi-add-rkvdec-node.patch removed because upstream merged. 2, add-board-roc-pc.patch rename rkvdec to vdec 3, add-board-tvbox-rk3318.patch rename rkvdec to vdec, rename rkvdec_mmu to vdec_mmu. 4, board-firefly-rk3399-dts.patch removed since @150balbes said this board is in media family. 5, board-pbp-add-suspend.patch moved to need_checking. Upstream code has changed a lot and I don't know how to do with this patch. 6, refactor-iommu-initialisation.patch removed since already merged to upstream 7, wifi-4005-uwe5622-makefile.patch modified due to upstream change 8, general-add-xtx-spi-nor-chips.patch modified due to upstream change 9, general-rockchip-overlays.patch modified due to upstream change 10, regenerate rock-3a and rk356x patches because rock-3a device tree is in mainline now. 11, add new patch general-hantro-be-more-accurate-on-pixel-formats-step_width-constraints.patch to make hantro hwdec works on rk356x. This is a commit merged to linux-next but not merged to 5.19 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Patches applied with no error, build with no error [x] My rock-3a can boot with this kernel. @catalinii you can test this kernel on your rock3a. [ ] Other rockchip64 board need testing Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article Link to comment Share on other sites More sharing options...
Recommended Posts