scripts: dtc: Build fdtoverlay
Subsystems (2)
v4 cover scripts: dtc: Build fdtoverlay
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching and building it.
While at it, also remove fdtdump.c file, which isn't used by the kernel.
V4:
- Don't fetch and build fdtdump.c
- Remove fdtdump.c
Viresh Kumar (3):
scripts: dtc: Add fdtoverlay.c to DTC_SOURCE
scripts: dtc: Build fdtoverlay tool
scripts: dtc: Remove the unused fdtdump.c file
scripts/dtc/Makefile | 6 +- scripts/dtc/fdtdump.c | 163 ------------------------------- scripts/dtc/update-dtc-source.sh | 6 +- 3 files changed, 8 insertions(+), 167 deletions(-) delete mode 100644 scripts/dtc/fdtdump.c
Signature · 1 line
2.25.0.rc1.19.g042ed3e048af
PATCH v4 1/3 scripts: dtc: Add fdtoverlay.c to DTC_SOURCE
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching it.
--- scripts/dtc/update-dtc-source.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
scripts/dtc/update-dtc-source.sh +3 -3
@@ -31,9 +31,9 @@ set -ev DTC_UPSTREAM_PATH=`pwd`/../dtc DTC_LINUX_PATH=`pwd`/scripts/dtc -DTC_SOURCE="checks.c data.c dtc.c dtc.h flattree.c fstree.c livetree.c srcpos.c \ - srcpos.h treesource.c util.c util.h version_gen.h yamltree.c \ - dtc-lexer.l dtc-parser.y" +DTC_SOURCE="checks.c data.c dtc.c dtc.h fdtoverlay.c flattree.c fstree.c \ + livetree.c srcpos.c srcpos.h treesource.c util.c \ + util.h version_gen.h yamltree.c dtc-lexer.l dtc-parser.y" LIBFDT_SOURCE="fdt.c fdt.h fdt_addresses.c fdt_empty_tree.c \ fdt_overlay.c fdt_ro.c fdt_rw.c fdt_strerror.c fdt_sw.c \ fdt_wip.c libfdt.h libfdt_env.h libfdt_internal.h"
Signature · 1 line
2.25.0.rc1.19.g042ed3e048af
PATCH v4 2/3 scripts: dtc: Build fdtoverlay tool
In reply to Viresh KumarWe will start building overlays for platforms soon in the kernel and would need fdtoverlay going forward. Lets start building it.
The fdtoverlay program applies (or merges) one ore more overlay dtb blobs to a base dtb blob. The kernel build system would later use fdtoverlay to generate the overlaid blobs based on platform specific configurations.
--- scripts/dtc/Makefile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
scripts/dtc/Makefile +5 -1
@@ -1,13 +1,17 @@ # SPDX-License-Identifier: GPL-2.0 # scripts/dtc makefile -hostprogs-always-$(CONFIG_DTC) += dtc +hostprogs-always-$(CONFIG_DTC) += dtc fdtoverlay hostprogs-always-$(CHECK_DT_BINDING) += dtc dtc-objs := dtc.o flattree.o fstree.o data.o livetree.o treesource.o \ srcpos.o checks.o util.o dtc-objs += dtc-lexer.lex.o dtc-parser.tab.o +libfdt-objs := fdt.o fdt_ro.o fdt_wip.o fdt_sw.o fdt_rw.o fdt_strerror.o fdt_empty_tree.o fdt_addresses.o fdt_overlay.o +libfdt = $(addprefix libfdt/,$(libfdt-objs)) +fdtoverlay-objs := $(libfdt) fdtoverlay.o util.o + # Source files need to get at the userspace version of libfdt_env.h to compile HOST_EXTRACFLAGS += -I $(srctree)/$(src)/libfdt
Signature · 1 line
2.25.0.rc1.19.g042ed3e048af
PATCH v4 3/3 scripts: dtc: Remove the unused fdtdump.c file
In reply to Viresh KumarThis was copied from external DTC repository long back and isn't used anymore. Over that the dtc tool can be used to generate the dts source back from the dtb. Remove the unused fdtdump.c file.
--- scripts/dtc/fdtdump.c | 163 ------------------------------------------ 1 file changed, 163 deletions(-) delete mode 100644 scripts/dtc/fdtdump.c
scripts/dtc/fdtdump.c deleted +0 -163
@@ -1,163 +0,0 @@ -// SPDX-License-Identifier: GPL-2.0 -/* -* fdtdump.c - Contributed by Pantelis Antoniou <pantelis.antoniou AT gmail.com> -*/ - -#include <stdint.h> -#include <stdio.h> -#include <stdlib.h> -#include <string.h> -#include <ctype.h> - -#include <fdt.h> -#include <libfdt_env.h> - -#include "util.h" - -#define ALIGN (x, a) (((x) + ((a) - 1)) & ~((a) - 1)) -#define PALIGN (p, a) ((void *)(ALIGN((unsigned long)(p), (a)))) -#define GET_CELL (p) (p += 4, *((const uint32_t *)(p-4))) - -static void print_data (const char *data,int len) -{ -int i; -const char *p = data; - -/* no data, don't print */ -if (len ==0 ) -return ; - -if (util_is_printable_string (data, len)) { -printf (" = \"%s\"" , (const char *)data); - }else if ((len %4 ) ==0 ) { -printf (" = <" ); -for (i =0 ; i < len; i +=4 ) -printf ("0x%08x%s" ,fdt32_to_cpu (GET_CELL (p)), - i < (len -4 ) ?" " :"" ); -printf (">" ); - }else { -printf (" = [" ); -for (i =0 ; i < len; i++) -printf ("%02x%s" , *p++, i < len -1 ?" " :"" ); -printf ("]" ); - } -} - -static void dump_blob (void *blob) -{ -struct fdt_header *bph = blob; -uint32_t off_mem_rsvmap =fdt32_to_cpu (bph->off_mem_rsvmap); -uint32_t off_dt =fdt32_to_cpu (bph->off_dt_struct); -uint32_t off_str =fdt32_to_cpu (bph->off_dt_strings); -struct fdt_reserve_entry *p_rsvmap = - (struct fdt_reserve_entry *)((char *)blob + off_mem_rsvmap); -const char *p_struct = (const char *)blob + off_dt; -const char *p_strings = (const char *)blob + off_str; -uint32_t version =fdt32_to_cpu (bph->version); -uint32_t totalsize =fdt32_to_cpu (bph->totalsize); -uint32_t tag; -const char *p, *s, *t; -int depth, sz, shift; -int i; -uint64_t addr, size; - - depth =0 ; - shift =4 ; - -printf ("/dts-v1/;\n" ); -printf ("// magic:\t\t0x%x\n" ,fdt32_to_cpu (bph->magic)); -printf ("// totalsize:\t\t0x%x (%d)\n" , totalsize, totalsize); -printf ("// off_dt_struct:\t0x%x\n" , off_dt); -printf ("// off_dt_strings:\t0x%x\n" , off_str); -printf ("// off_mem_rsvmap:\t0x%x\n" , off_mem_rsvmap); -printf ("// version:\t\t%d\n" , version); -printf ("// last_comp_version:\t%d\n" , -fdt32_to_cpu (bph->last_comp_version)); -if (version >=2 ) -printf ("// boot_cpuid_phys:\t0x%x\n" , -fdt32_to_cpu (bph->boot_cpuid_phys)); - -if (version >=3 ) -printf ("// size_dt_strings:\t0x%x\n" , -fdt32_to_cpu (bph->size_dt_strings)); -if (version >=17 ) -printf ("// size_dt_struct:\t0x%x\n" , -fdt32_to_cpu (bph->size_dt_struct)); -printf ("\n" ); - -for (i =0 ; ; i++) { - addr =fdt64_to_cpu (p_rsvmap[i].address); - size =fdt64_to_cpu (p_rsvmap[i].size); -if (addr ==0 && size ==0 ) -break ; - -printf ("/memreserve/ %llx %llx;\n" , - (unsigned long long )addr, (unsigned long long )size); - } - - p = p_struct; -while ((tag =fdt32_to_cpu (GET_CELL (p))) !=FDT_END ) { - -/* printf("tag: 0x%08x (%d)\n", tag, p - p_struct); */ - -if (tag ==FDT_BEGIN_NODE ) { - s = p; - p =PALIGN (p +strlen (s) +1 ,4 ); - -if (*s =='\0' ) - s ="/" ; - -printf ("%*s%s {\n" , depth * shift,"" , s); - - depth++; -continue ; - } - -if (tag ==FDT_END_NODE ) { - depth--; - -printf ("%*s};\n" , depth * shift,"" ); -continue ; - } - -if (tag ==FDT_NOP ) { -printf ("%*s// [NOP]\n" , depth * shift,"" ); -continue ; - } - -if (tag !=FDT_PROP ) { -fprintf (stderr,"%*s ** Unknown tag 0x%08x\n" , depth * shift,"" , tag); -break ; - } - sz =fdt32_to_cpu (GET_CELL (p)); - s = p_strings +fdt32_to_cpu (GET_CELL (p)); -if (version <16 && sz >=8 ) - p =PALIGN (p,8 ); - t = p; - - p =PALIGN (p + sz,4 ); - -printf ("%*s%s" , depth * shift,"" , s); -print_data (t, sz); -printf (";\n" ); - } -} - - -int main (int argc,char *argv[]) -{ -char *buf; - -if (argc <2 ) { -fprintf (stderr,"supply input filename\n" ); -return 5 ; - } - - buf =utilfdt_read (argv[1 ]); -if (buf) -dump_blob (buf); -else -return 10 ; - -return 0 ; -}
Signature · 1 line
2.25.0.rc1.19.g042ed3e048af
Re: [PATCH V4 1/3] scripts: dtc: Add fdtoverlay.c to DTC_SOURCE
In reply to Viresh KumarQuoted 16 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching it.
Signed-off-by Viresh Kumar <[email protected]>--- scripts/dtc/update-dtc-source.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)scripts/dtc/update-dtc-source.sh +0
-0@@ -31,9 +31,9 @@ set -ev DTC_UPSTREAM_PATH=`pwd`/../dtc DTC_LINUX_PATH=`pwd`/scripts/dtc
scripts/dtc/update-dtc-source.sh set -ev · line 39
Quoted 10 lines
scripts/dtc/update-dtc-source.sh +3
-3-DTC_SOURCE="checks.c data.c dtc.c dtc.h flattree.c fstree.c livetree.c srcpos.c \ - srcpos.h treesource.c util.c util.h version_gen.h yamltree.c \ - dtc-lexer.l dtc-parser.y" +DTC_SOURCE="checks.c data.c dtc.c dtc.h fdtoverlay.c flattree.c fstree.c \ + livetree.c srcpos.c srcpos.h treesource.c util.c \ + util.h version_gen.h yamltree.c dtc-lexer.l dtc-parser.y" LIBFDT_SOURCE="fdt.c fdt.h fdt_addresses.c fdt_empty_tree.c \ fdt_overlay.c fdt_ro.c fdt_rw.c fdt_strerror.c fdt_sw.c \ fdt_wip.c libfdt.h libfdt_env.h libfdt_internal.h"
I made this comment in the v2 email thread. Copying it here since v4 is the current version of the patch series.
DTC_SOURCE is for the dtc program. Please add a FDTOVERLAY_SOURCE and related use for the fdtoverlay program.
-Frank
Re: [PATCH V4 2/3] scripts: dtc: Build fdtoverlay tool
In reply to Viresh KumarHi Viresh,
I made these comments in the v2 patch series. I am copying them here since this is the current version.
Quoted 19 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay going forward. Lets start building it.
The fdtoverlay program applies (or merges) one ore more overlay dtb blobs to a base dtb blob. The kernel build system would later use fdtoverlay to generate the overlaid blobs based on platform specific configurations.
Signed-off-by Viresh Kumar <[email protected]>--- scripts/dtc/Makefile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)scripts/dtc/Makefile +0
-0@@ -1,13 +1,17 @@ # SPDX-License-Identifier: GPL-2.0
scripts/dtc/Makefile line 10
Quoted 10 lines
scripts/dtc/Makefile +1
-1# scripts/dtc makefile -hostprogs-always-$(CONFIG_DTC) += dtc +hostprogs-always-$(CONFIG_DTC) += dtc fdtoverlay hostprogs-always-$(CHECK_DT_BINDING) += dtc dtc-objs := dtc.o flattree.o fstree.o data.o livetree.o treesource.o \ srcpos.o checks.o util.o dtc-objs += dtc-lexer.lex.o dtc-parser.tab.o
# The upstream project builds libfdt as a separate library. We are choosing to
# instead directly link the libfdt object files into fdtoverly
scripts/dtc/Makefile line 17
Quoted 8 lines
scripts/dtc/Makefile +4
-0+libfdt-objs := fdt.o fdt_ro.o fdt_wip.o fdt_sw.o fdt_rw.o fdt_strerror.o fdt_empty_tree.o fdt_addresses.o fdt_overlay.o +libfdt = $(addprefix libfdt/,$(libfdt-objs)) +fdtoverlay-objs := $(libfdt) fdtoverlay.o util.o + # Source files need to get at the userspace version of libfdt_env.h to compile HOST_EXTRACFLAGS += -I $(srctree)/$(src)/libfdt
In general, I am a proponent of using shared libraries (which the upstream project builds by default) because if a security bug in the library is fixed, it is fixed for all users of the library.
In this specific case, I actually prefer the implementation that the patch provides (directly linking the library object files into fdtoverlay, which uses the library) because it is the only user of the library _and_ fdtoverlay will not inadvertently use the system wide libfdt if it happens to be installed (as it is on my system).
Any thoughts on this Rob?
-Frank
Quoted 15 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching and building it.
While at it, also remove
fdtdump.cfile, which isn't used by the kernel.V4:
- Don't fetch and buildfdtdump.c
- Removefdtdump.cViresh Kumar (3):
scripts: dtc: Addfdtoverlay.ctoDTC_SOURCE
scripts: dtc: Build fdtoverlay tool
scripts: dtc: Remove the unusedfdtdump.cfile
Quoted 6 lines
scripts/dtc/Makefile | 6 +- scripts/dtc/fdtdump.c | 163 ------------------------------- scripts/dtc/update-dtc-source.sh | 6 +- 3 files changed, 8 insertions(+), 167 deletions(-) delete mode 100644 scripts/dtc/fdtdump.c
My first inclination was to accept fdtoverlay, as is, from the upstream project.
But my experiences debugging use of fdtoverlay against the existing unittest overlay files has me very wary of accepting fdtoverlay in it's current form.
As an exmple, adding an overlay that fails to reply results in the following build messages:
linux--5.11-rc> make zImage
make[1]: Entering directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc'
GEN Makefile
CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/checksyscalls.sh
CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/atomic/check-atomics.sh
CHK include/generated/compile.h FDTOVERLAY drivers/of/unittest-data/static_test.dtb
Failed to apply 'drivers/of/unittest-data/overlay.dtb': FDT_ERR_NOTFOUND
make[4]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/drivers/of/unittest-data/Makefile:96: drivers/of/unittest-data/static_test.dtb] Error 1 make[3]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of/unittest-data] Error 2 make[2]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of] Error 2
make[1]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/Makefile:1805: drivers] Error 2
make[1]: Leaving directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc'
make: *** [Makefile:185: __sub-make] Error 2
The specific error message (copied from above) is:
Failed to apply 'drivers/of/unittest-data/overlay.dtb': FDT_ERR_NOTFOUND
which is cryptic and does not even point to the location in the overlay that is problematic. If you look at the source of fdtoverlay / libfdt, you will find that FDT_ERR_NOTFOUND may be generated in one of many places.
I do _not_ want to do a full review of fdtoverlay, but I think that it is reasonable to request enhancing fdtoverlay in the parent project to generate usable error messages before enabling fdtoverlay in the Linux kernel tree.
fdtoverlay in it's current form adds a potential maintenance burden to me (as the overlay maintainer). I now have the experience of how difficult it was to debug the use of fdtoverlay in the context of the proposed patch to use it with the devicetree unittest overlay .dtb files.
-Frank
+David.
Quoted 68 lines · Frank Rowand
Quoted 15 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching and building it.
While at it, also remove
fdtdump.cfile, which isn't used by the kernel.V4:
- Don't fetch and buildfdtdump.c
- Removefdtdump.cViresh Kumar (3):
scripts: dtc: Addfdtoverlay.ctoDTC_SOURCE
scripts: dtc: Build fdtoverlay tool
scripts: dtc: Remove the unusedfdtdump.cfileQuoted 6 lines
scripts/dtc/Makefile | 6 +- scripts/dtc/fdtdump.c | 163 ------------------------------- scripts/dtc/update-dtc-source.sh | 6 +- 3 files changed, 8 insertions(+), 167 deletions(-) delete mode 100644 scripts/dtc/fdtdump.cMy first inclination was to accept fdtoverlay, as is, from the upstream project.
But my experiences debugging use of fdtoverlay against the existing unittest overlay files has me very wary of accepting fdtoverlay in it's current form.
As an exmple, adding an overlay that fails to reply results in the following build messages:
linux--5.11-rc> make zImage make[1]: Entering directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' GEN Makefile CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/checksyscalls.sh CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/atomic/check-atomics.sh CHK include/generated/compile.h FDTOVERLAY drivers/of/unittest-data/static_test.dtb Failed to apply 'drivers/of/unittest-data/overlay.dtb': FDT_ERR_NOTFOUND make[4]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/drivers/of/unittest-data/Makefile:96: drivers/of/unittest-data/static_test.dtb] Error 1 make[3]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of/unittest-data] Error 2 make[2]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of] Error 2 make[1]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/Makefile:1805: drivers] Error 2 make[1]: Leaving directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' make: *** [Makefile:185: __sub-make] Error 2The specific error message (copied from above) is:
Failed to apply '
drivers/of/unittest-data/overlay.dtb':FDT_ERR_NOTFOUNDwhich is cryptic and does not even point to the location in the overlay that is problematic. If you look at the source of fdtoverlay / libfdt, you will find that
FDT_ERR_NOTFOUNDmay be generated in one of many places.I do _not_ want to do a full review of fdtoverlay, but I think that it is reasonable to request enhancing fdtoverlay in the parent project to generate usable error messages before enabling fdtoverlay in the Linux kernel tree.
fdtoverlay in it's current form adds a potential maintenance burden to me (as the overlay maintainer). I now have the experience of how difficult it was to debug the use of fdtoverlay in the context of the proposed patch to use it with the devicetree unittest overlay .dtb files.
-Frank
Signature · 1 line
viresh
Re: [PATCH V4 2/3] scripts: dtc: Build fdtoverlay tool
In reply to Frank RowandQuoted 53 lines · Frank Rowand
Hi Viresh,
I made these comments in the v2 patch series. I am copying them here since this is the current version.
Quoted 19 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay going forward. Lets start building it.
The fdtoverlay program applies (or merges) one ore more overlay dtb blobs to a base dtb blob. The kernel build system would later use fdtoverlay to generate the overlaid blobs based on platform specific configurations.
Signed-off-by Viresh Kumar <[email protected]>--- scripts/dtc/Makefile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)scripts/dtc/Makefile +0
-0@@ -1,13 +1,17 @@ # SPDX-License-Identifier: GPL-2.0scripts/dtc/Makefile line 10
Quoted 10 lines
scripts/dtc/Makefile +1
-1# scripts/dtc makefile -hostprogs-always-$(CONFIG_DTC) += dtc +hostprogs-always-$(CONFIG_DTC) += dtc fdtoverlay hostprogs-always-$(CHECK_DT_BINDING) += dtc dtc-objs := dtc.o flattree.o fstree.o data.o livetree.o treesource.o \ srcpos.o checks.o util.o dtc-objs += dtc-lexer.lex.o dtc-parser.tab.o# The upstream project builds libfdt as a separate library. We are choosing to
# instead directly link the libfdt object files into fdtoverlyscripts/dtc/Makefile line 17
Quoted 8 lines
scripts/dtc/Makefile +4
-0+libfdt-objs := fdt.o fdt_ro.o fdt_wip.o fdt_sw.o fdt_rw.o fdt_strerror.o fdt_empty_tree.o fdt_addresses.o fdt_overlay.o +libfdt = $(addprefix libfdt/,$(libfdt-objs)) +fdtoverlay-objs := $(libfdt) fdtoverlay.o util.o + # Source files need to get at the userspace version of libfdt_env.h to compile HOST_EXTRACFLAGS += -I $(srctree)/$(src)/libfdtIn general, I am a proponent of using shared libraries (which the upstream project builds by default) because if a security bug in the library is fixed, it is fixed for all users of the library.
Quoted 6 lines
In this specific case, I actually prefer the implementation that the patch provides (directly linking the library object files into fdtoverlay, which uses the library) because it is the only user of the library _and_ fdtoverlay will not inadvertently use the system wide libfdt if it happens to be installed (as it is on my system).
Any thoughts on this Rob?
I agree. No point in complicating the build to do a library.
Rob
Quoted 64 lines · Viresh Kumar
+David.
Quoted 61 lines · Frank Rowand
Quoted 15 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching and building it.
While at it, also remove
fdtdump.cfile, which isn't used by the kernel.V4:
- Don't fetch and buildfdtdump.c
- Removefdtdump.cViresh Kumar (3):
scripts: dtc: Addfdtoverlay.ctoDTC_SOURCE
scripts: dtc: Build fdtoverlay tool
scripts: dtc: Remove the unusedfdtdump.cfileQuoted 6 lines
scripts/dtc/Makefile | 6 +- scripts/dtc/fdtdump.c | 163 ------------------------------- scripts/dtc/update-dtc-source.sh | 6 +- 3 files changed, 8 insertions(+), 167 deletions(-) delete mode 100644 scripts/dtc/fdtdump.cMy first inclination was to accept fdtoverlay, as is, from the upstream project.
But my experiences debugging use of fdtoverlay against the existing unittest overlay files has me very wary of accepting fdtoverlay in it's current form.
As an exmple, adding an overlay that fails to reply results in the following build messages:
linux--5.11-rc> make zImage make[1]: Entering directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' GEN Makefile CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/checksyscalls.sh CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/atomic/check-atomics.sh CHK include/generated/compile.h FDTOVERLAY drivers/of/unittest-data/static_test.dtb Failed to apply 'drivers/of/unittest-data/overlay.dtb': FDT_ERR_NOTFOUND make[4]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/drivers/of/unittest-data/Makefile:96: drivers/of/unittest-data/static_test.dtb] Error 1 make[3]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of/unittest-data] Error 2 make[2]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of] Error 2 make[1]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/Makefile:1805: drivers] Error 2 make[1]: Leaving directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' make: *** [Makefile:185: __sub-make] Error 2The specific error message (copied from above) is:
Failed to apply '
drivers/of/unittest-data/overlay.dtb':FDT_ERR_NOTFOUNDwhich is cryptic and does not even point to the location in the overlay that is problematic. If you look at the source of fdtoverlay / libfdt, you will find that
FDT_ERR_NOTFOUNDmay be generated in one of many places.I do _not_ want to do a full review of fdtoverlay, but I think that it is reasonable to request enhancing fdtoverlay in the parent project to generate usable error messages before enabling fdtoverlay in the Linux kernel tree.
That's... actually much harder than it sounds. fdtoverlay is basically a trivial wrapper around the fdt_overlay_apply() function in libfdt. Matching the conventions of the rest of the library, really it's only way to report errors is a single error code.
Returning richer errors is not an easy problem in a C library, especially one designed to be usable in embedded systems, without an allocator or much else available.
Of course it would be possible to write a friendly command line tool specifically for applying overlays, which could give better errors. fdtoverlay as it stands isn't really that - it was pretty much written just to invoke fdt_overlay_apply() in testcases.
Quoted 7 lines
Quoted 6 lines
fdtoverlay in it's current form adds a potential maintenance burden to me (as the overlay maintainer). I now have the experience of how difficult it was to debug the use of fdtoverlay in the context of the proposed patch to use it with the devicetree unittest overlay .dtb files.
-Frank
Signature · 4 lines
David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Hi David,
Quoted 72 lines · David Gibson
Quoted 64 lines · Viresh Kumar
+David.
Quoted 61 lines · Frank Rowand
Quoted 15 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching and building it.
While at it, also remove
fdtdump.cfile, which isn't used by the kernel.V4:
- Don't fetch and buildfdtdump.c
- Removefdtdump.cViresh Kumar (3):
scripts: dtc: Addfdtoverlay.ctoDTC_SOURCE
scripts: dtc: Build fdtoverlay tool
scripts: dtc: Remove the unusedfdtdump.cfileQuoted 6 lines
scripts/dtc/Makefile | 6 +- scripts/dtc/fdtdump.c | 163 ------------------------------- scripts/dtc/update-dtc-source.sh | 6 +- 3 files changed, 8 insertions(+), 167 deletions(-) delete mode 100644 scripts/dtc/fdtdump.cMy first inclination was to accept fdtoverlay, as is, from the upstream project.
But my experiences debugging use of fdtoverlay against the existing unittest overlay files has me very wary of accepting fdtoverlay in it's current form.
As an exmple, adding an overlay that fails to reply results in the following build messages:
linux--5.11-rc> make zImage make[1]: Entering directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' GEN Makefile CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/checksyscalls.sh CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/atomic/check-atomics.sh CHK include/generated/compile.h FDTOVERLAY drivers/of/unittest-data/static_test.dtb Failed to apply 'drivers/of/unittest-data/overlay.dtb': FDT_ERR_NOTFOUND make[4]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/drivers/of/unittest-data/Makefile:96: drivers/of/unittest-data/static_test.dtb] Error 1 make[3]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of/unittest-data] Error 2 make[2]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of] Error 2 make[1]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/Makefile:1805: drivers] Error 2 make[1]: Leaving directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' make: *** [Makefile:185: __sub-make] Error 2The specific error message (copied from above) is:
Failed to apply '
drivers/of/unittest-data/overlay.dtb':FDT_ERR_NOTFOUNDwhich is cryptic and does not even point to the location in the overlay that is problematic. If you look at the source of fdtoverlay / libfdt, you will find that
FDT_ERR_NOTFOUNDmay be generated in one of many places.I do _not_ want to do a full review of fdtoverlay, but I think that it is reasonable to request enhancing fdtoverlay in the parent project to generate usable error messages before enabling fdtoverlay in the Linux kernel tree.
That's... actually much harder than it sounds. fdtoverlay is basically a trivial wrapper around the
fdt_overlay_apply()function in libfdt. Matching the conventions of the rest of the library, really it's only way to report errors is a single error code.
Quoted 8 lines
Returning richer errors is not an easy problem in a C library, especially one designed to be usable in embedded systems, without an allocator or much else available.
Of course it would be possible to write a friendly command line tool specifically for applying overlays, which could give better errors. fdtoverlay as it stands isn't really that - it was pretty much written just to invoke
fdt_overlay_apply()in testcases.
Thank you for providing that context.
I do not know if there is a way to enable the code that is currently in libfdt to both be useful as an embedded library (for example, U-boot seems to often have a need to keep memory usage very small) and also be part of a tool with effective warning and error messages.
Before having looked at libfdt only at a cursory level while debugging the proposed use of fdtoverlay in Linux, my first thought was that maybe it would be possible to add warning and error messages within "#ifdef" blocks, or other ways that cause the error code to _not_ be compiled as part of library version of libfdt, but only be compiled as part of fdtoverlay _when built in the Linux kernel_ (noting that the proposed Linux patch builds the libfdt files as part of the fdtoverlay compile instead of as a discrete library). After looking at the libfdt source a tiny bit more carefully, I would probably shoot down this suggestion, as it makes the source code uglier and harder to understand and maintain for the primary purpose of being an embedded library.
Do you have any thoughts on how warning and error messages could be added, or if it is even possible? Or maybe your suggestion of writing a "friendly command line tool specifically for applying overlays" is the path that Viresh should pursue?
-Frank
Quoted 9 lines
Quoted 8 lines
Quoted 7 lines
fdtoverlay in it's current form adds a potential maintenance burden to me (as the overlay maintainer). I now have the experience of how difficult it was to debug the use of fdtoverlay in the context of the proposed patch to use it with the devicetree unittest overlay .dtb files.
-Frank
Quoted 84 lines · Frank Rowand
Hi David,
Quoted 72 lines · David Gibson
Quoted 64 lines · Viresh Kumar
+David.
Quoted 61 lines · Frank Rowand
Quoted 15 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching and building it.
While at it, also remove
fdtdump.cfile, which isn't used by the kernel.V4:
- Don't fetch and buildfdtdump.c
- Removefdtdump.cViresh Kumar (3):
scripts: dtc: Addfdtoverlay.ctoDTC_SOURCE
scripts: dtc: Build fdtoverlay tool
scripts: dtc: Remove the unusedfdtdump.cfileQuoted 6 lines
scripts/dtc/Makefile | 6 +- scripts/dtc/fdtdump.c | 163 ------------------------------- scripts/dtc/update-dtc-source.sh | 6 +- 3 files changed, 8 insertions(+), 167 deletions(-) delete mode 100644 scripts/dtc/fdtdump.cMy first inclination was to accept fdtoverlay, as is, from the upstream project.
But my experiences debugging use of fdtoverlay against the existing unittest overlay files has me very wary of accepting fdtoverlay in it's current form.
As an exmple, adding an overlay that fails to reply results in the following build messages:
linux--5.11-rc> make zImage make[1]: Entering directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' GEN Makefile CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/checksyscalls.sh CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/atomic/check-atomics.sh CHK include/generated/compile.h FDTOVERLAY drivers/of/unittest-data/static_test.dtb Failed to apply 'drivers/of/unittest-data/overlay.dtb': FDT_ERR_NOTFOUND make[4]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/drivers/of/unittest-data/Makefile:96: drivers/of/unittest-data/static_test.dtb] Error 1 make[3]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of/unittest-data] Error 2 make[2]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of] Error 2 make[1]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/Makefile:1805: drivers] Error 2 make[1]: Leaving directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' make: *** [Makefile:185: __sub-make] Error 2The specific error message (copied from above) is:
Failed to apply '
drivers/of/unittest-data/overlay.dtb':FDT_ERR_NOTFOUNDwhich is cryptic and does not even point to the location in the overlay that is problematic. If you look at the source of fdtoverlay / libfdt, you will find that
FDT_ERR_NOTFOUNDmay be generated in one of many places.I do _not_ want to do a full review of fdtoverlay, but I think that it is reasonable to request enhancing fdtoverlay in the parent project to generate usable error messages before enabling fdtoverlay in the Linux kernel tree.
That's... actually much harder than it sounds. fdtoverlay is basically a trivial wrapper around the
fdt_overlay_apply()function in libfdt. Matching the conventions of the rest of the library, really it's only way to report errors is a single error code.Quoted 8 lines
Returning richer errors is not an easy problem in a C library, especially one designed to be usable in embedded systems, without an allocator or much else available.
Of course it would be possible to write a friendly command line tool specifically for applying overlays, which could give better errors. fdtoverlay as it stands isn't really that - it was pretty much written just to invoke
fdt_overlay_apply()in testcases.
Quoted 6 lines
Thank you for providing that context.
I do not know if there is a way to enable the code that is currently in libfdt to both be useful as an embedded library (for example, U-boot seems to often have a need to keep memory usage very small) and also be part of a tool with effective warning and error messages.
Yeah, I don't know either.
Quoted 10 lines
Before having looked at libfdt only at a cursory level while debugging the proposed use of fdtoverlay in Linux, my first thought was that maybe it would be possible to add warning and error messages within "#ifdef" blocks, or other ways that cause the error code to _not_ be compiled as part of library version of libfdt, but only be compiled as part of fdtoverlay
_whenbuilt in the Linuxkernel_(noting that the proposed Linux patch builds the libfdt files as part of the fdtoverlay compile instead of as a discrete library). After looking at the libfdt source a tiny bit more carefully, I would probably shoot down this suggestion, as it makes the source code uglier and harder to understand and maintain for the primary purpose of being an embedded library.
Oof. That sounds really ugly, but maybe it could be pulled off.
Quoted 4 lines
Do you have any thoughts on how warning and error messages could be added, or if it is even possible? Or maybe your suggestion of writing a "friendly command line tool specifically for applying overlays" is the path that Viresh should pursue?
I think at this stage it's a matter of trying a few approaches and seeing what works out.
Signature · 4 lines
David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Quoted 12 lines · David Gibson
Quoted 10 lines · Frank Rowand
Before having looked at libfdt only at a cursory level while debugging the proposed use of fdtoverlay in Linux, my first thought was that maybe it would be possible to add warning and error messages within "#ifdef" blocks, or other ways that cause the error code to _not_ be compiled as part of library version of libfdt, but only be compiled as part of fdtoverlay
_whenbuilt in the Linuxkernel_(noting that the proposed Linux patch builds the libfdt files as part of the fdtoverlay compile instead of as a discrete library). After looking at the libfdt source a tiny bit more carefully, I would probably shoot down this suggestion, as it makes the source code uglier and harder to understand and maintain for the primary purpose of being an embedded library.
Quoted 1 line
Oof. That sounds really ugly, but maybe it could be pulled off.
I started looking at this and I was able to get to a not so ugly solution.
Do this in dtc:
-------------------------8<-------------------------
--- dtc.h | 6 ++++++ fdtoverlay.c | 2 ++ 2 files changed, 8 insertions(+)
dtc.h +6 -0
@@ -29,6 +29,12 @@#define debug (...)#endif +#ifdef VERBOSE +#define pr_err (...) fprintf(stderr, __VA_ARGS__) +#else +#define pr_err (...) +#endif +#define DEFAULT_FDT_VERSION 17/*
fdtoverlay.c +2 -0
@@ -16,6 +16,7 @@#include <libfdt.h> +#include "dtc.h" #include "util.h" #define BUF_INCREMENT 65536
@@ -76,6 +77,7 @@ static void *apply_one(char *base, const char *overlay, size_t *buf_len,if (ret) {fprintf (stderr,"\nFailed to apply '%s': %s\n" , name,fdt_strerror (ret)); +pr_err ("New error\n" ); goto fail; }
-------------------------8<------------------------- And do this in kernel:
-------------------------8<-------------------------
scripts/dtc/Makefile +1 -0
@@ -13,6 +13,7 @@ dtc-objs += dtc-lexer.lex.o dtc-parser.tab.o libfdt-objs := fdt.o fdt_ro.o fdt_wip.o fdt_sw.o fdt_rw.o fdt_strerror.o fdt_empty_tree.o fdt_addresses.o fdt_overlay.o libfdt = $(addprefix libfdt/,$(libfdt-objs)) fdtoverlay-objs := $(libfdt) fdtoverlay.o util.o +HOSTCFLAGS_fdtoverlay.o := -DVERBOSE # Source files need to get at the userspace version of libfdt_env.h to compile HOST_EXTRACFLAGS += -I $(srctree)/$(src)/libfdt
-------------------------8<-------------------------
Will that be acceptable ? With this we can add as many error messages to libfdt without affecting any other users of it other than Linux.
Signature · 1 line
viresh
Quoted 108 lines · David Gibson
Quoted 84 lines · Frank Rowand
Hi David,
Quoted 72 lines · David Gibson
Quoted 64 lines · Viresh Kumar
+David.
Quoted 61 lines · Frank Rowand
Quoted 15 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching and building it.
While at it, also remove
fdtdump.cfile, which isn't used by the kernel.V4:
- Don't fetch and buildfdtdump.c
- Removefdtdump.cViresh Kumar (3):
scripts: dtc: Addfdtoverlay.ctoDTC_SOURCE
scripts: dtc: Build fdtoverlay tool
scripts: dtc: Remove the unusedfdtdump.cfileQuoted 6 lines
scripts/dtc/Makefile | 6 +- scripts/dtc/fdtdump.c | 163 ------------------------------- scripts/dtc/update-dtc-source.sh | 6 +- 3 files changed, 8 insertions(+), 167 deletions(-) delete mode 100644 scripts/dtc/fdtdump.cMy first inclination was to accept fdtoverlay, as is, from the upstream project.
But my experiences debugging use of fdtoverlay against the existing unittest overlay files has me very wary of accepting fdtoverlay in it's current form.
As an exmple, adding an overlay that fails to reply results in the following build messages:
linux--5.11-rc> make zImage make[1]: Entering directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' GEN Makefile CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/checksyscalls.sh CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/atomic/check-atomics.sh CHK include/generated/compile.h FDTOVERLAY drivers/of/unittest-data/static_test.dtb Failed to apply 'drivers/of/unittest-data/overlay.dtb': FDT_ERR_NOTFOUND make[4]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/drivers/of/unittest-data/Makefile:96: drivers/of/unittest-data/static_test.dtb] Error 1 make[3]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of/unittest-data] Error 2 make[2]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of] Error 2 make[1]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/Makefile:1805: drivers] Error 2 make[1]: Leaving directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' make: *** [Makefile:185: __sub-make] Error 2The specific error message (copied from above) is:
Failed to apply '
drivers/of/unittest-data/overlay.dtb':FDT_ERR_NOTFOUNDwhich is cryptic and does not even point to the location in the overlay that is problematic. If you look at the source of fdtoverlay / libfdt, you will find that
FDT_ERR_NOTFOUNDmay be generated in one of many places.I do _not_ want to do a full review of fdtoverlay, but I think that it is reasonable to request enhancing fdtoverlay in the parent project to generate usable error messages before enabling fdtoverlay in the Linux kernel tree.
That's... actually much harder than it sounds. fdtoverlay is basically a trivial wrapper around the
fdt_overlay_apply()function in libfdt. Matching the conventions of the rest of the library, really it's only way to report errors is a single error code.Quoted 8 lines
Returning richer errors is not an easy problem in a C library, especially one designed to be usable in embedded systems, without an allocator or much else available.
Of course it would be possible to write a friendly command line tool specifically for applying overlays, which could give better errors. fdtoverlay as it stands isn't really that - it was pretty much written just to invoke
fdt_overlay_apply()in testcases.Quoted 6 lines
Thank you for providing that context.
I do not know if there is a way to enable the code that is currently in libfdt to both be useful as an embedded library (for example, U-boot seems to often have a need to keep memory usage very small) and also be part of a tool with effective warning and error messages.
Yeah, I don't know either.
Quoted 10 lines
Before having looked at libfdt only at a cursory level while debugging the proposed use of fdtoverlay in Linux, my first thought was that maybe it would be possible to add warning and error messages within "#ifdef" blocks, or other ways that cause the error code to _not_ be compiled as part of library version of libfdt, but only be compiled as part of fdtoverlay
_whenbuilt in the Linuxkernel_(noting that the proposed Linux patch builds the libfdt files as part of the fdtoverlay compile instead of as a discrete library). After looking at the libfdt source a tiny bit more carefully, I would probably shoot down this suggestion, as it makes the source code uglier and harder to understand and maintain for the primary purpose of being an embedded library.Oof. That sounds really ugly, but maybe it could be pulled off.
Quoted 7 lines
Quoted 4 lines
Do you have any thoughts on how warning and error messages could be added, or if it is even possible? Or maybe your suggestion of writing a "friendly command line tool specifically for applying overlays" is the path that Viresh should pursue?
I think at this stage it's a matter of trying a few approaches and seeing what works out.
Another way would be applying overlays to dtc's live tree. This could apply overlays from dts in addition to dtb. It could be a plug-in if we ever get that finished up.
The downside of this is not testing libfdt's code and possible differences between 2 implementations.
Rob
Quoted 115 lines · Rob Herring
Quoted 113 lines · David Gibson
Quoted 84 lines · Frank Rowand
Hi David,
Quoted 72 lines · David Gibson
Quoted 64 lines · Viresh Kumar
+David.
Quoted 61 lines · Frank Rowand
Quoted 15 lines · Viresh Kumar
We will start building overlays for platforms soon in the kernel and would need fdtoverlay tool going forward. Lets start fetching and building it.
While at it, also remove
fdtdump.cfile, which isn't used by the kernel.V4:
- Don't fetch and buildfdtdump.c
- Removefdtdump.cViresh Kumar (3):
scripts: dtc: Addfdtoverlay.ctoDTC_SOURCE
scripts: dtc: Build fdtoverlay tool
scripts: dtc: Remove the unusedfdtdump.cfileQuoted 6 lines
scripts/dtc/Makefile | 6 +- scripts/dtc/fdtdump.c | 163 ------------------------------- scripts/dtc/update-dtc-source.sh | 6 +- 3 files changed, 8 insertions(+), 167 deletions(-) delete mode 100644 scripts/dtc/fdtdump.cMy first inclination was to accept fdtoverlay, as is, from the upstream project.
But my experiences debugging use of fdtoverlay against the existing unittest overlay files has me very wary of accepting fdtoverlay in it's current form.
As an exmple, adding an overlay that fails to reply results in the following build messages:
linux--5.11-rc> make zImage make[1]: Entering directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' GEN Makefile CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/checksyscalls.sh CALL /local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/atomic/check-atomics.sh CHK include/generated/compile.h FDTOVERLAY drivers/of/unittest-data/static_test.dtb Failed to apply 'drivers/of/unittest-data/overlay.dtb': FDT_ERR_NOTFOUND make[4]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/drivers/of/unittest-data/Makefile:96: drivers/of/unittest-data/static_test.dtb] Error 1 make[3]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of/unittest-data] Error 2 make[2]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/scripts/Makefile.build:496: drivers/of] Error 2 make[1]: *** [/local/frowand_nobackup/src/git_linus/linux--5.11-rc/Makefile:1805: drivers] Error 2 make[1]: Leaving directory '/local/frowand_nobackup/src/git_linus/build/dragon_linus_5.11-rc' make: *** [Makefile:185: __sub-make] Error 2The specific error message (copied from above) is:
Failed to apply '
drivers/of/unittest-data/overlay.dtb':FDT_ERR_NOTFOUNDwhich is cryptic and does not even point to the location in the overlay that is problematic. If you look at the source of fdtoverlay / libfdt, you will find that
FDT_ERR_NOTFOUNDmay be generated in one of many places.I do _not_ want to do a full review of fdtoverlay, but I think that it is reasonable to request enhancing fdtoverlay in the parent project to generate usable error messages before enabling fdtoverlay in the Linux kernel tree.
That's... actually much harder than it sounds. fdtoverlay is basically a trivial wrapper around the
fdt_overlay_apply()function in libfdt. Matching the conventions of the rest of the library, really it's only way to report errors is a single error code.Quoted 8 lines
Returning richer errors is not an easy problem in a C library, especially one designed to be usable in embedded systems, without an allocator or much else available.
Of course it would be possible to write a friendly command line tool specifically for applying overlays, which could give better errors. fdtoverlay as it stands isn't really that - it was pretty much written just to invoke
fdt_overlay_apply()in testcases.Quoted 6 lines
Thank you for providing that context.
I do not know if there is a way to enable the code that is currently in libfdt to both be useful as an embedded library (for example, U-boot seems to often have a need to keep memory usage very small) and also be part of a tool with effective warning and error messages.
Yeah, I don't know either.
Quoted 10 lines
Before having looked at libfdt only at a cursory level while debugging the proposed use of fdtoverlay in Linux, my first thought was that maybe it would be possible to add warning and error messages within "#ifdef" blocks, or other ways that cause the error code to _not_ be compiled as part of library version of libfdt, but only be compiled as part of fdtoverlay
_whenbuilt in the Linuxkernel_(noting that the proposed Linux patch builds the libfdt files as part of the fdtoverlay compile instead of as a discrete library). After looking at the libfdt source a tiny bit more carefully, I would probably shoot down this suggestion, as it makes the source code uglier and harder to understand and maintain for the primary purpose of being an embedded library.Oof. That sounds really ugly, but maybe it could be pulled off.
Quoted 4 lines
Do you have any thoughts on how warning and error messages could be added, or if it is even possible? Or maybe your suggestion of writing a "friendly command line tool specifically for applying overlays" is the path that Viresh should pursue?
Quoted 6 lines
Quoted 2 lines
I think at this stage it's a matter of trying a few approaches and seeing what works out.
Another way would be applying overlays to dtc's live tree. This could apply overlays from dts in addition to dtb. It could be a plug-in if we ever get that finished up.
This is actually a really interesting idea, because in a sense dtc already *does* apply overlays. It's just that it effectively resolves as it is parsing, rather than realizing separate overlay objects then merging as a separate step.
I would actually like to change that, so that it *does* explicitly produce a chain of overlays internally. That has advantages for the checking code, because some checks make sense to apply to individual overlay fragments, but some only make sense on a fully resolved tree.
As a bonus, it could handle this use case. Unlike libfdt, dtc is a much more normal userspace program and adding extra verbose debugging is no realy problem.
It probably is more work in the short term, though.
Quoted 2 lines
The downside of this is not testing libfdt's code and possible differences between 2 implementations.
That can be mitigated by having a bunch of examples in the testsuite where we cross compare fdtoverlay's output with dtc's.
Signature · 4 lines
David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson