January 2014 - U-Boot

[U-Boot] [PATCH] cosmetic: uImage.FIT: fix documents
by Masahiro Yamada 17 Jan '14

17 Jan '14

- Fix the path to source_file_format.txt - Fix a minor typo - Fix the type for FIT blob: it must be "flat_dt" Signed-off-by: Masahiro Yamada <yamada.m(a)jp.panasonic.com> --- doc/uImage.FIT/howto.txt | 6 +++--- doc/uImage.FIT/source_file_format.txt | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/uImage.FIT/howto.txt b/doc/uImage.FIT/howto.txt index 59e21e9..526be55 100644 --- a/doc/uImage.FIT/howto.txt +++ b/doc/uImage.FIT/howto.txt @@ -20,8 +20,8 @@ www.jdl.com for its latest version. mkimage (together with dtc) takes as input an image source file, which describes the contents of the image and defines its various properties used during booting. By convention, image source file has the ".its" extension, also, the details of its format are given in -doc/source_file_format.txt. The actual data that is to be included in the -uImage (kernel, ramdisk, etc.) is specified in the image source file in the +doc/uImage.FIT/source_file_format.txt. The actual data that is to be included in +the uImage (kernel, ramdisk, etc.) is specified in the image source file in the form of paths to appropriate data files. The outcome of the image creation process is a binary file (by convention with the ".itb" extension) that contains all the referenced data (kernel, ramdisk, etc.) and other information @@ -39,7 +39,7 @@ Here's a graphical overview of the image creation and booting process: image source file mkimage + dtc transfer to target + ---------------> image file --------------------> bootm -image data files(s) +image data file(s) Example 1 -- old-style (non-FDT) kernel booting diff --git a/doc/uImage.FIT/source_file_format.txt b/doc/uImage.FIT/source_file_format.txt index 160b2d0..9ed6f65 100644 --- a/doc/uImage.FIT/source_file_format.txt +++ b/doc/uImage.FIT/source_file_format.txt @@ -159,7 +159,7 @@ the '/images' node should have the following layout: - description : Textual description of the component sub-image - type : Name of component sub-image type, supported types are: "standalone", "kernel", "ramdisk", "firmware", "script", "filesystem", - "fdt". + "flat_dt". - data : Path to the external file which contains this node's binary data. - compression : Compression used by included data. Supported compressions are "gzip" and "bzip2". If no compression is used compression property -- 1.8.3.2

2 1

[U-Boot] [PATCH] nand: fix reading after switching ecc
by Jeroen Hofstee 17 Jan '14

17 Jan '14

The omap_gpmc allows switching ecc at runtime. Since the NAND_SUBPAGE_READ flag is only set, it is kept when switching to hw ecc, which is not correct. This leads to calling chip->ecc.read_subpage which is not a valid pointer. Therefore also clear the flag so reading in hw mode works again. Cc: Scott Wood <scottwood(a)freescale.com> Cc: Pekon Gupta <pekon(a)ti.com> Cc: Nikita Kiryanov <nikita(a)compulab.co.il> Signed-off-by: Jeroen Hofstee <jeroen(a)myspectrum.nl> --- drivers/mtd/nand/nand_base.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c index 1ce55fd..0762a19 100644 --- a/drivers/mtd/nand/nand_base.c +++ b/drivers/mtd/nand/nand_base.c @@ -3354,6 +3354,8 @@ int nand_scan_tail(struct mtd_info *mtd) /* Large page NAND with SOFT_ECC should support subpage reads */ if ((chip->ecc.mode == NAND_ECC_SOFT) && (chip->page_shift > 9)) chip->options |= NAND_SUBPAGE_READ; + else + chip->options &= ~NAND_SUBPAGE_READ; /* Fill in remaining MTD driver data */ mtd->type = MTD_NANDFLASH; -- 1.8.3.2

6 14

[U-Boot] Pull request: u-boot-arm/master
by Albert ARIBAUD 17 Jan '14

17 Jan '14

Hello Tom, The following changes since commit 6ba2bc8fa9be4bd09ec43e39cb8e666480ef010c: arm: use canonical sub mnemonic (2014-01-14 12:38:47 +0100) are available in the git repository at: git://git.denx.de/u-boot-arm master for you to fetch changes up to bf46e7d8d134521301ff02b6d97e8998aa10a83d: Merge branch 'u-boot-imx/master' into 'u-boot-arm/master' (2014-01-15 15:18:04 +0100) ---------------------------------------------------------------- Albert ARIBAUD (1): Merge branch 'u-boot-imx/master' into 'u-boot-arm/master' Fabio Estevam (2): mx6: clock: Pass the frequency as argument of enable_fec_anatop_clock() mx6: Add initial support for the Hummingboard solo arch/arm/cpu/armv7/mx6/clock.c | 8 +- arch/arm/include/asm/arch-mx6/clock.h | 9 +- arch/arm/include/asm/arch-mx6/imx-regs.h | 4 + board/freescale/mx6slevk/mx6slevk.c | 2 +- board/solidrun/hummingboard/Makefile | 9 + board/solidrun/hummingboard/README | 40 ++++ board/solidrun/hummingboard/hummingboard.c | 187 +++++++++++++++++ board/solidrun/hummingboard/solo.cfg | 25 +++ board/solidrun/mx6-microsom/800mhz_2x128mx16.cfg | 74 +++++++ board/solidrun/mx6-microsom/clocks.cfg | 33 +++ .../mx6-microsom/ddr-800mhz-32bit-setup.cfg | 76 +++++++ boards.cfg | 1 + include/configs/hummingboard.h | 226 +++++++++++++++++++++ 13 files changed, 691 insertions(+), 3 deletions(-) create mode 100644 board/solidrun/hummingboard/Makefile create mode 100644 board/solidrun/hummingboard/README create mode 100644 board/solidrun/hummingboard/hummingboard.c create mode 100644 board/solidrun/hummingboard/solo.cfg create mode 100644 board/solidrun/mx6-microsom/800mhz_2x128mx16.cfg create mode 100644 board/solidrun/mx6-microsom/clocks.cfg create mode 100644 board/solidrun/mx6-microsom/ddr-800mhz-32bit-setup.cfg create mode 100644 include/configs/hummingboard.h Amicalement, -- Albert.

2 3

[U-Boot] [PATCH] board_r - fixup functions table after relocation
by Alexey Brodkin 17 Jan '14

17 Jan '14

"init_sequence_r" is just an array that consists of compile-time adresses of init functions. Since this is basically an array of integers (pointers to "void" to be more precise) it won't be modified during relocation - it will be just copied to new location as it is. As a consequence on execution after relocation "initcall_run_list" will be jumping to pre-relocation addresses. As long as we don't overwrite pre-relocation memory area init calls are executed correctly. But still it is dangerous because after relocation we don't expect initially used memory to stay untouched. Signed-off-by: Alexey Brodkin <abrodkin(a)synopsys.com> Cc: Tom Rini <trini(a)ti.com> Cc: Simon Glass <sjg(a)chromium.org> Cc: Masahiro Yamada <yamada.m(a)jp.panasonic.com> Cc: Doug Anderson <dianders(a)chromium.org> --- common/board_r.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/common/board_r.c b/common/board_r.c index 86ca1cb..8f45943 100644 --- a/common/board_r.c +++ b/common/board_r.c @@ -903,9 +903,14 @@ init_fnc_t init_sequence_r[] = { void board_init_r(gd_t *new_gd, ulong dest_addr) { + int i; #ifndef CONFIG_X86 gd = new_gd; #endif + /* Fixup table after relocation */ + for (i = 0; i < sizeof(init_sequence_r)/sizeof(void *); i++) + init_sequence_r[i] += gd->reloc_off; + if (initcall_run_list(init_sequence_r)) hang(); -- 1.8.4.2

6 11

[U-Boot] U-boot memory test results
by aryanlak 17 Jan '14

17 Jan '14

Hi all, I want to perform memory test (FLASH) during U-boot and read the results after the operating system (Linux) is booted up. Is it possible? If so, can anyone guide me to do so? Regards Lakshmi -- View this message in context: http://u-boot.10912.n7.nabble.com/U-boot-memory-test-results-tp171691.html Sent from the U-Boot mailing list archive at Nabble.com.

2 1

[U-Boot] Fwd: Re: Boot Linux kernel with initramfs fails
by Jean-baptiste DURONEA 17 Jan '14

17 Jan '14

Dear Wolfgang Denk, I forgot some explanations, sorry about that. I refer to this problem : http://lists.denx.de/pipermail/u-boot/2013-July/159055.html First, I tried to boot linux with initramfs through u-boot, but I had the same problem explained in my first post. Here is a part of the config file used by my -boot : /* High Level Configuration Options */ #define CONFIG_ARMV7 /* This is armv7 Cortex-A9 CPU core */ #define CONFIG_MXC #define CONFIG_MX6DL #define CONFIG_MX6DL_DDR3 #define CONFIG_MX6DL_SABRESD #define CONFIG_DDR_32BIT #define CONFIG_FLASH_HEADER #define CONFIG_FLASH_HEADER_OFFSET 0x400 #define CONFIG_MX6_CLK32 32768 /* Disable secure boot feature in default, if you want to enable this * feature, please carefully read related documents, you may needs to * change u-boot.lds */ #undef CONFIG_SECURE_BOOT #define CONFIG_SKIP_RELOCATE_UBOOT #define CONFIG_ARCH_CPU_INIT #undef CONFIG_ARCH_MMU /* disable MMU first */ #define CONFIG_L2_OFF /* disable L2 cache first*/ #define CONFIG_MX6_HCLK_FREQ 24000000 #define CONFIG_DISPLAY_CPUINFO #define CONFIG_DISPLAY_BOARDINFO #define CONFIG_SYS_64BIT_VSPRINTF #define BOARD_LATE_INIT #define CONFIG_CMDLINE_TAG /* enable passing of ATAGs */ #define CONFIG_SERIAL_TAG #define CONFIG_REVISION_TAG #define CONFIG_SETUP_MEMORY_TAGS #define CONFIG_INITRD_TAG #define CONFIG_MXC_GPIO initramfs is loaded in ram at 0x10C00000 by mfgtools, which is the freescales's manufacturing tool. I don't know which configuration I need to set on u-boot to tell him initramfs is at address 0x10C00000, and consequently it hands on linux. I am really bloqued on this problem. Can you give me some hints ? Tanks a lot ! Regards, Le 17/01/2014 07:16, Wolfgang Denk a écrit : > Dear Jean-baptiste DURONEA, > > In message <52D7D2F7.2050307(a)gmail.com> you wrote: >> We made a custom board based on imx6solo. >> I have the same problem ! > The same problem as what or who? I cannot even guess... > >> I have some trouble booting linux kernel with initramfs. I built linux >> kernel with CONFIG_BLK_DEV_INITRD, so Kbuild generates >> usr/initramfs_data.cpio which is integrated into the kernel. > ... > ... >> My kernel hangs after the last line, instead of doing "Freeing init >> memory: ..." but I don't know if it comes from the same problem or not... > Sorry, but I cannot see anything in your posting which might even > remotely be related to U-Boot. This is the U-Boot mailing list - your > question is off topic here. > > Best regards, > > Wolfgang Denk >

2 2

[U-Boot] [PATCH v5 0/38] Switch over to real Kbuild
by Masahiro Yamada 17 Jan '14

17 Jan '14

We switched to Kbuild style makefiles at v2014.01-rc1 release. With that modification, we can write makefiles simpler. But it is NOT real Kbuild. We need more progress. As the next step, this series imports (+ adjusts) build scripts from Linux Kernel under scripts/ directory. By applying this series, we can get more advantages: - short log - perfect dependency tracking - preparation to the next step, Kconfig - other things... Kbuild without Kconfig ---------------------- First of all, to make things clearer, let me explain the difference between "Kbuild" and "Kconfig". They are, I think, sometimes confusing. Kbuild - build system used for Linux Kernel. Some features of Kbuild are: (a) We can describe makefiles simply. Just add objects to "obj-y" like this: obj-$(CONFIG_FOO) += foo.o (b) We can describe directory descending nicely. Add directories with a slash to "obj-y" like this: obj-$(CONFIG_BAR) += bar/ (c) Short log like follows: CC common/foo.o CC common/bar.o LD common/built-in.o (d) Perfect dependency tracking I think this is the biggest advantage. To be honest, the dependency tracing of U-Boot build system was not reliable. Kconfig - A tool to manage CONFIG macros. We can handle the dependency among CONFIG macros. Kconfig allows us to modify CONFIG settings easily by "make config". GUI interface are also available by "make menuconfig" All defined CONFIG macros are stored into ".config" file I think most of U-boot developers are already familiar with above. (In most cases, they are Linux Kernel developers too.) I definitely want to port both of these, but I want to do them separately: Kbuild first. (If we do Kbuild and Kconfig at the same time, it might be messed up.) So, I want to do "Kbuild without Kconfig" in this series. The conventional tool (mkconfig + boards.cfg file) is used for board configuration. Prerequisite ------------ You need to apply the followings beforehand to use this series. [1] sandbox: Use system headers first for sandbox's os.c in a different way http://patchwork.ozlabs.org/patch/294233/ [2] board: tec-ng: Do not make directories in a board Makefile http://patchwork.ozlabs.org/patch/310825/ How to Build ? -------------- We can build the same as before. Do board configuraton first and then run "make". $ make omap4_panda_config Configuring for omap4_panda board... $ make CROSS_COMPILE=arm-linux-gnueabi- GEN include/autoconf.mk.dep GEN include/autoconf.mk CC lib/asm-offsets.s GEN include/generated/generic-asm-offsets.h CC arch/arm/cpu/armv7/omap4/asm-offsets.s GEN include/generated/asm-offsets.h HOSTCC scripts/basic/fixdep ... You will find a difference at a glance, short log If you need detail log message, please add "V=1". (You can also use "V=2") Please note we can no longer use $ make omap4_panda CROSS_COMPILE=arm-linux-gnueabi- to do board configuration and "make" at the same time. Instead, we can use Kbuild-ish way for that purpose: $ make omap4_panda_config all CROSS_COMPILE=arm-linux-gnuabi- This series keeps the other features: - Support out-of-tree build You can use "O=<dir_name>" like this $ mkdir build_dir $ make omap4_panda_config all O=build_dir CROSS_COMPILE=arm-linux-gnueabi- - Works with parallel make option Add "-j" option for this. Compiling will get faster. - Of cource, SPL, TPL build are supported (nand_spl also works. But "nand_spl" is obsolete and we should switch to "spl". Until when should we continue to maintain nand_spl?) - Breaks no boards (except some boards which are already broken) I built all target boards to prove correctness of this series at least for compile test. My Next Plan ------------ - Import Kconfig Use "make config", "make menuconfig", "make defconfig", etc. in U-Boot. - More refactoring Some parts of makefiles are still dirty. I want to refactor more makefiles in follow-up patches. - Use "obj-m" for standalone program?? Loadable module?? I have not deceided about this yet. Note ---- - I marked dirty parts with "FIX ME". In some board-specific config.mk files. # FIX ME ifneq ($(filter lib lib/lzma lib/zlib, $(obj)),) ccflags-y := -O2 endif In the top Makefile # FIX ME cpp_flags := $(KBUILD_CPPFLAGS) $(CPPFLAGS) $(UBOOTINCLUDE) $(NOSTDINC_FLAGS) c_flags := $(KBUILD_CFLAGS) $(cpp_flags) I will re-write them more nicely after other parts are prepared. Changes for v5: - Fix a bug reported by Gerhard Sittig: "make tools" before running "make" failed at v4. - Revive "env" target so that we can build only under tools/env/. - Add a new patch at the tail: 38/38 "tools/env: cross-compile fw_printenv without setting HOSTCC" - Describe "clobber" target shortly by deleteing "*.imx" and "*.map" with wildcard matching. - Rebase on the current u-boot/master Changes for v4: - Add a new patch at the tail: 37/37 "kbuild: Do not generate .*.su files at the top directory" - Change "checkstack" target to Kbuild style - Move the line where U_BOOT_VERSION is defined Changes for v3: - Rebase on the current u-boot/master - Add a new patch at the tail: 36/36 "board: sandburst: delete FORCEBUILD" Changes for v2: - At version 1, nand_spl boards got broken at 12 and fixed at 14. Fix this problem - At version 1, sandbox got broken at 17 and fixed at 21. Fix this problem - Add a new patch at the tail: 35/35 "Kbuild: chech clean source and generate Makefile for out-of-tree build" - Rebase on v2014.01-rc2 tag Masahiro Yamada (38): .gitignore: ingore files generated by Kbuild Makefile.host.tmp: add a new script to refactor tools tools: convert makefiles to kbuild style board: samsung: refactor host programs examples: Use scripts/Makefile.build nand-spl: Use scripts/Makefile.build Makfile: move suffix rules to Makefile.build Makefile: move some variable definitions to the top Makefile Makefile: move BFD_ROOT_DIR to tools/gdb/Makefile kbuild: import Kbuild.include from linux v3.12 tag kbuild: Use Kbuild.include Makefile: move more flags to the top Makefile Makefile: refactor include path settings Makefile: move more stuff to top Makefile Makefile: move some flags to spl/Makefile Makefile: move some flags to examples makefiles kbuild: change out-of-tree build kbuild: add dummy obj-y to create built-in.o Makefile: rename scripts/Makefile.build to scripts/Makefile.build.tmp kbuild: import more build scripts from Linux v3.12 tag kbuild: use Linux Kernel build scripts kbuild: delete temporary build scripts kbuild: move some lines to more suitable place kbuild: convert some make rules to Kbuild style kbuild: move include directives of board configuration files kbuild: generate {spl,tpl}-autoconf.mk only when it is necessary Makefile: remove a cleaning target "tidy" kbuild: change the top Makefile to more Kbuild-ish structure examples: move api/ and standalone/ to examples/Makefile kbuild: refactor Makefile and spl/Makefile more Makefile: Do not pass MTD_VERSION from the top Makefile Makefile: refactor tools-all targets kbuild: use scripts/Makefile.clean kbuild: support simultaneous board configuration and "make all" kbuild: check clean source and generate Makefile for out-of-tree build board: sandburst: delete FORCEBUILD kbuild: Do not generate .*.su files at the top directory tools/env: cross-compile fw_printenv without setting HOSTCC .gitignore | 28 +- MAKEALL | 8 +- Makefile | 1310 +++++++++++++------- arch/arm/cpu/arm1136/config.mk | 2 +- arch/arm/cpu/arm926ejs/config.mk | 2 +- arch/arm/cpu/arm926ejs/davinci/config.mk | 2 +- arch/arm/cpu/armv7/am33xx/config.mk | 2 +- arch/arm/cpu/armv7/config.mk | 2 +- arch/arm/cpu/armv7/omap3/config.mk | 2 +- arch/arm/cpu/armv7/omap4/config.mk | 2 +- arch/arm/cpu/armv7/omap5/config.mk | 2 +- arch/arm/cpu/armv7/socfpga/config.mk | 2 +- arch/arm/cpu/armv7/tegra114/Makefile | 3 +- arch/arm/cpu/armv7/tegra30/Makefile | 3 +- arch/arm/imx-common/Makefile | 2 +- arch/blackfin/config.mk | 10 +- arch/blackfin/cpu/Makefile | 10 +- arch/blackfin/lib/Makefile | 5 +- arch/m68k/cpu/mcf5227x/Makefile | 2 +- arch/m68k/cpu/mcf523x/Makefile | 2 +- arch/m68k/cpu/mcf52x2/Makefile | 2 +- arch/m68k/cpu/mcf532x/Makefile | 2 +- arch/m68k/cpu/mcf5445x/Makefile | 2 +- arch/m68k/cpu/mcf547x_8x/Makefile | 2 +- arch/mips/cpu/mips32/config.mk | 2 +- arch/mips/cpu/mips64/config.mk | 2 +- arch/mips/cpu/xburst/config.mk | 2 +- arch/nds32/config.mk | 2 +- arch/nds32/cpu/n1213/Makefile | 3 + arch/powerpc/cpu/mpc8xx/Makefile | 2 +- arch/powerpc/lib/Makefile | 4 +- arch/sandbox/cpu/Makefile | 11 +- arch/sparc/config.mk | 3 +- arch/x86/lib/Makefile | 2 +- board/ait/cam_enc_4xx/config.mk | 2 +- board/avionic-design/medcom-wide/Makefile | 2 +- board/avionic-design/plutux/Makefile | 2 +- board/avionic-design/tec-ng/Makefile | 2 +- board/avionic-design/tec/Makefile | 2 +- board/bct-brettl2/config.mk | 7 +- board/bf518f-ezbrd/config.mk | 7 +- board/bf526-ezbrd/config.mk | 7 +- board/bf527-ad7160-eval/config.mk | 7 +- board/bf527-ezkit/config.mk | 7 +- board/bf527-sdp/config.mk | 7 +- board/bf533-ezkit/config.mk | 7 +- board/bf533-stamp/config.mk | 7 +- board/bf537-stamp/config.mk | 7 +- board/bf538f-ezkit/config.mk | 7 +- board/bf548-ezkit/config.mk | 7 +- board/bf561-acvilon/config.mk | 7 +- board/bf561-ezkit/config.mk | 7 +- board/br4/config.mk | 7 +- board/cm-bf527/config.mk | 7 +- board/cm-bf533/config.mk | 7 +- board/cm-bf537e/config.mk | 7 +- board/cm-bf537u/config.mk | 7 +- board/cm-bf548/config.mk | 7 +- board/cm-bf561/config.mk | 7 +- board/compal/paz00/Makefile | 2 +- board/compulab/trimslice/Makefile | 2 +- board/cray/L1/Makefile | 10 +- board/freescale/common/Makefile | 5 +- board/h2200/Makefile | 2 +- board/ip04/config.mk | 7 +- board/matrix_vision/mvblm7/Makefile | 4 +- board/matrix_vision/mvblx/Makefile | 2 +- board/matrix_vision/mvsmr/Makefile | 2 +- board/nvidia/common/Makefile | 2 +- board/pcs440ep/config.mk | 2 +- board/pr1/config.mk | 7 +- board/samsung/origen/Makefile | 23 +- .../origen/tools/{mkv310_image.c => mkorigenspl.c} | 0 board/samsung/smdkv310/Makefile | 16 +- .../tools/{mkv310_image.c => mksmdkv310spl.c} | 0 board/sandburst/karef/Makefile | 6 +- board/sandburst/metrobox/Makefile | 6 +- board/spear/common/Makefile | 5 +- board/spear/x600/Makefile | 5 +- board/st-ericsson/snowball/Makefile | 2 +- board/st-ericsson/u8500/Makefile | 2 +- board/tcm-bf518/config.mk | 7 +- board/tcm-bf537/config.mk | 7 +- common/Makefile | 11 +- config.mk | 333 +---- disk/Makefile | 2 +- doc/DocBook/Makefile | 17 - drivers/bios_emulator/Makefile | 5 +- drivers/hwmon/Makefile | 2 +- drivers/net/npe/Makefile | 4 +- drivers/rtc/Makefile | 2 +- drivers/usb/musb-new/Makefile | 7 +- dts/Makefile | 20 +- examples/Makefile | 9 + examples/api/Makefile | 44 +- examples/standalone/Makefile | 71 +- fs/ubifs/Makefile | 2 +- fs/yaffs2/Makefile | 9 +- lib/Makefile | 2 +- lib/lzma/Makefile | 2 +- mkconfig | 2 +- nand_spl/board/amcc/acadia/Makefile | 43 +- nand_spl/board/amcc/bamboo/Makefile | 43 +- nand_spl/board/amcc/canyonlands/Makefile | 43 +- nand_spl/board/amcc/kilauea/Makefile | 41 +- nand_spl/board/amcc/sequoia/Makefile | 45 +- nand_spl/board/freescale/mpc8315erdb/Makefile | 45 +- nand_spl/board/freescale/mpc8536ds/Makefile | 57 +- nand_spl/board/freescale/mpc8569mds/Makefile | 57 +- nand_spl/board/freescale/mpc8572ds/Makefile | 57 +- nand_spl/board/freescale/p1023rds/Makefile | 58 +- nand_spl/board/freescale/p1_p2_rdb/Makefile | 57 +- nand_spl/board/sheldon/simpc8313/Makefile | 46 +- net/Makefile | 2 +- post/lib_powerpc/fpu/Makefile | 30 +- rules.mk | 51 - scripts/Kbuild.include | 284 +++++ scripts/Makefile | 2 + scripts/Makefile.build | 519 +++++++- scripts/Makefile.clean | 108 ++ scripts/Makefile.host | 170 +++ scripts/Makefile.lib | 375 ++++++ scripts/basic/.gitignore | 1 + scripts/basic/Makefile | 15 + scripts/basic/fixdep.c | 462 +++++++ scripts/mkmakefile | 59 + spl/Makefile | 187 +-- tools/.gitignore | 3 +- tools/Makefile | 373 ++---- tools/crc32.c | 1 + tools/easylogo/Makefile | 12 +- tools/env/.gitignore | 2 + tools/env/Makefile | 39 +- tools/env/README | 5 +- tools/env/crc32.c | 1 + tools/env/ctype.c | 1 + tools/env/env_attr.c | 1 + tools/env/env_flags.c | 1 + tools/env/linux_string.c | 1 + tools/env_embedded.c | 1 + tools/fdt.c | 1 + tools/fdt_ro.c | 1 + tools/fdt_rw.c | 1 + tools/fdt_strerror.c | 1 + tools/fdt_wip.c | 1 + tools/gdb/Makefile | 64 +- tools/image-fit.c | 1 + tools/image-sig.c | 1 + tools/image.c | 1 + tools/kernel-doc/Makefile | 21 +- tools/md5.c | 1 + tools/rsa-sign.c | 1 + tools/sha1.c | 1 + 153 files changed, 3621 insertions(+), 2035 deletions(-) rename board/samsung/origen/tools/{mkv310_image.c => mkorigenspl.c} (100%) rename board/samsung/smdkv310/tools/{mkv310_image.c => mksmdkv310spl.c} (100%) create mode 100644 examples/Makefile delete mode 100644 rules.mk create mode 100644 scripts/Kbuild.include create mode 100644 scripts/Makefile create mode 100644 scripts/Makefile.clean create mode 100644 scripts/Makefile.host create mode 100644 scripts/Makefile.lib create mode 100644 scripts/basic/.gitignore create mode 100644 scripts/basic/Makefile create mode 100644 scripts/basic/fixdep.c create mode 100644 scripts/mkmakefile create mode 100644 tools/crc32.c create mode 100644 tools/env/.gitignore create mode 100644 tools/env/crc32.c create mode 100644 tools/env/ctype.c create mode 100644 tools/env/env_attr.c create mode 100644 tools/env/env_flags.c create mode 100644 tools/env/linux_string.c create mode 100644 tools/env_embedded.c create mode 100644 tools/fdt.c create mode 100644 tools/fdt_ro.c create mode 100644 tools/fdt_rw.c create mode 100644 tools/fdt_strerror.c create mode 100644 tools/fdt_wip.c create mode 100644 tools/image-fit.c create mode 100644 tools/image-sig.c create mode 100644 tools/image.c create mode 100644 tools/md5.c create mode 100644 tools/rsa-sign.c create mode 100644 tools/sha1.c -- 1.8.3.2

1 38

[U-Boot] [PATCH] drivers/designware_i2c - add suppor of CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW
by Alexey Brodkin 17 Jan '14

17 Jan '14

Since we agreed on legacy implementation of "eeprom_{read|write}" (http://patchwork.ozlabs.org/patch/295825/) I had to fix/make it work again DesignWare I2C driver for cases when 1 EEPROM IC fake I2C with anumber of "built-in" ICs with different chip addresses. Signed-off-by: Alexey Brodkin <abrodkin(a)synopsys.com> Cc: Tom Rini <trini(a)ti.com> cc: Armando Visconti <armando.visconti(a)st.com> Cc: Stefan Roese <sr(a)denx.de> Cc: Albert ARIBAUD <albert.u.boot(a)aribaud.net> Cc: Heiko Schocher <hs(a)denx.de> Cc: Vipin KUMAR <vipin.kumar(a)st.com> Cc: Tom Rix <Tom.Rix(a)windriver.com> Cc: Mischa Jonker <mjonker(a)synopsys.com> Cc: Kuo-Jung Su <dantesu(a)faraday-tech.com> --- drivers/i2c/designware_i2c.c | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/drivers/i2c/designware_i2c.c b/drivers/i2c/designware_i2c.c index cb2ac04..9ed9295 100644 --- a/drivers/i2c/designware_i2c.c +++ b/drivers/i2c/designware_i2c.c @@ -266,6 +266,25 @@ int i2c_read(uchar chip, uint addr, int alen, uchar *buffer, int len) { unsigned long start_time_rx; +#ifdef CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW + /* + * EEPROM chips that implement "address overflow" are ones + * like Catalyst 24WC04/08/16 which has 9/10/11 bits of + * address and the extra bits end up in the "chip address" + * bit slots. This makes a 24WC08 (1Kbyte) chip look like + * four 256 byte chips. + * + * Note that we consider the length of the address field to + * still be one byte because the extra address bits are + * hidden in the chip address. + */ + chip |= ((addr >> (alen * 8)) & CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW); + addr &= ~(CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW << (alen * 8)); + + debug("%s: fix addr_overflow: chip %02x addr %02x\n", __func__, chip, + addr); +#endif + if (check_params(addr, alen, buffer, len)) return 1; @@ -307,6 +326,25 @@ int i2c_write(uchar chip, uint addr, int alen, uchar *buffer, int len) int nb = len; unsigned long start_time_tx; +#ifdef CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW + /* + * EEPROM chips that implement "address overflow" are ones + * like Catalyst 24WC04/08/16 which has 9/10/11 bits of + * address and the extra bits end up in the "chip address" + * bit slots. This makes a 24WC08 (1Kbyte) chip look like + * four 256 byte chips. + * + * Note that we consider the length of the address field to + * still be one byte because the extra address bits are + * hidden in the chip address. + */ + chip |= ((addr >> (alen * 8)) & CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW); + addr &= ~(CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW << (alen * 8)); + + debug("%s: fix addr_overflow: chip %02x addr %02x\n", __func__, chip, + addr); +#endif + if (check_params(addr, alen, buffer, len)) return 1; -- 1.8.4.2

3 3

[U-Boot] Boot Linux kernel with initramfs fails
by Axel Lin 17 Jan '14

17 Jan '14

Hi, When I boot Linux kernel with FIT Image, the kernel does not unpacking initramfs. ( The root cause is "initrd_start is NULL".) The initramfs is built-in with kernel, so I don't specify ramdisk in my kernel.its file. Is this a known issue or do I need special setting to boot a Linux kernel with initramfs? BTW, bootm shows below messages: => bootm ## Loading kernel from FIT Image at 00400000 ... Using 'conf@1' configuration Trying 'kernel@1' kernel subimage Description: kernel Type: Kernel Image Compression: uncompressed Data Start: 0x004000e8 Data Size: 2496848 Bytes = 2.4 MiB Architecture: ARM OS: Linux Load Address: 0x00000000 Entry Point: 0x00000000 Verifying Hash Integrity ... OK ## Loading fdt from FIT Image at 00400000 ... Using 'conf@1' configuration Trying 'fdt@1' fdt subimage Description: gpl327xx.dtb Type: Flat Device Tree Compression: uncompressed Data Start: 0x00661ae8 Data Size: 2174 Bytes = 2.1 KiB Architecture: ARM Hash algo: sha1 Hash value: 674b5443523a23ad8de49b161932fd3a1d7f90ea Verifying Hash Integrity ... sha1+ OK Booting using the fdt blob at 0x661ae8 Loading Kernel Image ... OK ## initrd_high = 0xffffffff, copy_to_ram = 1 ramdisk load start = 0x00000000, ramdisk load end = 0x00000000 Loading Device Tree to 019b4000, end 019b787d ... OK Below is part of my boot messages: NET: Registered protocol family 1 BEGIN::: populate_rootfs... ^^^ My debug message, so I know populate_rootfs() is executed. populate_rootfs... initrd_start is NULL ^^^ My debug message, I got "initrd_start is NULL". That is why the initramfs is not unpack. ROMFS MTD (C) 2007 Red Hat, Inc. io scheduler noop registered (default) TCP: cubic registered NET: Registered protocol family 10 sit: IPv6 over IPv4 tunneling driver Warning: unable to open an initial console. VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper Not tainted 3.11.0-rc1-00018-g16fc5bc-dirty #131 [<0000bda8>] (unwind_backtrace+0x0/0xf0) from [<0000ac0c>] (show_stack+0x10/0x14) [<0000ac0c>] (show_stack+0x10/0x14) from [<001fcff8>] (panic+0x7c/0x1c4) [<001fcff8>] (panic+0x7c/0x1c4) from [<0026ddb4>] (mount_block_root+0x1f4/0x2b4) [<0026ddb4>] (mount_block_root+0x1f4/0x2b4) from [<0026e000>] (prepare_namespace+0x128/0x18c) [<0026e000>] (prepare_namespace+0x128/0x18c) from [<0026da74>] (kernel_init_freeable+0x164/0x1a8) [<0026da74>] (kernel_init_freeable+0x164/0x1a8) from [<001fb808>] (kernel_init+0x8/0xe4) [<001fb808>] (kernel_init+0x8/0xe4) from [<00008f70>] (ret_from_fork+0x14/0x24) (Test on latest u-boot git tree.) Regards, Axel

3 3

[U-Boot] [PATCH RFC 1/4] config: remove distro_default from common.h
by Stephen Warren 17 Jan '14

17 Jan '14

From: Stephen Warren <swarren(a)nvidia.com> Including it from here doesn't ensure that the config options show up in all the right places. Instead, each per-board header file (or a file that boards include) should include it themselves directly. Signed-off-by: Stephen Warren <swarren(a)nvidia.com> --- This series is based on: a) Dennis Gilmore's series to add config_distro_default.h. Since that series is RFC, so is this. b) My recent series to implement the "exists" shell command. --- include/common.h | 5 ----- 1 file changed, 5 deletions(-) diff --git a/include/common.h b/include/common.h index 00969a51240d..d49c51464dad 100644 --- a/include/common.h +++ b/include/common.h @@ -99,11 +99,6 @@ typedef volatile unsigned char vu_char; #include <flash.h> #include <image.h> -/* use generic distro config */ -#ifdef DISTRO_DEFAULTS -#include <config_distro_default.h> -#endif - #ifdef DEBUG #define _DEBUG 1 #else -- 1.8.1.5

1 3