dfcd7f2160
Several boards used different ways to specify the size of the protected area when enabling flash write protection for the sectors holding the environment variables: some used CONFIG_ENV_SIZE and CONFIG_ENV_SIZE_REDUND, some used CONFIG_ENV_SECT_SIZE, and some even a mix of both for the "normal" and the "redundant" areas. Normally, this makes no difference at all. However, things are different when you have to deal with boards that can come with different types of flash chips, which may have different sector sizes. Here we may have to chose CONFIG_ENV_SECT_SIZE such that it fits the biggest sector size, which may include several sectors on boards using the smaller sector flash types. In such a case, using CONFIG_ENV_SIZE or CONFIG_ENV_SIZE_REDUND to enable the protection may lead to the case that only the first of these sectors get protected, while the following ones aren't. This is no real problem, but it can be confusing for the user - especially on boards that use CONFIG_ENV_SECT_SIZE to protect the "normal" areas, while using CONFIG_ENV_SIZE_REDUND for the "redundant" area. To avoid such inconsistencies, I changed all sucn boards that I found to consistently use CONFIG_ENV_SECT_SIZE for protection. This should not cause any functional changes to the code. Signed-off-by: Wolfgang Denk <wd@denx.de> Cc: Paul Ruhland Cc: Pantelis Antoniou <panto@intracom.gr> Cc: Stefan Roese <sr@denx.de> Cc: Gary Jennejohn <garyj@denx.de> Cc: Dave Ellis <DGE@sixnetio.com> Acked-by: Stefan Roese <sr@denx.de> |
||
|---|---|---|
| .. | ||
| Makefile | ||
| Pt1000_temp_data.h | ||
| README.kbd | ||
| auto_update.c | ||
| cmd_trab.c | ||
| config.mk | ||
| flash.c | ||
| lowlevel_init.S | ||
| memory.c | ||
| rs485.c | ||
| rs485.h | ||
| trab.c | ||
| trab_fkt.c | ||
| tsc2000.c | ||
| tsc2000.h | ||
| u-boot.lds | ||
| vfd.c | ||
README.kbd
The TRAB keyboard implementation is similar to that for LWMON and R360MPI boards. The only difference concerns key naming. There are 4 keys on TRAB: 1, 2, 3, 4. 1) The "kbd" command provides information about the current state of the keys. For example, TRAB # kbd Keys: 1 0 1 0 means that keys 1 and 3 are pressed. The keyboard status is also stored in the "keybd" environment variable. In this example we get keybd=1010 2) The "preboot" variable is set according to current environment settings and keys pressed. This is an example: TRAB # setenv magic_keys XY TRAB # setenv key_magicX 12 TRAB # setenv key_cmdX echo ## Keys 1 + 2 pressed ##\;echo TRAB # setenv key_magicY 13 TRAB # setenv key_cmdY echo ## Keys 1 + 3 pressed ##\;echo Here "magic_keys=XY" means that the "key_magicX" and "key_magicY" variables will be checked for a match. Each variable "key_magic*" defines a set of keys. In the our example, if keys 1 and 3 are pressed during reset, then "key_magicY" matches, so the "preboot" variable will be set to the contents of "key_cmdY": preboot=echo ## Keys 1 + 3 pressed ##;echo 3) The TRAB board has optional modem support. When a certain key combination is pressed on the keyboard at power-on, the firmware performs the necessary initialization of the modem and allows for dial-in. The key combination is specified in the "include/configs/trab.h" file. For example: #define CONFIG_MODEM_KEY_MAGIC "23" means that modem will be initialized if and only if both keys 2, 3 are pressed. Note that the format of this string is similar to the format of "key_magic*" environment variables described above.