- May 26, 2015
-
-
Joe Hershberger authored
A common case for failed builds is a missing compiler. Print a message for that case to tell the user concisely which compiler was expected that was not found. This patch also has the effect of not printing build errors any longer. The next patch will add a switch to optionally bring that back. Signed-off-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Joe Hershberger authored
If boards fail, output that list to a file so that it can easily be passed back into moveconfig.py using the -d option. Signed-off-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Joe Hershberger authored
Some config.h files live in arch and board directories. They will need to be cleaned up as well, so run the same filters there. Signed-off-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Joe Hershberger authored
In some case you may want to only cleanup the headers. Make it possible without waiting for all boards to compile. Signed-off-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Joe Hershberger authored
This is helpful to re-attempt to move failed boards from a previous run without starting over. Signed-off-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Joe Hershberger authored
When moving configs, it is important to know what was defined in the config header even if it duplicates the configs coming from Kconfig. This is specifically needed for the case where a config is set to default 'y' in the Kconfig. This would previously cause the actual value from the include config to be filtered out, and moveconfig.py would think that it was 'n'... This means that the value that should be 'y' is now (in every defconfig) set to 'not set'. tools/moveconfig.py now defines KCONFIG_IGNORE_DUPLICATES to prevent the filtering from happening and selecting wrong values for the defconfig. Signed-off-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Joe Hershberger authored
This will ensure that the order of the defconfig entries will always match that of the Kconfig files. After one slightly painful (but still early in the process) pass over all boards, this should keep the defconfigs clean from here on. Users must edit the Kconfig first to add the menu entries and then run moveconfig.py to update the defconfig files and the include configs. As such, moveconfig.py cannot compare against the '.config' contents. Signed-off-by:
Joe Hershberger <joe.hershberger@ni.com> Acked-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
This tool was originally written for my local use to ease the task of tons of CONFIG moves, but there have been some requests for mainlining it. So, I have tidied up the code with nicer comments, and here it is. See the comment block of the script for usage. The first draft was http://patchwork.ozlabs.org/patch/430422/ Main updates are: - Adapted to the single .config configuration - Support colored log - Support moving multiple options at once (and take configs via input file only) - Continue even if some boards fail (Idea provided by Joe Hershberger) - Add more options - More comments and code cleanups Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by:
Joe Hershberger <joe.hershberger@ni.com>
-
git://www.denx.de/git/u-boot-imxTom Rini authored
-
Move CONFIG_CMD_CACHE to mx6_common and standardise the way it's defined. Signed-off-by:
Peter Robinson <pbrobinson@gmail.com> Reviewed-by: Tom Rini <trini at konsulko.com>
-
Move all standard mx6 MMC configs to mx6_common. Signed-off-by:
Peter Robinson <pbrobinson@gmail.com> Reviewed-by: Tom Rini <trini at konsulko.com>
-
Move all standard filesystem, partition and fdt options to mx6_common. Signed-off-by:
Peter Robinson <pbrobinson@gmail.com>
-
Move generic miscellaneous options that are standard across most, if not all, mx6 boards to central mx6_common define to ensure consistent features. Signed-off-by:
Peter Robinson <pbrobinson@gmail.com>
-
Define common LOADADDR and BOOTDELAY to ensure a consistent experience across mx6 boards Signed-off-by:
Peter Robinson <pbrobinson@gmail.com>
-
Define CONFIG_MXC_GPIO and CONFIG_CMD_GPIO by default in mx6_common Signed-off-by:
Peter Robinson <pbrobinson@gmail.com>
-
Define the standard ATAG consfigs in mx6_common. Signed-off-by:
Peter Robinson <pbrobinson@gmail.com> Reviewed-by: Tom Rini <trini at konsulko.com>
-
All boards define CONFIG_MX6, CONFIG_DISPLAY_BOARDINFO, CONFIG_DISPLAY_CPUINFO and CONFIG_SYS_GENERIC_BOARD so define them in mx6_common Signed-off-by:
Peter Robinson <pbrobinson@gmail.com> Reviewed-by: Tom Rini <trini at konsulko.com>
-
The linux/sizes.h, asm/arch/imx-regs.h, asm/imx-common/gpio.h, config_cmd_default.h includes are used fairly universally across imx6 boards so include them in mx6_common.h by default. We define CONFIG_SYS_NO_FLASH before config_cmd_default.h so that we don't have to undef CONFIG_CMD_FLASH / CONFIG_CMD_IMLS everywhere. Signed-off-by:
Peter Robinson <pbrobinson@gmail.com>
-
Standardise mx6_common.h to the same as other mx6 boards Signed-off-by:
Peter Robinson <pbrobinson@gmail.com> Reviewed-by: Tom Rini <trini at konsulko.com>
-
91199f4a broke mmc based Falcon mode. The block_read function returns the number of blocks read thus the error check needs to look for a return of 0 blocks read. Cc: Paul Kocialkowski <contact@paulk.fr> Signed-off-by:
Tim Harvey <tharvey@gateworks.com> Acked-by:
Paul Kocialkowski <contact@paulk.fr>
-
Signed-off-by:
Tim Harvey <tharvey@gateworks.com>
-
Signed-off-by:
Tim Harvey <tharvey@gateworks.com>
-
We will use the same env size and redundancy used for NAND env for MMC. Signed-off-by:
Tim Harvey <tharvey@gateworks.com>
-
The CPU temperature grade from OTP is now used to define the critical threshold at which point we busyloop until we are below, however this threshold is still too low. Instead of 20C below the max CPU temperature, change it to 5C defined now by TEMPERATURE_HOT_DETLA for clarity. Rename 'passive' to 'critical' as that better defines our use case here. Additionally change the output of the busyloop message to show the max CPU temperature as well as current. Before: CPU Temperature is 101 C, too hot to boot, waiting... CPU Temperature is 101 C, too hot to boot, waiting... After: CPU Temperature (101C) too close to max (105C) waiting... CPU Temperature (101C) too close to max (105C) waiting... Cc: Stefan Roese <sr@denx.de> Cc: Eric Nelson <eric.nelson@boundarydevices.com> Cc: Heiko Schocher <hs@denx.de> Cc: Nikita Kiryanov <nikita@compulab.co.il> Cc: Jon Nettleton <jon.nettleton@gmail.com> Cc: Jason Liu <r64343@freescale.com> Cc: Ye Li <b37916@freescale.com> Cc: Fabio Estevam <fabio.estevam@freescale.com> Cc: Christian Gmeiner <christian.gmeiner@gmail.com> Cc: Markus Niebel <Markus.Niebel@tq-group.com> Cc: Peng Fan <b51431@freescale.com> Signed-off-by:
Tim Harvey <tharvey@gateworks.com>
-
add support for imx6dl based aristainetos2 board U-Boot 2015.04-rc5-00066-g60f6ed4 (Apr 10 2015 - 08:46:27) CPU: Freescale i.MX6DL rev1.1 at 792 MHz Reset cause: WDOG Board: aristaitenos2 Watchdog enabled I2C: ready DRAM: 1 GiB NAND: 1024 MiB MMC: FSL_SDHC: 0 SF: Detected N25Q128A with page size 256 Bytes, erase size 64 KiB, total 16 MiB Display: lg4573 (480x800) In: serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 0 => Signed-off-by:
Heiko Schocher <hs@denx.de>
-
rework and unify i2c address names for different SoCs, which use the mxc_i2c driver. Signed-off-by:
Heiko Schocher <hs@denx.de>
-
add I2C4 modul for MX6DL based boards. Signed-off-by:
Heiko Schocher <hs@denx.de>
-
We should not hardcode MXS_DMA_ALIGNMENT to 32, since we can not guarantee that socs' cache line size is 32 bytes. If on chips whose cache line size is 64 bytes, error occurs: " NAND: ERROR: v7_dcache_inval_range - start address is not aligned - 0xbdf1d1a0 ERROR: v7_dcache_inval_range - stop address is not aligned - 0xbdf1f4a0 ERROR: v7_dcache_inval_range - start address is not aligned - 0xbdf1d1a0 " Align MXS_DMA_ALIGNMENT with ARCH_DMA_MINALIGN whose value is same to CONFIG_SYS_CACHELINE_SIZE if CONFIG_SYS_CACHELINE_SIZE defined. Signed-off-by:
Peng Fan <Peng.Fan@freescale.com> Acked-by:
Marek Vasut <marex@denx.de>
-
The break after return is unreachable code, remove it. Signed-off-by:
Axel Lin <axel.lin@ingics.com> Acked-by:
Stefano Babic <sbabic@denx.de> Acked-by:
Heiko Schocher <hs@denx.de>
-
pwm_id_to_reg() can return NULL, so add NULL testing to prevent NULL pointer dereference. Signed-off-by:
Axel Lin <axel.lin@ingics.com> Acked-by:
Stefano Babic <sbabic@denx.de> Acked-by:
Heiko Schocher <hs@denx.de>
-
- May 25, 2015
-
-
Masahiro Yamada authored
Due to licensing issues, the files ps7_init.c/h are not able to be distributed with U-Boot source code. Recent Xilinx tools also provide the GPL variants (ps7_init_gpl.c/h), compatible with U-Boot license. Prior to this commit, we had to copy ps7_init files into board/xilinx/zynq/ before the compile. To be more user-friendly, let's include ps7_init_gpl.c/h for Zedboard, MicroZed, ZC702, ZC706. These init code have been taken from the hwplatform_templates directory of Xilinx SDK 2014.4. You can still use customized ps7_init_gpl.c/h by enabling CONFIG_ZYNQ_CUSTOM_INIT. The recommended directory for storing them is now board/xilinx/zynq/custom_hw_platform, but board/xilinx/zynq is still supported for backward compatibility. The latter emits a warning message to prompt users to gradually switch to the new directory. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by:
Sören Brinkmann <soren.brinkmann@xilinx.com> Acked-by:
Joe Hershberger <joe.hershberger@ni.com> Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
Masahiro Yamada authored
Prior to this commit, ZC702 and ZC706 shared the same configuration and were built as follows: ZC702: make zynq_zc70x_defconfig && make ZC706: make zynq_zc70x_defconfig && make DEVICE_TREE=zynq-zc706 This commit introduces separate configuration for them, which makes the next commit much easier. Going forward, the recommended build commands are: ZC702: make zynq_zc702_defconfig && make ZC706: make zynq_zc706_defconfig && make Although the old work flow is still supported, CONFIG_TARGET_ZC70X has been marked as deprecated. If used, the warning message is shown to prompt users to switch to the new scheme. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by:
Joe Hershberger <joe.hershberger@ni.com> Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
Michal Simek authored
Don't use error-prone arch timer code and instead use system timer implementation to simplify our code. Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
- May 24, 2015
-
-
Stefan Agner authored
This changes enable ONFI detection. The Read ID command now allows one address byte which is needed for ONFI detection. To read the ONFI parameter page, the NAND_CMD_PARAM need to be supported. The CMD code enables one command and one address byte along with reading data from flash using R/B#, as specified by ONFI. Signed-off-by:
Stefan Agner <stefan@agner.ch>
-
Stefan Agner authored
Add option to choose between current 24-error correction and 32-error correction through Kconfig. 32-error correction allow to use NAND chips which require up to 8-bit error correction per 512 byte (when using 2K pages). Signed-off-by:
Stefan Agner <stefan@agner.ch>
-
Stefan Agner authored
This commit allows users to enable/disable the Freescale NFC controller found in systems like Vybrid (VF610), MPC5125, MCF54418 or Kinetis K70 via Kconfig with more detailed help docs. Signed-off-by:
Stefan Agner <stefan@agner.ch> Acked-by:
Stefano Babic <sbabic@denx.de> [scottwood: updated vf610twr_nand_defconfig] Signed-off-by:
Scott Wood <scottwood@freescale.com>
-
Stefan Agner authored
Use in-band bad block table (NAND_BBT_NO_OOB) which allows to use the full OOB for hardare ECC purposes. Since there is no ECC correction on the OOB it is also safer to use in-band area to store the bad block table marker. Signed-off-by:
Stefan Agner <stefan@agner.ch>
-
Stefan Agner authored
Implement read of OOB area only. When using column and sector size properties, only parts of the page can be read. However, this works only when hardware ECC is disabled, otherwise the ECC engine would ruin the data in the buffer. To allow OOB only reads, three points had to be addressed: - Set ECC mode per command. - Handle NAND_CMD_READOOB seperate. Make sure column and sector size is correctly set up, while disabling ECC. - Now, the OOB data end up at the beginning of the buffer. Remove the special handling of OOB (spareonly). Especially bad block scans benefit from this change. On a 512MiB SLC NAND device, the bad block scan took 1.5s less than before. Signed-off-by:
Stefan Agner <stefan@agner.ch>
-