Add support for Firefly-ROC-RK3328-CC

[daijh223]

please add support for firefly-roc-rk3328-cc

roc-rk3328-cc wiki:http://en.t-firefly.com/doc/product/info/381.html#

[igorpecovnik]

We don't need new family. Use rk3328 and only add u-boot patch for this particular board if needed. U-boot is unique for each board and userspace changes are packed into boards support package. Specifics can be added to family config -> sources/rk3328.conf

Please rework. Thanks!

[daijh223]

@igorpecovnik
Do you mean that the same chip can't modify the BOARDFAMILY ?
Is BOARDFAMILY only equal to rk3328？
But in the sources/rk3328.conf file ：
BOOTSOURCE='https://github.com/ayufan-rock64/linux-u-boot'
......
ATFSOURCE='https://github.com/ayufan-rock64/arm-trusted-firmware'
......
KERNELSOURCE='https://github.com/ayufan-rock64/linux-kernel'
......
All come from a particular board(rock64)

If I want to add support to my board, can I only use rock64 source code and add my patch？

[Tonymac32]

In general yes. The Ayufan source is the Rockchip source with some work done to better support the SoC family and Rock64. It isn't, as far as I'm aware, Rock64-centric in practice, it can be used to produce kernels for other hardware (the power of the device tree). I think more than one person has created rk3328 TV box images using this source. See comparison: rockchip-linux/kernel@release-4.4...ayufan-rock64:release-4.4 I agree in principle that pulling the kernel directly from Rockchip would be a better solution, and having a patchset for the boards we support. However, someone would have to maintain that patchset, and that is no small task.

[ThomasKaiser]

I too vote for using ayufan's kernel for whatever RK3328 (and RK3399) device.

[daijh223]

I made some changes to my first submission.Only add kernel dts ,config/boards/roc-rk3328-cc.wip,and u-boot patch for roc-rk3328-cc.

[igorpecovnik]

This is much better. Only one tiny remark (you can leave it as is) - we usually don't store full u-boot config. I don't have other complaints. Until official maintainer is not set, a board can actually be a .csc target (community supported), not .wip. We don't have this hardware so end-user support is not possible.

[daijh223]

I'm sorry.I haven't thought consummately.now i change .wip to .csc