15 Mar, 2016
3 commits
-
This is a device number, and we want to use 'dev' to mean a driver model
device. Rename the member.Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
Tested-by: Stephen Warren -
Rename this function to blk_get_device_part_str(). This is a better name
because it makes it clear that the function returns a block device and
parses a string.Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
Tested-by: Stephen Warren -
Use 'struct' instead of a typdef. Also since 'struct block_dev_desc' is long
and causes 80-column violations, rename it to struct blk_desc.Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
Tested-by: Stephen Warren
12 Sep, 2015
1 commit
-
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: Simon Glass
23 Nov, 2014
1 commit
-
Change the internal FAT functions to use loff_t for offsets.
Signed-off-by: Suriyan Ramasami
Acked-by: Simon Glass
[trini: Fix fs/fat/fat.c for min3 updates]
Signed-off-by: Tom Rini
09 Aug, 2014
1 commit
-
We must ensure the buffer we read the env into is aligned or we may get
warnings later on.Signed-off-by: Tom Rini
08 Jul, 2014
1 commit
-
Use get_device_and_partition() is better since:
1. It will call the device initialize function internally. So we can
remove the mmc intialization code to save many lines.
2. It is used by fatls/fatload/fatwrite. So saveenv & load env should
use it too.
3. It can parse the "D:P", "D", "D:", "D:auto" string to get correct
device and partition information by run-time.Also we remove the FAT_ENV_DEVICE and FAT_ENV_PART. We use a string:
FAT_ENV_DEVICE_AND_PART.
For at91sam9m10g45ek, it is "0". That means use device 0 and if:
a)device 0 has no partition table, use the whole device as a FAT file
system.
b)device 0 has partittion table, use the partition #1.Refer to the commit: 10a37fd7a4 for details of device & partition string.
Signed-off-by: Josh Wu
Reviewed-by: Stephen Warren
22 Mar, 2014
1 commit
-
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: Marek Vasut
15 Oct, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
24 Jul, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
06 Apr, 2013
1 commit
-
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 60d7d5a63189c9f77a190c9965861dc15482c2d0.
Signed-off-by: Tom Rini
03 Apr, 2013
1 commit
-
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: Rob Herring
14 Dec, 2012
1 commit
-
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: Joe Hershberger
27 Sep, 2012
2 commits
-
env_fat has several checkpatch warnings - clean those up.
Signed-off-by: Igor Grinberg
-
env_fat and env_remote have an implementation of env_get_char_spec()
function that is not different than the default.
Remove the duplicated code.Signed-off-by: Igor Grinberg
31 Mar, 2012
1 commit
-
The following must be defined:
CONFIG_ENV_IS_IN_FAT
Enable this saving environment to FAT.FAT_ENV_INTERFACE
Interface the FAT resides on (e.g. mmc).FAT_ENV_DEVICE
The interface device number (e.g. 0 for mmc0)FAT_ENV_PART
The device part (e.g. 1 for mmc0:1)FAT_ENV_FILE
The filename of the environment file.Author: Maximilian Schwerin
Removed dead DEBUG comment.
Signed-off-by: Wolfgang Denk
