10 Oct, 2014
3 commits
-
At least on OMAP, init_sata() no longer performs scsi_scan()
so we must do it explicitly here.Cc: Dan Murphy
Signed-off-by: Roger Quadros -
Commit 294b91a5817147d4b7f47be2ac69bac2a1f26491 moved initr_malloc
earlier than initr_unlock_ram_in_cache. This causes issue on T4240.
It may be related to locked L1 d-cache and unlocked L2 cache. D-
cache could and should be unlock earlier for normal operation.This patch moves initr_unlock_ram_in_cache before initr_malloc. It
has been verified on the following boards, in which only T4240QDS
suffered and has been since fixed: T4240QDS, T2080QDS, P5040DS,
P4080DS, MPC8572DS, MPC8536DS, MPC8641HPCN, B4860QDS.Signed-off-by: York Sun
CC: Scott Wood
CC: Simon Glass
Acked-by: Simon Glass -
On a couple of platforms I've tripped over long PXE append lines overflowing
this array, due to having CONFIG_SYS_CBSIZE == 256. When doing preseeded Debian
installs it's pretty trivial to exceed that.Since the symptom can be a silent hang or a crash add a check. Of course the
affected boards would also need an increased CBSIZE to actually work.Note that due to the printing of the final bootargs string CONFIG_SYS_PBSIZE
also needs to be sufficiently large.Signed-off-by: Ian Campbell
[trini: Use %zd not %d in printf for all args]
Signed-off-by: Tom Rini
07 Oct, 2014
2 commits
-
Fix a trivial conflict in dw_mmc.c after talking with Marek.
Conflicts:
drivers/mmc/dw_mmc.cSigned-off-by: Tom Rini
06 Oct, 2014
7 commits
-
Like many platforms, the Altera socfpga platform requires that the
preloader be "signed" in a certain way or the built-in boot ROM will
not boot the code.This change automatically creates an appropriately signed preloader
from an SPL image.The signed image includes a CRC which must, of course, be generated
with a CRC generator that the SoCFPGA boot ROM agrees with otherwise
the boot ROM will reject the image.Unfortunately the CRC used in this boot ROM is not the same as the
Adler CRC in lib/crc32.c. Indeed the Adler code is not technically a
CRC but is more correctly described as a checksum.Thus, the appropriate CRC generator is added to lib/ as crc32_alt.c.
Signed-off-by: Charles Manning
Signed-off-by: Marek Vasut
Cc: Chin Liang See
Cc: Dinh Nguyen
Cc: Albert Aribaud
Cc: Tom Rini
Cc: Wolfgang Denk
Cc: Pavel Machek
Acked-by: Pavel MachekV2: - Zap unused constant
- Explicitly print an error message in case of error
- Rework the hdr_checksum() function to take the *header directly
instead of a plan buffer pointer -
Use the new force parameter to make the stdio_deregister succeed, replacing
stdin with a nulldev, and assume that the usb keyboard will come back after
the reset.Signed-off-by: Hans de Goede
-
In some cases we really want to move forward with a deregister, add a force
parameter to allow this, and replace the dev with a nulldev in this case.Signed-off-by: Hans de Goede
-
We now always properly deregister the keyboard before calling
drv_usb_kbd_init(), so we can drop the check for already being registered.Signed-off-by: Hans de Goede
-
We need to call usb_kbd_deregister() before calling usb_stop().
usbkbd's stdio_dev->priv points to the usb_device, and usb_kbd_testc
dereferences usb_device->privptr.usb_stop zeros usb_device, leaving usb_device->privptr NULL, causing
bad things (tm) to happen once control returns to the main loop and
usb_kbd_testc gets called.Calling usb_kbd_deregister() avoids this. Note that we do not allow
the "usb reset" to continue when the deregister fails. This will be fixed
in a later patch.For the same reasons always fail "usb stop" if the usb_kbd_deregister() fails,
even in the force path. This can happen when CONFIG_SYS_STDIO_DEREGISTER is
not set.Signed-off-by: Hans de Goede
-
ENODEV menas no usb keyboard was registered, threat this as a successful
usb_kbd_deregister.Signed-off-by: Hans de Goede
-
Signed-off-by: Hans de Goede
03 Oct, 2014
2 commits
-
sub-command 'bootpart-resize' check for argc == 4,
it will retrun CMD_RET_FAILURE when argc value not matched.but bootpart-resize's maxarg is 3, which means you never execute
this sub-command successfully.fix it by change bootpart-resize maxarg to 4.
Signed-off-by: wally.yeh
Cc: Wolfgang Denk
Cc: Pierre Aubert
Acked-by: Pantelis Antoniou -
The code to set the MMC partition uses an weak function to obtain the
correct partition number. Use that instead of the compile-time default
when deciding whether it needs to switch back.Fixes: 6e7b7df4df43574 ("env_mmc: support env partition setup in runtime")
Signed-off-by: Peter A. Bigot
Acked-by: Dmitry Lifshitz
Acked-by: Pantelis Antoniou
27 Sep, 2014
2 commits
-
In preparation for changing the error handling in this code for driver
model, move it into its own function.Reviewed-by: Jagannadha Sutradharudu Teki
Signed-off-by: Simon Glass
26 Sep, 2014
1 commit
25 Sep, 2014
14 commits
-
of_bus_default_count_cells can be used to get the #address-cells
and #size-cells defined by the current node's parent node. This
is required when using of_read_number to read from FDT nodes that
can be 32 or 64 bytes depending on values defined by the parent.Signed-off-by: Arnab Basu
CC: Scott Wood -
This is being done so that it can be used outside 'fdt_support.c'. Making
life more convenient when reading device node properties that can be 32
or 64 bits long.Signed-off-by: Arnab Basu
Cc: Scott Wood -
[1] Move driver/core/, driver/input/ and drivers/input/ entries
from the top Makefile to drivers/Makefile[2] Remove the conditional by CONFIG_DM in drivers/core/Makefile
because the whole drivers/core directory is already selected
by CONFIG_DM in the upper level[3] Likewise for CONFIG_DM_DEMO in drivers/demo/Makefile
[4] Simplify common/Makefile - both CONFIG_DDR_SPD and
CONFIG_SPD_EEPROM are boolean macros so they can directly
select objectsSigned-off-by: Masahiro Yamada
Acked-by: Marek Vasut -
The arg_off() and arg_off_size() update the 'current NAND
device' variable (dev). This is then used when assigning the
(nand_info_t*)nand value. Place the assignment after the
arg_off(_size) calls to prevent using incorrect (nand_info_t*)
nand value.Signed-off-by: Rostislav Lisovy
-
Since CONFIG_CMD_IMPORTENV is defined in config_cmd_defaults.h,
it should be enabled for all the boards except bf506f-ezkit
that undefs it explicitely.Signed-off-by: Masahiro Yamada
Acked-by: Simon Glass
Tested-by: Simon Glass -
Since CONFIG_CMD_GO is defined in config_cmd_defaults.h
(and no board undefs it its own header), it can be moved to
Kconfig with the default value "y".Signed-off-by: Masahiro Yamada
Acked-by: Simon Glass
Tested-by: Simon Glass -
Since CONFIG_CMD_EXPORTENV is defined in config_cmd_defaults.h,
it should be enabled for all the boards except bf506f-ezkit
that undefs it explicitely.Signed-off-by: Masahiro Yamada
Acked-by: Simon Glass
Tested-by: Simon Glass -
Since CONFIG_CMD_CRC32 is defined in config_cmd_defaults.h,
it is enabled for all the boards except the ones undefining it
explicitly:
kwb
tseries_mmc
tseries_nand
tseries_spi
vct_platinum_onenand_small
vct_platinum_small
vct_platinumavc_onenand_small
vct_platinumavc_small
vct_premium_onenand_small
vct_premium_smallThe default value of this config option should be "y" and
"# CONFIG_CMD_CRC32 is not set" should be added for those exceptions.Signed-off-by: Masahiro Yamada
Acked-by: Simon Glass -
CONFIG_CMD_BOOTM is defined in config_cmd_defaults.h
which is forcebly included from each board.
So, the default value of "config CMD_BOOTM" should be "y".For some boards undefining it (bf506f-ezkit, controlcenterd_TRAILBLA,
controlcenterd_TRAILBLAZER_DEVELOP, controlcenterd_TRAILBLAZER),
"# CONFIG_CMD_BOOTM is not set" should be added to their defconfig.Signed-off-by: Masahiro Yamada
Acked-by: Simon Glass -
This would be useful to start moving various config options.
Signed-off-by: Masahiro Yamada
Acked-by: Simon Glass
Tested-by: Simon Glass -
This is not supported properly on sandbox, and interferes with running
tests, since when a test script is piped in, some commands will call
ctrlc() which will drop characters from the test script.Signed-off-by: Simon Glass
-
- add capability to "fastboot flash" with sparse format images
Signed-off-by: Steve Rae
Acked-by: Lukasz Majewski -
- update static function
- additional debugging statements
- update "fastboot command" information
- add missing include file
- update spellingSigned-off-by: Steve Rae
-
- add support for 'fastboot flash' command for eMMC devices
Signed-off-by: Steve Rae
24 Sep, 2014
1 commit
-
Currently, CONFIG_SPL_SPI_* #defines are used for controlling SPI boot in
SPL. These #defines do not allow the user to select SPI mode for the SPI flash
(there's no CONFIG_SPL_SPI_MODE, so the SPI mode is hardcoded in
spi_spl_load.c), and duplicate information already provided by
CONFIG_SF_DEFAULT_* #defines.Kill CONFIG_SPL_SPI_*, and use CONFIG_SF_DEFAULT_* instead.
Cc: Tom Rini
Cc: Marek Vasut
Cc: Sudhakar Rajashekhara
Cc: Lokesh Vutla
Cc: Vitaly Andrianov
Cc: Lars Poeschel
Cc: Bo Shen
Cc: Hannes Petermaier
Cc: Michal Simek
Acked-by: Marek Vasut
Signed-off-by: Nikita Kiryanov
Reviewed-by: Jagannadha Sutradharudu Teki
17 Sep, 2014
8 commits
-
gd->fdt_blob is used for FDT control of U-Boot.
If CONFIG_OF_CONTROL is not defined, it is useless.Signed-off-by: Masahiro Yamada
Cc: Simon Glass
Acked-by: Simon Glass -
This was breaking the build for some boards:
MPC8536DS MPC8536DS_36BIT MPC8536DS_SDCARD MPC8536DS_SPIFLASH qemu-ppce500Include only these features for some PPC boards if the configuration for MultiProcessor
is enabled.Signed-off-by: Gabriel Huau
Cc: Tom Rini
Cc: York Sun
Acked-by: York Sun -
update to provide usable implementation to U-Boot
Signed-off-by: Steve Rae
-
- port dprintf() to debug()
- update formattingSigned-off-by: Steve Rae
-
- remove unnecessary functions
Signed-off-by: Steve Rae
-
Add original file (pristine) from :
https://www.codeaurora.org/cgit/quic/la/kernel/lk/plain/app/aboot/aboot.c?h=master
[3b5092d20bd15a7a2879c13e9f64acc48d04af2d]Signed-off-by: Steve Rae
-
Signed-off-by: Masahiro Yamada
Acked-by: Simon Glass -
There are two ways to run into handle_exception, run command 'kgdb' and
encounter a breakpoint which triggers exception handling.The origin source code only saves regs when first run command 'kgdb'.
Take the following for example, When run 'kgdb', regs is saved to entry_regs.
When run 'bootz', regs is not saved. However, if we set a breakpoint, then
continue. When breakpoint is reached, run `quit`, and Now return to the
instruction which follows kgdb, but not bootz.This may cause errors. So,
save regs for each handle_exception call to return to the correct place.
Example:
Target | Host
=>kgdb | (gdb)b bootz
| (gdb)c
=>bootz |
| (gdb)Here stop because of breakpoint
| (gdb)qSigned-off-by: Peng Fan
