- Apr 20, 2015
-
-
Scott Wood authored
U-Boot on this board grew a long time ago past the 384 KiB that it reserves for the U-Boot image, before the environment. Thus, saveenv overwrites the U-Boot image and bricks the board. I tried to find out when U-Boot grew beyond this point, but there is a long stretch in the history where this board did not build -- and AFAICT when it did fit in 384 KiB, it was missing vital features such as fdt support. Turning off CONFIG_VIDEO was not enough to make it fit. Thus, I don't think we have any choice other than to move the environment. Signed-off-by:
Scott Wood <scottwood@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Shengzhou Liu authored
CONFIG_PHY_AQ1202 is no longer needed, use CONFIG_PHY_AQUANTIA. Signed-off-by:
Shengzhou Liu <Shengzhou.Liu@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Scott Wood authored
U-Boot does not have system calls (the services it exposes to standalone commands use a different mechanism), so the syscall handler is dead code. It's also broken code, as it assumes it is located at 0xc00 -- while even before the patch to stop relocating exception vectors to 0, U-Boot had the syscall at 0x900. The critical and machine check return paths are never called -- the regular exception return path is used instead, which works because xSRR0/1 have already been saved and can be restored via the regular SRR0/1 (we don't care too much in U-Boot about taking a critical/mcheck inside another exception prolog/epilog). Also remove a few other small unused functions. Signed-off-by:
Scott Wood <scottwood@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Scott Wood authored
Booke does not require exception vectors to be located at address zero. U-Boot was doing so anyway, simply because that's how it had been done on other PPC. The downside of this is that once the OS is loaded to address zero, the exception vectors have been overwritten -- which makes it difficult to diagnose a crash that happens after that point. The IVOR setup and trap entry code is simplified somewhat as a result. Also, there is no longer a need to align individual exceptions on 0x100 byte boundaries. Signed-off-by:
Scott Wood <scottwood@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Shengzhou Liu authored
Support SODIMM D3XP12081XL10AA 1866MT/s on T2080RDB. Enable CONFIG_CMD_MEMTEST as well. Signed-off-by:
Shengzhou Liu <Shengzhou.Liu@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Chunhe Lan authored
Now cortina driver uses macro CONFIG_SYS_CORTINA_FW_IN_NOR to define that firmware of cortina driver is stored in the nor flash. Signed-off-by:
Chunhe Lan <Chunhe.Lan@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Ying Zhang authored
The fuse status register provides the values from on-chip voltage ID efuses programmed at the factory. These values define the voltage requirements for the chip. u-boot reads FUSESR and translates the values into the appropriate commands to set the voltage output value of an external voltage regulator. Signed-off-by:
Ying Zhang <b40530@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Shengzhou Liu authored
T2080 rev1.1 also needs erratum a007186. Signed-off-by:
Shengzhou Liu <Shengzhou.Liu@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Alexander Graf authored
QEMU 2.3 changes the address layout of the CCSR map in the PV ppce500 machine to reside in higher address space. Unfortunately, this exposed a glitch in u-boot for ppce500: While providing a function to dynamically evaluate the CCSR region's position in physical address space, we never used it. Plus we forgot to support 64bit physical addresses. This patch fixes that mishap, making u-boot work fine with latest QEMU again. Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Scott Wood <scottwood@freescale.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
Curt Brune authored
According to the MPC8555/MPC8541 reference manual the SS_EN (source synchronous enable) bit in the DDR_SDRAM_CLK_CNLT register must be set during initialization. >From section 9.4.1.8 of that manual: Source synchronous enable. This bit field must be set during initialization. See Section 9.6.1, "DDR SDRAM Initialization Sequence," details. 0 - Reserved 1 - The address and command are sent to the DDR SDRAMs source synchronously. In addition, Freescale application note AN2805 is also very clear that this bit must be set. This patch reverts a change introduced by commit 457caecd. Testing Done: Compiled targets CONFIG_TARGET_MPC8555CDS and CONFIG_TARGET_MPC8541CDS and inspected the generated assembly code to verify the SS_EN bit was being set. There is one extra instruction emitted: fff9b774: 65 29 80 00 oris r9,r9,32768 Compiled the CONFIG_TARGET_MPC8548CDS target and verified that no additional instructions were emitted related to this patch. Booted an image on a MPC8541 based board successfully. Signed-off-by:
Curt Brune <curt@cumulusnetworks.com> Reviewed-by:
York Sun <yorksun@freescale.com>
-
- Apr 18, 2015
-
-
git://git.denx.de/u-boot-x86Tom Rini authored
-
Wu, Josh authored
Make cover letter shows like 0/x, 00/xx and 000/xxx etc. Signed-off-by:
Josh Wu <josh.wu@atmel.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Tom Rini authored
The help text for -V says we will pass V=1 but all it really did was not pass in -s. Change the logic to pass make V=1 with given to buildman -V or -s to make otherwise. Cc: Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Tom Rini authored
When told to keep outputs, be much more liberal in what files we keep. In addition to adding 'MLO', keep anything that matches u-boot-spl.* (so that we keep the map file as well) and anything we generate about 'u-boot itself. A large number of bootable formats now match this and thus it's easier to build many targets and then boot them afterwards using buildman. Cc: Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
It is useful to be able to see CONFIG changes made by commits. Add this feature to buildman using the -K flag so that all CONFIG changes are reported. The CONFIG options exist in a number of files. Each is reported individually as well as a summary that covers all files. The output shows three parts: green for additions, red for removals and yellow for changes. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Store all config file output so that we can compare changes if requested. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
At present buildman tries to detect an aborted build and doesn't record a result in that case. This is to make sure that an abort (e.g. with Ctrl-C) does not mark the build as done. Without this option, buildman would never retry the build unless -f/-F are provided. The effect is that aborting the build creates 'fake errors' on whatever builds buildman happens to be working on at the time. Unfortunately the current test is not reliable and this detection can trigger if a required toolchain tool is missing. In this case the toolchain problem is never reported. Adjust the logic to continue processing the build result, mark the build as done (and failed), but with a return code which indicates that it should be retried. The correct fix is to fully and correctly detect an aborted build, quit buildman immediately and not write any partial build results in this case. Unfortunately this is currently beyond my powers and is left as an exercise for the reader (and patches are welcome). Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
When a verbose build it selected, show the make command before the output of that command. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
At present CONFIG options are split across Kconfig and board config headers files. Also we have multiple files containing these CONFIG options. In order to see exactly what is being used for building, create a .cfg file which holds these options as reported by the C preprocessor. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Scott Wood authored
Don't store it in a u32. Don't dereference the bus address as if it were a virtual address (fixes 284231e4 ("ahci: Support splitting of read transactions into multiple chunks")). Fixes crash on boot in MPC8641HPCN_36BIT target. Signed-off-by:
Scott Wood <scottwood@freescale.com> Cc: Vadim Bendebury <vbendeb@chromium.org> Acked-by:
York Sun <yorksun@freescale.com>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Heiko <Schocher<hs@denx.de>
-
Simon Glass authored
Move this over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move these over to Kconfig and tidy up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move CONFIG_BOOT_STAGE and its associated options to Kconfig. Adjust existing users and code. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Switch this board over to use driver model for Ethernet. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Adjust the Ethernet initialisation code to support driver model. It is no-longer necessary to call designware_initialize(). The device will be probed when it is used. The PHY type and GMAC base will come from the device tree. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add driver model support to the designware driver. This reuses most of the existing code except for some duplication in the probe() method. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Joe Hershberger <joe.hershberger@ni.com>
-
Simon Glass authored
Adjust the error handling to use errno.h instead of returning -1. Change leaf functions to pass in the arguments they require rather than struct eth_device. Apart from simplifying the code it makes is easier to reuse these functions for driver model, since mostly they actually only use struct dw_eth_priv (which we can keep). Create a stub for each Ethernet operation function. This will allow use to share code with the driver model versions. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Joe Hershberger <joe.hershberger@ni.com>
-
Simon Glass authored
When driver model is used for Ethernet a few functions are passed a udevice instead of an eth_device. Also add a function to find a PHY type given its name. This will be used to decode the device tree node. Finally, put a phy_interface field in struct eth_pdata since this is an important part of the platform data for Ethernet. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Joe Hershberger <joe.hershberger@ni.com>
-
Simon Glass authored
This function is not supported with driver model. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Joe Hershberger <joe.hershberger@ni.com>
-