On Fri, Jan 20, 2017 at 8:51 PM, Simon Glass <s...@chromium.org> wrote: > Hi, > > On 17 January 2017 at 08:50, Emmanuel Vadot <m...@bidouilliste.com> wrote: >> Add kconfig file to enable API support >> >> Signed-off-by: Emmanuel Vadot <m...@bidouilliste.com> >> --- >> Kconfig | 2 ++ >> api/Kconfig | 9 +++++++++ >> 2 files changed, 11 insertions(+) >> create mode 100644 api/Kconfig >> >> diff --git a/Kconfig b/Kconfig >> index 39a4d938d8..6a93d8820f 100644 >> --- a/Kconfig >> +++ b/Kconfig >> @@ -306,6 +306,8 @@ config ARCH_FIXUP_FDT_MEMORY >> >> endmenu # Boot images >> >> +source "api/Kconfig" >> + >> source "common/Kconfig" >> >> source "cmd/Kconfig" >> diff --git a/api/Kconfig b/api/Kconfig >> new file mode 100644 >> index 0000000000..88b4f6c4e5 >> --- /dev/null >> +++ b/api/Kconfig >> @@ -0,0 +1,9 @@ >> +menu "API" >> + >> +config API >> + bool "Enable U-Boot API" >> + default n >> + help >> + This option enable the U-Boot API. > > Can you add a little detail about what the API is and what it is for?
You can find complete documentation in the api directory. In brief, it allows the loaded binary to call back into the loader to do generic things like send network packets or read blocks from mass storage. > Also, are you going to migrate all boards to use Kconfig for this > option and drop it from the whitelist? I'll leave that to Emmanuel. Warner >> + >> +endmenu >> -- >> 2.11.0 >> > > Regards, > Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
