Hi Tom, On Thu, 31 Aug 2023 at 08:01, Tom Rini <tr...@konsulko.com> wrote: > > On Wed, Aug 30, 2023 at 09:53:13PM -0600, Simon Glass wrote: > > Move this to be with the other devicetree-fixup options. > > > > Signed-off-by: Simon Glass <s...@chromium.org> > > --- > > > > (no changes since v1) > > > > boot/Kconfig | 16 ++++++++-------- > > 1 file changed, 8 insertions(+), 8 deletions(-) > > > > diff --git a/boot/Kconfig b/boot/Kconfig > > index 023446130282..257f4cc085e1 100644 > > --- a/boot/Kconfig > > +++ b/boot/Kconfig > > @@ -693,14 +693,6 @@ config SUPPORT_RAW_INITRD > > address of the initrd must be augmented by it's size, in the > > following > > format: "<initrd address>:<initrd size>". > > > > -config ARCH_FIXUP_FDT_MEMORY > > - bool "Enable arch_fixup_memory_banks() call" > > - default y > > - help > > - Enable FDT memory map syncup before OS boot. This feature can be > > - used for booting OS with different memory setup where the part of > > - the memory location should be used for different purpose. > > - > > config CHROMEOS > > bool "Support booting Chrome OS" > > help > > @@ -1492,6 +1484,14 @@ config FDT_SIMPLEFB > > the presence of the simple frame buffer with associated reserved > > memory > > > > +config ARCH_FIXUP_FDT_MEMORY > > + bool "Enable arch_fixup_memory_banks() call" > > + default y > > + help > > + Enable FDT memory map syncup before OS boot. This feature can be > > + used for booting OS with different memory setup where the part of > > + the memory location should be used for different purpose. > > + > > endmenu > > > > endif # OF_LIBFDT > > It seems like fixups are mixed in with other changes in this menu when > we should probably keep the fixups lumped together at least.
>From what I can tell all of the things I am putting in this menu relate to DT fixups. The naming is a bit odd though, on some of them. Regards, Simon
