29 Nov, 2016
14 commits
-
With our common code in place actually make use of it across all our
modules.Signed-off-by: Marcel Ziswiler
Acked-by: Max Krummenacher -
Add Toradex factory configuration block handling. The config block is a
data structure which gets stored to flash during production testing. The
structure holds such information as board resp. hardware revision,
product ID and serial number which is used as the NIC part of the
Ethernet MAC address as well. The config block will be read upon boot by
the show_board_info() function, displayed as part of the board
information and passed to Linux via device tree or ATAGs.Signed-off-by: Marcel Ziswiler
Acked-by: Max Krummenacher -
Deactivate CONFIG_DISPLAY_BOARDINFO in favour of
CONFIG_DISPLAY_BOARDINFO_LATE which also displays on the LCD.Signed-off-by: Marcel Ziswiler
Acked-by: Max Krummenacher -
Make show_board_info() a weak function which allows for custom board
specific implementations thereof.Signed-off-by: Marcel Ziswiler
Reviewed-by: Tom Rini
Acked-by: Max Krummenacher -
Drop CONFIG_CUSTOM_BOARDINFO as it is not Kconfig compliant and anyway
not really used anywhere plus the upcoming weak show_board_info()
approach seems much superior.This reverts commit a9ad18c9d5fe2554753b0f9a52adfd5ebce61147.
Signed-off-by: Marcel Ziswiler
Reviewed-by: Tom Rini
Acked-by: Max Krummenacher -
Image header was checked twice.
Signed-off-by: Tomas Melin
Acked-by: Lokesh Vutla
Reviewed-by: Simon Glass -
Add check for FDT_MAGIC, otherwise also legacy images will be loaded as
a FIT. With this check in place, the loader works correct both
with legacy and FIT images.Signed-off-by: Tomas Melin
Acked-by: Lokesh Vutla
Reviewed-by: Simon Glass -
To send a parametrized command to the PHY over MDIO, we should write
the data first, the trigger the execution by the command register
write. Fix the access pattern in our MDIO write routine.
Apparently this doesn't really matter with the Realtek PHY on the
Pine64, but other PHYs (which require more setup) will choke on
the wrong order.
[Andre: add commit message]Signed-off-by: Philipp Tomsich
Signed-off-by: Andre Przywara
Acked-by: Jagan Teki -
Add board support for sun8i_r16 Nintendo NES Classic edition.
Signed-off-by: FUKAUMI Naoki
[jagan: Add commit message body]
Signed-off-by: Jagan Teki
Reviewed-by: Jagan Teki -
Add the description of the Toshiba TC58NVG2S0H SLC nand to the nand_ids
table so we can use the NAND ECC infos and the ONFI timings.Signed-off-by: Boris Brezillon
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
Signed-off-by: Hans de Goede -
And also remove it from scripts/config_whitelist.txt as the
Mele_M5_defconfig was the only one defining it.Signed-off-by: Hans de Goede
Acked-by: Ian Campbell
Reviewed-by: Jagan Teki -
Set CONFIG_SYS_MMC_MAX_DEVICE to 4 for sunxi SoC.
This define is needed in the API code.Signed-off-by: Emmanuel Vadot
Reviewed-by: Hans de Goede
Signed-off-by: Hans de Goede -
Currently, USB is forced-enabled for the sunxi familly, and there is no
way to disable it.However, USB takes a long time to initiliase, delaying the boot by up to
5 seconds (without any USB device attached!). This is a very long delay,
especially in cases where USB booting is not wanted at all, and where
the device is expected to boot relatively often (even in production).Change the way the dependencies are handled, by only forcibly selecting
USB when CONFIG_DISTRO_DEFAULTS ("defaults suitable for booting general
purpose Linux distributions") is set. This option defaults to y for the
sunxi familly, so the current default behaviour is kept unchanged. Users
interested in boot time and/or size will be able to disable this to
further disable USB.With USB disabled, the time spent in U-Boot before handing control to
the Linux kernel is about 1s now, down from ~5s (Nanopi Neo, sunxi H3).Signed-off-by: "Yann E. MORIN"
Cc: Ian Campbell
Cc: Hans De Goede
Reviewed-by: Hans de Goede
Signed-off-by: Hans de Goede -
Use the already available Kconfig option for AHCI. Tested on the
BananaPi.Signed-off-by: Jelle van der Waa
Reviewed-by: Hans de Goede
Signed-off-by: Hans de Goede
27 Nov, 2016
7 commits
-
We have all the building blocks now to run arbitrary efi applications
in travis. The most important one out there is grub2, so let's add
a simple test to verify that grub2 still comes up.Signed-off-by: Alexander Graf
-
Most of the time when running the sleep test in Travis for
the integratorcp_cm926ejs target I get errors like this:E assert 2.999901056289673 >= 3
The deviation is tiny, but fails the overall build result. Since
the sleep test is not terribly important as gate keeper for travis
tests, let's just exclude it for this board.Signed-off-by: Alexander Graf
Reviewed-by: Tom Rini -
Today we can compile a self-contained hello world efi test binary that
allows us to quickly verify whether the EFI loader framwork works.We can use that binary outside of the self-contained test case though,
by providing it to a to-be-tested system via tftp.This patch separates compilation of the helloworld.efi file from
including it in the u-boot binary for "bootefi hello". It also modifies
the efi_loader test case to enable travis to pick up the compiled file.
Because we're now no longer bloating the resulting u-boot binary, we
can enable compilation always, giving us good travis test coverage.Signed-off-by: Alexander Graf
Reviewed-by: Tom Rini -
Now that we have working network tests and a hello world efi application
built inside our tree, we can automatically test that efi binary running
inside of U-Boot.Signed-off-by: Alexander Graf
Reviewed-by: Simon Glass
Reviewed-by: Tom Rini -
When running in travis-ci, we want to pass environment configuration to
the tests. These reside in a path available through PYTHONPATH, so let's
define that one to point to the unit test repo.Signed-off-by: Alexander Graf
Reviewed-by: Tom Rini -
Some travis QEMU tests can transfer files between the build directory
and the guest U-Boot instance. For that to work, both need to have access
to the same directory.This patch puts the current build path into an environment variable, so
that the environment generating python scripts can extract it from there
and read the respective files.Signed-off-by: Alexander Graf
Reviewed-by: Tom Rini -
The network test currently downloads files at 0MB offset of RAM start.
This works for most ARM systems, but x86 has weird memory layout constraints
on the first MB of RAM.To not get caught into any of these, let's add a 4MB pad from start
of RAM to the default memory offset.Signed-off-by: Alexander Graf
Reviewed-by: Simon Glass
Reviewed-by: Tom Rini
26 Nov, 2016
19 commits
-
It should be 112M, to make rootfs start at 0x40000
Signed-off-by: Jacob Chen
Acked-by: Simon Glass -
This adds support for the Asus Chromebook Flip, an RK3288-based clamshell
device which can flip into 'tablet' mode. The device tree file comes from
Linux v4.8. The SDRAM parameters are for 4GB Samsung LPDDR3.Signed-off-by: Simon Glass
-
This adds support for the Asus Chromebit, and RK3288-based device designed
to plug directly into an HDMI monitor. The device tree file comes from
Linux v4.8.Signed-off-by: Simon Glass
-
It makes not sense using u8 to hold a value on a 32-bit or 64-bit machine.
It can only bloat the code by forcing the compiler to mask the value.
Change it to uint.Signed-off-by: Simon Glass
-
Update board_init() to increase the ARM clock to the maximum speed on
veyron boards. This makes quite a large difference in performance. With
this change, speed goes from about 750 DMIPS to 2720 DMIPs.Signed-off-by: Simon Glass
-
Add basic support for setting the ARM clock, since this allows us to run
at maximum speed in U-Boot. Currently only a single speed is supported
(1.8GHz).Signed-off-by: Simon Glass
-
The SDRAM settings are not common across all veyron models. Move the
current settings into Jerry's file.Signed-off-by: Simon Glass
-
Add a comment to indicate that we are not supporting the PWM regulator
yet.Signed-off-by: Simon Glass
-
At present we have a single rk3288-based Chromebook: chromebook_jerry. But
all such Chromebooks can use the same binary with only device-tree
differences. The family name is 'veyron', so rename the files accordingly.Also update the device-tree filename since this currently differs from
Linux.Signed-off-by: Simon Glass
-
Adjust jerry to use of-platdata like other rk3288 boards. This reduces the
SPL size enough that it boots again.Signed-off-by: Simon Glass
-
Check whether a display device is in use before using it. Add a comment as
to why two displays cannot currently be used at the same time.This allows us to remove the device-tree change that disables vopb on
jerry.Signed-off-by: Simon Glass
-
Mark a display as in use when display_enable() is called. This can avoid
a display being used by multiple video-output devices.Signed-off-by: Simon Glass
-
Sometimes the frame buffer is not a multiple of the cache line size.
Adjust the cache-flushing code to avoid cache warnings/errors in this
case.Signed-off-by: Simon Glass
-
This is an uncommon error but we may as well have a debug() message when
it happens.Signed-off-by: Simon Glass
-
This is not currently implemented. Add support for this so that the Chrome
OS EC can be used on jerry.Signed-off-by: Simon Glass
-
Allow this driver to be used with of-platdata on rk3288.
Signed-off-by: Simon Glass
-
Some boards may want to use these subsystems with of-platdata in SPL. Add
support for this by avoiding any device tree access in this case.Signed-off-by: Simon Glass
-
The current code assumes that the devices are ordered corresponding to
their alias value. But (for example) video1 can come before video0 in the
device tree.Correct this, by always looking for device 0 first. After that we can fall
back to finding the first available device.Signed-off-by: Simon Glass
