Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
0 authors
  1. Jan 10, 2013
    • Simon Glass's avatar
      arm: Add CONFIG_DISPLAY_BOARDINFO_LATE to display board info on LCD · e2e3e2b1
      Simon Glass authored 
      
This option displays board info after stdio is running, so that it will
appear on the LCD. If it is displayed earlier, the board info will appear
on the serial console but not on the LCD.

Here follows a blow-by-blow description.

1a. Without CONFIG_DISPLAY_BOARDINFO_LATE, on serial:

U-Boot 2011.12-02550-g037e1c5-dirty (Nov 15 2012 - 14:29:42) for SMDK5250

CPU:   S5PC520 @ 1700MHz

Board: Google Snow, rev 0
I2C:   ready
DRAM:  2 GiB Elpida DDR3 @ 800MHz
MMC:   S5P MSHC0: 0, S5P MSHC1: 1
SF: Detected W25Q32 with page size 4 KiB, total 4 MiB
*** Warning - bad CRC, using default environment

In:    mkbp-keyb
Out:   lcd
Err:   lcd
Net:   No ethernet found.
Hit any key to stop autoboot:  0
SMDK5250 #

1b. Without CONFIG_DISPLAY_BOARDINFO_LATE, on LCD (note machine info
is missing):

In:    mkbp-keyb
Out:   lcd
Err:   lcd
Net:   No ethernet found.
Hit any key to stop autoboot:  0
SMDK5250 #

2a. With CONFIG_DISPLAY_BOARDINFO_LATE, on serial:

U-Boot 2011.12-02550-g037e1c5 (Nov 15 2012 - 14:27:40) for SMDK5250

CPU:   S5PC520 @ 1700MHz
I2C:   ready
DRAM:  2 GiB Elpida DDR3 @ 800MHz
MMC:   S5P MSHC0: 0, S5P MSHC1: 1
SF: Detected W25Q32 with page size 4 KiB, total 4 MiB
*** Warning - bad CRC, using default environment

Model: Google Snow
In:    mkbp-keyb
Out:   lcd
Err:   lcd
Net:   No ethernet found.
Hit any key to stop autoboot:  0
SMDK5250 #

2b. With CONFIG_DISPLAY_BOARDINFO_LATE, on LCD (note machine info is present):

Model: Google Snow
In:    mkbp-keyb
Out:   lcd
Err:   lcd
Net:   No ethernet found.
Hit any key to stop autoboot:  0
SMDK5250 #

Since the LCD is all that a typical user sees, it is useful to display
the model there.

We may be able to rearrange things some other way one day, but at
present this seems like a convenient way of getting the required
behaviour.

Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      e2e3e2b1
    • Simon Glass's avatar
      Document the CONFIG_DISPLAY_BOARDINFO option · b2b92f53
      Simon Glass authored 
      
Add a short note about this in the README.

Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      b2b92f53
    • Simon Glass's avatar
      arm: Add CONFIG_DELAY_ENVIRONMENT to delay environment loading · 06fd8538
      Simon Glass authored 
      This option delays loading of the environment until later, so that only the
default environment will be available to U-Boot.

This can address the security risk of untrusted data being used during boot.

Any time you load untrusted data you expose yourself to a bug in the
code. The attacker gets to choose the data so can sometimes carefully
craft it to exploit a bug. We try to avoid touching user-controlled
data during a verified boot unless strictly necessary. Since the
default environment is good enough in this case (or you would just
change it), this gets around the problem by just not loading the
environment.

When CONFIG_DELAY_ENVIRONMENT is defined, it is convenient to have a
run-time way of enabling loading of the environment. Add this to the
fdt as /config/delay-environment.

Note: This patch depends on http://patchwork.ozlabs.org/patch/194342/



Signed-off-by: default avatarDoug Anderson <dianders@chromium.org>
Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
Reviewed-by: default avatarDoug Anderson <dianders@chromium.org>
      06fd8538
    • Simon Glass's avatar
      arm: Move fdt check earlier so that board_early_init_f() can use it · eae78c34
      Simon Glass authored 
      
We want to use the fdt inside board_early_init_f(), so check for its
presence earlier in the pre-reloc init sequence.

So far ARM and microblaze are the only only ones that use
CONFIG_OF_CONTROL. Microblaze does not have the same init loop, and in
particular does not have the board_early_init_f() call. So a patch for
microblaze would have no meaning.

Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      eae78c34
    • Gabe Black's avatar
      arm: Keep track of the tlb size as well as its location · 724cdffc
      Gabe Black authored 
      
It may be necessary to know where the TLB area ends as well as where it
starts. This allows board code to complete a secure memory erase without
destroying the page tables.

Signed-off-by: default avatarGabe Black <gabeblack@google.com>
Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      724cdffc
    • Arun Mankuzhi's avatar
      arm: move flush_dcache_all() to just before disable cache · 44df5e8d
      Arun Mankuzhi authored 
      
In Cortex-A15 architecture, when we run cache invalidate
the cache clean operation executes automatically.
So if there are any dirty cache lines before disabling the L2 cache
these will be synchronized with the main memory when
invalidate_dcache_all() runs in the last part of U-boot

The two functions after flush_dcache_all is using the stack. So this
data will be on the cache. After disable when invalidate is called the
data will be flushed from cache to memory. This corrupts the stack in
invalida_dcache_all. So this change is required to avoid the u-boot
hang.

So flush has to be done just before clearing CR_C bit

Signed-off-by: default avatarArun Mankuzhi <arun.m@samsung.com>
Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      44df5e8d
  3. Jan 09, 2013
  5. Jan 08, 2013
  7. Jan 05, 2013
  9. Dec 27, 2012
  11. Dec 26, 2012
  13. Dec 22, 2012
  15. Dec 19, 2012
  17. Dec 18, 2012