On 29/03/2022 9:50 am, Nicolas Ferre wrote:
Ansuel, All,
On 28/03/2022 at 10:55, Daniel Palmer wrote:
Hi Ansuel
On Mon, 28 Mar 2022 at 09:09, Ansuel Smith <ansuelsmth@xxxxxxxxx> wrote:
Hi,
as the title say, the intention of this ""series"" is to finally
categorize
the ARM dts directory in subdirectory for each oem.
While I agree with this change and think it's for the good (browsing
the ARM dts directory at the moment is frustrating..) I think
buildroot and others need to be told about this as it'll potentially
break their kernel build scripting for ARM and probably messes up the
configs they have for existing boards.
This aspect mustn't be underestimated and I anticipate lots of issues
during a long time on this particular topic of "build systems".
Another aspect is CI and public or private testing farms we all have
running.
Yet another is if this affects what `make dtbs_install` does (I don't
know for sure, but I'd be inclined to suspect it might). Some distros
use that to deliver the DTBs as part of their kernel package, so if
paths suddenly change it could break end users' bootloader setups too.
Thanks,
Robin.
These aspects always refrained me to change anything in the naming
scheme of our DT files, but if we go in this direction, we must really
be prepared and I'm still not convince it's worth it...
If this has to happen, I would also like to queue some file name changes
to do all modifications in one go in order to lower the annoyance level
of those who would need to adapt to those changes.
BTW, is there a common scheme for dts/dtsi file naming? Is it more
enforced in one way or another for arm64 in a sense that I can take some
norm as an example?
[..]
Best regards,
Nicolas
