__local_fixups__ format

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Hi,

I'm working on using libfdt's overlay support in bootloaders on
FreeBSD. I find that our BSD-licensed dtc(1) currently generates a
/__local_fixups__ node that matches the format (roughly, with some
slight bugs that I need to address) of /__fixups__; i.e. a bunch of
properties whose values are "path:name:offset".

I've not found any documentation on what is actually valid here, but I
do know that libfdt will not accept this. Is this completely invalid
and our BSD-licensed dtc(1) should write /__local_fixups__
differently? If not, Is it OK enough that a patch would be welcome to
support this in libfdt? I like the consistency myself, for what it's
worth.

Thanks,

Kyle Evans
--
To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Device Tree]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux