- 21 8月, 2017 1 次提交
-
-
由 Simon Glass 提交于
Some of these were missed in the conversion. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 16 8月, 2017 3 次提交
-
-
由 Simon Glass 提交于
The load() methods have inconsistent behaviour on error. Some of them load an empty default environment. Some load an environment containing an error message. Others do nothing. As a step in the right direction, have the method return an error code. Then the caller could handle this itself in a consistent way. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Add a name to the driver and use that instead of the global variable declared by each driver. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
Move over to use a the master implementation of the location drivers, with each method calling out to the appropriate driver. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
- 15 8月, 2017 4 次提交
-
-
由 Simon Glass 提交于
Set up a location driver for each supported environment location. At present this just points to the global functions and is not used. A later patch will switch this over to use private functions in each driver. There are several special cases here in various drivers to handle peculiarities of certain boards: 1. Some boards define CONFIG_ENV_IS_IN_FAT and CONFIG_SPL_ENV_SUPPORT but do not actually load the environment in SPL. The env load code was optimised out before but with the driver, it is not. Therefore a special case is added to env/fat.c. The correct fix (depending on board testing might be to disable CONFIG_SPL_ENV_SUPPORT. 2. A similar situations happens with CONFIG_ENV_IS_IN_FLASH. Some boards do not actually load the environment in SPL, so to reduce code size we need to drop that code. A similar fix may be possible with these boards, or it may be possible to adjust the environment CONFIG settings. Added to the above is that the CONFIG_SPL_ENV_SUPPORT option does not apply when the environment is in flash. Obviously the above has been discovered through painful and time-consuming trial and error. Hopefully board maintainers can take a look and figure out what is actually needed. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
We want to use this name for all environment drivers. Update the nand driver to use a more specific name. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
At present we have three states for the environment, numbered 0, 1 and 2. Add an enum to record this to avoid open-coded values. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
About a quarter of the files in common/ relate to the environment. It seems better to put these into their own subdirectory and remove the prefix. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
- 23 7月, 2017 1 次提交
-
-
由 Fiach Antaw 提交于
The env_nand, env_mmc and env_ubi implementations all implement redundancy using an identical serial-number scheme. This commit migrates them to use the implementation in env_common, which is functionally identical. Signed-off-by: NFiach Antaw <fiach.antaw@uqconnect.edu.au> Reviewed-by: NTom Rini <trini@konsulko.com>
-
- 12 7月, 2017 1 次提交
-
-
由 Grygorii Strashko 提交于
As part of preparation for nand DM conversion the new API has been introduced to remove direct access to nand_info array. So, use it here instead of accessing to nand_info array directly. Signed-off-by: NGrygorii Strashko <grygorii.strashko@ti.com>
-
- 16 8月, 2016 1 次提交
-
-
由 Tom Rini 提交于
Now that nand_info[] is an array of pointers we need to ensure that it's been populated prior to use. We may for example have ENV in NAND set in configurations that run on boards with and without NAND (where default env is fine enough, such as omap3_beagle and beagleboard (NAND) vs beagle xM (no NAND)). Fixes: b616d9b0 ("nand: Embed mtd_info in struct nand_chip") Cc: Scott Wood <oss@buserror.net> Signed-off-by: NTom Rini <trini@konsulko.com> Acked-by: NScott Wood <oss@buserror.net>
-
- 04 6月, 2016 2 次提交
-
-
由 Scott Wood 提交于
nand_info[] is now an array of pointers, with the actual mtd_info instance embedded in struct nand_chip. This is in preparation for syncing the NAND code with Linux 4.6, which makes the same change to struct nand_chip. It's in a separate commit due to the large amount of changes required to accommodate the change to nand_info[]. Signed-off-by: NScott Wood <oss@buserror.net>
-
由 Scott Wood 提交于
This typedef serves no purpose other than causing confusion with struct nand_chip. Signed-off-by: NScott Wood <oss@buserror.net>
-
- 12 9月, 2015 1 次提交
-
-
由 Simon Glass 提交于
Now that we have a new header file for cache-aligned allocation, we should move the stack-based allocation macro there also. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 19 5月, 2015 1 次提交
-
-
由 Tim Harvey 提交于
The readenv() implementation of env_nand uses the mtd layer which is unnecessary overhead in SPL when we already have a nand_spl_load_image() function that doesn't need it. Using this instead eliminates the need to provide a mtd_read for SPL env as well as reduces code (4KB savings in IMX6 SPL). Signed-off-by: NTim Harvey <tharvey@gateworks.com> Acked-by: NScott Wood <scottwood@freescale.com>
-
- 23 11月, 2014 1 次提交
-
-
由 Masahiro Yamada 提交于
U-Boot has never cared about the type when we get max/min of two values, but Linux Kernel does. This commit gets min, max, min3, max3 macros synced with the kernel introducing type checks. Many of references of those macros must be fixed to suppress warnings. We have two options: - Use min, max, min3, max3 only when the arguments have the same type (or add casts to the arguments) - Use min_t/max_t instead with the appropriate type for the first argument Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NPavel Machek <pavel@denx.de> Acked-by: NLukasz Majewski <l.majewski@samsung.com> Tested-by: NLukasz Majewski <l.majewski@samsung.com> [trini: Fixup arch/blackfin/lib/string.c] Signed-off-by: NTom Rini <trini@ti.com>
-
- 25 10月, 2014 1 次提交
-
-
由 Jeroen Hofstee 提交于
Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
-
- 22 3月, 2014 1 次提交
-
-
由 Marek Vasut 提交于
Implement env_export() wrapper, so that all implementers of saveenv() don't have to call hexport_r(), crc32() etc. sequence . This trims down a bit of code duplication. Signed-off-by: NMarek Vasut <marex@denx.de>
-
- 15 10月, 2013 1 次提交
-
-
由 Wolfgang Denk 提交于
Signed-off-by: NWolfgang Denk <wd@denx.de>
-
- 23 8月, 2013 1 次提交
-
-
由 Phil Sutter 提交于
Without this patch, when the currently chosen environment to be written has bad blocks, saveenv fails completely. Instead, when there is redundant environment fall back to the other copy. Environment reading needs no adjustment, as the fallback logic for incomplete writes applies to this case as well. Signed-off-by: NPhil Sutter <phil.sutter@viprinet.com>
-
- 24 7月, 2013 1 次提交
-
-
由 Wolfgang Denk 提交于
Signed-off-by: NWolfgang Denk <wd@denx.de> [trini: Fixup common/cmd_io.c] Signed-off-by: NTom Rini <trini@ti.com>
-
- 10 4月, 2013 1 次提交
-
-
由 Tom Rini 提交于
We make these two functions take a size_t pointer to how much space was used on NAND to read or write the buffer (when reads/writes happen) so that bad blocks can be accounted for. We also make them take an loff_t limit on how much data can be read or written. This means that we can now catch the case of when writing to a partition would exceed the partition size due to bad blocks. To do this we also need to make check_skip_len count not just complete blocks used but partial ones as well. All callers of nand_(read|write)_skip_bad are adjusted to call these with the most sensible limits available. The changes were started by Pantelis and finished by Tom. Signed-off-by: NPantelis Antoniou <panto@antoniou-consulting.com> Signed-off-by: NTom Rini <trini@ti.com>
-
- 06 4月, 2013 1 次提交
-
-
由 Tom Rini 提交于
Wolfgang requested this be reverted and Rob agreed after further discussion. This was a symptom of a larger problem we need to deal with. This reverts commit 60d7d5a6. Signed-off-by: NTom Rini <trini@ti.com>
-
- 03 4月, 2013 1 次提交
-
-
由 Rob Herring 提交于
Most of the various environment functions create CONFIG_ENV_SIZE buffers on the stack. At least on ARM and PPC which have 4KB stacks, this can overflow the stack if we have large environment sizes. So move all the buffers off the stack to static buffers. Signed-off-by: NRob Herring <rob.herring@calxeda.com>
-
- 23 2月, 2013 2 次提交
-
-
由 Phil Sutter 提交于
Calculating the checksum of incompletely read data is useless. Signed-off-by: NPhil Sutter <phil.sutter@viprinet.com> [scottwood@freescale.com: minor formatting fix] Signed-off-by: NScott Wood <scottwood@freescale.com>
-
由 Phil Sutter 提交于
The single message is misleading, since there is no equivalent success note when reading the other copy succeeds. Instead, warn if one of the redundant copies could not be loaded and emphasise on the error when reading both fails. Signed-off-by: NPhil Sutter <phil.sutter@viprinet.com>
-
- 14 12月, 2012 1 次提交
-
-
由 Joe Hershberger 提交于
When printing all variables with env print, don't print variables that begin with '.'. If env print is called with a '-a' switch, then include variables that begin with '.' (just like the ls command). Variables printed explicitly will be printed even without the -a. Signed-off-by: NJoe Hershberger <joe.hershberger@ni.com>
-
- 19 9月, 2012 1 次提交
-
-
由 Stephen Warren 提交于
The third parameter to ALLOC_CACHE_ALIGN_BUFFER is not size (as named), but rather count (number of elements of the type to allocate). The current code ends up allocating one copy of env_t for each byte in its size, which quite possibly ends up overflowing RAM. This fixes a bug in commit 3801a15f "env_nand: align NAND buffers". Reported-by: NPrabhakar Lad <prabhakar.csengg@gmail.com> Signed-off-by: NStephen Warren <swarren@nvidia.com> Reported-by: NPrabhakar Lad <prabhakar.lad@ti.com>
-
- 02 9月, 2012 1 次提交
-
-
由 Stephen Warren 提交于
This allows cache flush/invalidate operations to succeed on the buffers. Signed-off-by: NStephen Warren <swarren@nvidia.com> Acked-by: NSimon Glass <sjg@chromium.org> Acked-by: NScott Wood <scottwood@freescale.com>
-
- 05 1月, 2012 1 次提交
-
-
由 Igor Grinberg 提交于
env_get_char_spec() function is duplicated across multiple environment files. Remove the duplication by providing a default implementation. Add "weak" declaration, so the default implementation can be overridden. Signed-off-by: NIgor Grinberg <grinberg@compulab.co.il>
-
- 06 12月, 2011 1 次提交
-
-
由 Thomas Weber 提交于
Signed-off-by: NThomas Weber <weber@corscience.de>
-
- 22 11月, 2011 3 次提交
-
-
由 Igor Grinberg 提交于
Cleanup the env_nand.c checkpatch warnings, errors and coding style. Signed-off-by: NIgor Grinberg <grinberg@compulab.co.il>
-
由 Igor Grinberg 提交于
Extract all extern declarations for environment out of c files into the environment.h header. Signed-off-by: NIgor Grinberg <grinberg@compulab.co.il>
-
由 Igor Grinberg 提交于
Extract all extern declarations for default_environment[] out of c files into the environment.h header. Signed-off-by: NIgor Grinberg <grinberg@compulab.co.il> Cc: Stefan Roese <sr@denx.de> Acked-by: NStefan Roese <sr@denx.de>
-
- 08 11月, 2011 1 次提交
-
-
由 Wolfgang Denk 提交于
New syntax: env export [-t | -b | -c] [-s size] addr [var ...] With this change it is possible to provide a list of variables names that shall be exported. Whenno arguments are given, the whole environment gets exported. NOTE: The new handling of the "size" argument means a change to the user API. Signed-off-by: NWolfgang Denk <wd@denx.de>
-
- 25 5月, 2011 1 次提交
-
-
由 Daniel Hobi 提交于
Commit 30486322 (nand erase: .spread, .part, .chip subcommands) added a new field to struct nand_erase_options, but forgot to update common/env_nand.c. Depending on the stack state and bad block distribution, saveenv() can thus erase more than CONFIG_ENV_RANGE bytes which may corrupt the following NAND sectors/partitions. Signed-off-by: NDaniel Hobi <daniel.hobi@schmid-telecom.ch> Signed-off-by: NScott Wood <scottwood@freescale.com>
-
- 09 2月, 2011 1 次提交
-
-
由 Scott Wood 提交于
Previously, uninitialized stack space was being referenced. Signed-off-by: NScott Wood <scottwood@freescale.com>
-
- 03 2月, 2011 1 次提交
-
-
由 Alexander Holler 提交于
When redundand environments are used the serial needs to get increased, otherwise the old one will still be used. Signed-off-by: NAlexander Holler <holler@ahsoftware.de>
-
- 18 12月, 2010 1 次提交
-
-
由 Mike Frysinger 提交于
The non-reentrant versions of the hashtable functions operate on a single shared hashtable. So if two different people try using these funcs for two different purposes, they'll cause problems for the other. Avoid this by converting all existing hashtable consumers over to the reentrant versions and then punting the non-reentrant ones. Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
- 07 12月, 2010 1 次提交
-
-
由 Steve Sakoman 提交于
The nand-read function returns an error code if correctable errors have occurred. This is not desirable, since the errors have been corrected! This patch switches to the nand_read_skip_bad function which does not return an error code if the errors are correctable. Signed-off-by: NSteve Sakoman <steve.sakoman@linaro.org> Acked-by: NScott Wood <scottwood@freescale.com>
-