The mainline uses 'rk3399-*', so there're rk3399-firefly.dts, rk3399-roc-pc.dts, rk3399-khadas-edge.dts, etc. Shall we follow the kernel convention, or add another roc-pc-rk3399 to the matrix? I prefer to keep it as it is.
"Jonathan A. Kollasch" jakllsch@kollasch.net writes:
On Sat, Nov 02, 2019 at 10:19:02AM +0530, Jagan Teki wrote:
roc-rk3399-pc_defconfig is committed in below
commit <8a681f4c5aa15db51ad0209734859c9fe7c29cfd> ("rockchip: rk3399:
Add ROC-RK3399-PC support")
which doesn't follow the existing defconfigs on rk3399.
So, rename as followed with other rk3399 defconfigs.
Cc: Levin Du djw@t-chip.com.cn Signed-off-by: Jagan Teki jagan@amarulasolutions.com
This strikes me as wrong, as the existing name is the actual name of the board.
https://libre.computer/products/boards/roc-rk3399-pc/
Jonathan Kollasch _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot