Skip to content

U
U-Boot.Mirror

OS / U-Boot.Mirror

通知 1
Star 0
Fork 0
U
U-Boot.Mirror

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 30 3月, 2018 3 次提交
  3. 24 3月, 2018 2 次提交
    • P
      Convert CONFIG_UBI_SILENCE_MSG to Kconfig · c0ce4cea
      由 Petr Vorel 提交于 
      Signed-off-by: NPetr Vorel <petr.vorel@gmail.com>
      c0ce4cea
    • P
      Convert CONFIG_UBIFS_SILENCE_MSG to Kconfig · afb6fda2
      由 Petr Vorel 提交于 
      Introduce another difference from upstream (kernel) source in
fs/ubifs/super.c: adding preprocessor condition as y variable in
mount_ubifs() depends on CONFIG_UBIFS_SILENCE_MSG:
fs/ubifs/super.c:1337:15: error: variable ?y? set but not used [-Werror=unused-but-set-variable]
  long long x, y;

Not setting CONFIG_UBIFS_SILENCE_MSG in am335x_igep003x_defconfig and
igep0032_defconfig. Although it was defined in their config headers, it
depends on CMD_UBIFS which is not set for them.
Signed-off-by: NPetr Vorel <petr.vorel@gmail.com>
Cc: Joe Hershberger <joe.hershberger@ni.com>
Cc: Heiko Schocher <hs@denx.de>
      afb6fda2
  5. 23 3月, 2018 1 次提交
    • L
      scripts/check-config.sh: fix "command not found" error handling · f69dce50
      由 Luca Ceresoli 提交于 
      scripts/check-config.sh exits successfully and silently without doing
any checks when the 'comm' command is not found.

The problem triggers from the command around line 39:

  comm -23 ${suspects} ${ok} >${new_adhoc}

This statement fails when 'comm' is not in $PATH, creating an empty
${new_adhoc} file. But the script continues and the following line,
which is supposed to detect an error:

  if [ -s ${new_adhoc} ]; then

will always be false since the file is empty, and the script will exit
successfully as if everything were OK.

The case where 'comm' in not in $PATH is not theoretical. It used to
happen on yocto until a recent fix [0], and still happens on the
current stable branch (rocko).

Fix by setting the errexit flag to exit with error when a statement
fails, so that at least the problem is noticed.

For additional safety also set the nounset flag to detect expansion
errors.

[0] http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=fe0b4cb5b48580d4a3f3c0eb82bfa6f1b13801e4Signed-off-by: NLuca Ceresoli <luca@lucaceresoli.net>
Reviewed-by: NSimon Glass <sjg@chromium.org>
      f69dce50
  7. 20 3月, 2018 1 次提交
  9. 14 3月, 2018 1 次提交
    • S
      Move CONFIG_PHY_ADDR to Kconfig · b30c4190
      由 Stefan Mavrodiev 提交于 
      CONFIG_PHY_ADDR is used for old-style configuration. This makes
impossible changing the PHY address, if multiple boards share a same
config header file (for example include/configs/sunxi-common.h).

Moving this to Kconfig helps overcoming this issue. It's defined
as entry inside PHYLIB section.

After the implemention, moveconfig was run. The issues are:
	- edb9315a	- CONFIG_PHYLIB is not enabled. Entry is
			  deleted.

	- ds414		- CONFIG_PHYLIB is in incompatible format:
			  { 0x1, 0x0 }. This entry is also deleted.

	- devkit3250	- The PHY_ADDR is in hex format (0x1F).
			  Manually CONFIG_PHY_ADDR=31 is added in
			  the defconfig.

After the changes the suspicious defconfigs passes building.
Signed-off-by: NStefan Mavrodiev <stefan@olimex.com>
Acked-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
[jagan: rebased on master]
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NJagan Teki <jagan@openedev.com>
      b30c4190
  11. 10 3月, 2018 2 次提交
  13. 09 3月, 2018 3 次提交
    • T
      ARM: Drop unreferenced CONFIG_* defines named after boards · b996b7d4
      由 Tuomas Tynkkynen 提交于 
      The following config symbols are only defined once and never referenced
anywhere else:

CONFIG_AT91SAM9263EK
CONFIG_AT91SAM9RLEK
CONFIG_BARIX_IPAM390
CONFIG_BOARD_H2200
CONFIG_EP9301
CONFIG_KZM_A9_GT
CONFIG_PICOSAM
CONFIG_PLATINUM_PICON
CONFIG_PLATINUM_TITANIUM
CONFIG_PM9261
CONFIG_PM9263
CONFIG_PM9G45
CONFIG_SIEMENS_DRACO
CONFIG_SIEMENS_PXM2
CONFIG_SIEMENS_RUT
CONFIG_SMDKC100
CONFIG_SMDKV310
CONFIG_STM32F4DISCOVERY

Most of them are config symbols named after the respective boards which
seems to have been a standard practice at some point.
Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>
      b996b7d4
    • T
      ARM: Drop unreferenced CONFIG_* defines named after SoCs · 17796171
      由 Tuomas Tynkkynen 提交于 
      The following config symbols are only defined once and never referenced
anywhere else:

CONFIG_ARM926EJS
CONFIG_CPUAT91
CONFIG_EXYNOS5800
CONFIG_SYS_CORTEX_R4

Most of them are config symbols named after the respective SoCs which
seems to have been a standard practice at some point.
Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>
      17796171
    • T
      MIPS: Drop unreferenced CONFIG_* defines · c604f47a
      由 Tuomas Tynkkynen 提交于 
      The following config symbols are only defined once and never referenced
anywhere else:

CONFIG_DBAU1X00
CONFIG_PB1X00

Most of them are config symbols named after the respective boards which
seems to have been a standard practice at some point.
Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>
      c604f47a
  15. 05 3月, 2018 1 次提交
  17. 24 2月, 2018 8 次提交
  19. 23 2月, 2018 2 次提交
  21. 20 2月, 2018 1 次提交
  23. 15 2月, 2018 4 次提交
  25. 14 2月, 2018 9 次提交
  27. 09 2月, 2018 2 次提交