Thread (1 message) 1 message, 1 author, 2018-12-06

Re: Moving ARM dts files

From: Olof Johansson <hidden>
Date: 2018-12-06 20:49:42
Also in: linux-devicetree

On Thu, Dec 6, 2018 at 12:07 PM Mark Brown [off-list ref] wrote:
On Thu, Dec 06, 2018 at 01:06:43PM -0600, Rob Herring wrote:
quoted
On Thu, Dec 6, 2018 at 7:32 AM Andreas Färber [off-list ref] wrote:
quoted
quoted
I'd be okay with distinguishing source vs. install location. Due to the
issue I mention below (and more) we can't use install_dtbs for openSUSE
and had to reimplement it, which we'd need to (and can) adjust.
quoted
What would be needed for dtbs_install to work? arm64 needs to support
a flat install? If it doesn't work for Debian or openSUSE, I'm not
sure why we have it. So I'd like to make it work.
Correct me if I'm wrong but as far as the flat vs directory thing goes
isn't the issue that this winds up being a rename for an existing 32 bit
system?  If you just install the dtbs in the default location then a
bootloader or whatever that is hard coded to look for foo-bar.dtb won't
see the new foo/foo-bar.dtb (or whatever) and will continue to use the
old binary.  It's not the fact that that it's in a directory, it's the
fact that the bootloader sees the name it needs to look for change (if
it's looking on a filesystem at all).  This isn't a problem for arm64 as
the location isn't changing, it's used directories from day one.
Yeah, install needs to remain flat even if the dts files move into
subdirectories. It will be painful for everybody if the install
location moves.
The issues with the existing install_dtbs sounded unrelated to this.
Agreed.


-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help