Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • stable
  • extraversion
  • early-display
  • variant-emmc-nvme-boot
  • 2024-07-19
  • 2024-06-30
  • 2023-10-18
  • 2023-10-10
  • 2023-07-04
  • 2023-01-25
  • v3
  • variant-emmc-nvme-boot
  • 2020-06-01
14 results
Search by author
  • Any Author
  • bnys bnys brendannystedt
  • buckket buckket buckket
  • Chris Hofstaedtler Chris Hofstaedtler zeha
  • Johannes Schauer Marin Rodrigues Johannes Schauer Marin Rodrigues josch
  • J W J W JulianWgs
  • minute minute mntmn
  • Nano Nano NanoCodeBug
  • neauoire neauoire hundredrabbits
  • plom plom heller
9 authors
  1. Sep 27, 2017
  3. Sep 24, 2017
  5. Sep 12, 2017
  7. Sep 08, 2017
    • Marek Vasut's avatar
      ARM: rmobile: Disable CONFIG_ARCH_FIXUP_FDT_MEMORY · 25f840d7
      Marek Vasut authored 
      
Disable CONFIG_ARCH_FIXUP_FDT_MEMORY to prevent U-Boot from modifying
the memory {} nodes in the DT passed to the Linux kernel. The R8A779x
DT contains multiple memory {} nodes, while U-Boot only modifies the
first one and stuffs all the memory entries into it, which is wrong.
Disabling CONFIG_ARCH_FIXUP_FDT_MEMORY is the least intrusive way to
fix the issue this close to the release, while the real fix is to
extend the fdt_fixup_memory_banks() to handle multiple memory nodes
in DT.

Signed-off-by: default avatarMarek Vasut <marek.vasut+renesas@gmail.com>
Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      25f840d7
  9. Aug 25, 2017
  11. Aug 16, 2017
    • Simon Glass's avatar
      env: Convert CONFIG_ENV_IS_IN... to a choice · c1c3fe23
      Simon Glass authored 
      
At present we support multiple environment drivers but there is not way to
select between them at run time. Also settings related to the position and
size of the environment area are global (i.e. apply to all locations).

Until these limitations are removed we cannot really support more than one
environment location. Adjust the location to be a choice so that only one
can be selected. By default the environment is 'nowhere', meaning that the
environment exists only in memory and cannot be saved.

Also expand the help for the 'nowhere' option and move it to the top since
it is the default.

Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
[trini: Move all of the imply logic to default X if Y so it works again]
Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      c1c3fe23
  13. Aug 14, 2017
  15. Aug 02, 2017
  17. Jul 26, 2017
    • Simon Glass's avatar
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass authored 
      
This converts the following to Kconfig:
   CONFIG_ENV_IS_IN_MMC
   CONFIG_ENV_IS_IN_NAND
   CONFIG_ENV_IS_IN_UBI
   CONFIG_ENV_IS_NOWHERE

In fact this already exists for sunxi as a 'choice' config. However not
all the choices are available in Kconfig yet so we cannot use that. It
would lead to more than one option being set.

In addition, one purpose of this series is to allow the environment to be
stored in more than one place. So the existing choice is converted to a
normal config allowing each option to be set independently.

There are not many opportunities for Kconfig updates to reduce the size of
this patch. This was tested with

   ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC

And then manual updates.  This is because for CHAIN_OF_TRUST boards they
can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
now.

Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      2be29653
  19. Jun 20, 2017
  21. Jun 19, 2017
  23. Jun 03, 2017
  25. May 21, 2017
  27. Apr 08, 2017
  29. Mar 13, 2017
  31. Jan 28, 2017
  33. Dec 29, 2016
    • Masahiro Yamada's avatar
      mmc: complete unfinished move of CONFIG_MMC · c2726995
      Masahiro Yamada authored 
      
Commit 7a777f6d ("mmc: Add generic Kconfig option") created
a Kconfig entry for this option without any actual moves, then
commit 44c79879 ("sunxi: Use Kconfig CONFIG_MMC") moved
instances only for SUNXI.

We generally do not like such partial moves.  This kind of work
is automated by tools/moveconfig.py, so it is pretty easy to
complete this move.

I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
This shortens the configs and will ease new board porting.

This commit was created as follows:

[1] Edit Kconfig (remove the "depends on", add the "default",
    copy the prompt and help message from Linux)

[2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'

Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: default avatarJaehoon Chung <jh80.chung@samsung.com>
      c2726995
  35. Sep 09, 2016
  37. Aug 17, 2016