Skip to content
This repository was archived by the owner on Nov 20, 2018. It is now read-only.

Conversation

@alexandrebelloni
Copy link
Contributor

Signed-off-by: Alexandre Belloni alexandre.belloni@free-electrons.com

Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
@alexandrebelloni
Copy link
Contributor Author

Completely untested but this should solve:

multi_v4t_defconfig:
    at91sam9261ek: 1 failed lab
    at91sam9m10g45ek: 1 failed lab
    at91sam9x25ek: 1 failed lab
    at91sam9x35ek: 1 failed lab

@khilman
Copy link
Contributor

khilman commented Jul 7, 2016

Wouldn't a more scalable solution be to just not build the DTs for these boards when it's V4 only?

I see mach-at91/Kconfig alrady has SOC_SAM_V7 and SOC_SAM_V4_V5, and those are already used in arch/arm/boot/dts/Makefile.

IMO, that approach should be expanded so that the DT files are not created.

In kernel CI, if a DT doesn't exist for a given build, it will not (cannot) be boot tested, so that will also fix this problem, but in a way that scales much better than having to tweak blacklists whenever new boards are added.

@alexandrebelloni
Copy link
Contributor Author

Yeah, this is doable, I'll send a patch.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants