On Mon, Jul 29, 2019 at 09:32:29AM -0600, Simon Glass wrote:
Hi Kever,
On Sun, 28 Jul 2019 at 21:03, Kever Yang kever.yang@rock-chips.com wrote:
Hi Simon,
On 2019/7/28 下午11:20, Simon Glass wrote:
Hi Kever,
On Sun, 28 Jul 2019 at 08:12, Simon Glass sjg@chromium.org wrote:
HI Kever,
On Sun, 28 Jul 2019 at 05:14, Kever Yang kever.yang@rock-chips.com wrote:
Hi Simon,
When I'm using the buildman for rockchip platform, it's alwaysbuild only 20 boards,
and many boards are not build, there are 38 boards with its defconfig in configs/ dir,
could you help to check what's missing?
I think I commented on this at the time of the patches to move away from arch-rockchip. There are now separate arch directories for each soc. Most of them don't mention rockchip at all. See boards.cfg for the resulting output.
There is no Kconfig string option for SoC vendor now, is it possible to add info by Kconfig option
which is able to identify the SoC vendor into boards.cfg? eg. There is a CONFIG_ARCH_ROCKCHIP
for rockchip platform, and the 'CONFIG_ARCH_' seems also use for many other platform.
See build log:
One more thing...to check what builds will be built try -nv :
buildman -nv rockchip
This will list the boards. You could use 'rk' instead of 'rockchip', perhaps?
Use 'rk' + 'rv' is OK to get all 38 boards for now, there might have SoCs leading with 'px' which will mix
with other SoC vendors.
Well, the only thing I can think oi is going back to the SoC being rockchip. Or maybe add a new thing to boards.cfg?
Part of the problem is that yes, what exactly IS the common string between all rockchip-the-SoC-vendor platforms that will catch the various SoCs as well as non-rockchip-the-board-producer platforms?
All that said, we shouldn't add more to boards.cfg we should make buildman consume/generate the db? May save us needing to convert genboardscfg.py to python3 :)