u-boot.git/fs, branch v2020.01-rc3 Unnamed repository; edit this file 'description' to name the repository. fs: add fs_get_type() for current filesystem type 2019-10-17T17:19:56+00:00 AKASHI Takahiro takahiro.akashi@linaro.org 2019-10-07T05:59:37+00:00 b7cd95627baac05b7023b014c802be309be636a0 This function is a variant of fs_get_type_name() and returns a filesystem type with which the current device is associated. We don't want to export fs_type variable directly because we have to take care of it consistently within fs.c. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de> 
This function is a variant of fs_get_type_name() and returns a filesystem
type with which the current device is associated.
We don't want to export fs_type variable directly because we have to take
care of it consistently within fs.c.

Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
fs: clean up around fs_type 2019-10-17T17:19:56+00:00 AKASHI Takahiro takahiro.akashi@linaro.org 2019-10-07T05:59:36+00:00 185aed7855573214794b13f20e597d36c6dc5760 fs_ls(), fs_mkdir() and fs_unlink() sets fs_type to FS_TYPE_ANY explicitly, but it is redundant as they call fs_close(). So just remove those lines. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de> 
fs_ls(), fs_mkdir() and fs_unlink() sets fs_type to FS_TYPE_ANY
explicitly, but it is redundant as they call fs_close().
So just remove those lines.

Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
fs: export fs_close() 2019-10-17T17:19:55+00:00 AKASHI Takahiro takahiro.akashi@linaro.org 2019-10-07T05:59:35+00:00 64f49eb7d0697b73fa271a69832069e591c07acc fs_close() closes the connection to a file system which opened with either fs_set_blk_dev() or fs_set_dev_with_part(). Many file system functions implicitly call fs_close(), e.g. fs_closedir(), fs_exist(), fs_ln(), fs_ls(), fs_mkdir(), fs_read(), fs_size(), fs_write() and fs_unlink(). So just export it. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de> 
fs_close() closes the connection to a file system which opened with
either fs_set_blk_dev() or fs_set_dev_with_part(). Many file system
functions implicitly call fs_close(), e.g. fs_closedir(), fs_exist(),
fs_ln(), fs_ls(), fs_mkdir(), fs_read(), fs_size(), fs_write()
and fs_unlink().
So just export it.

Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
fs: fat: get_contents() always returns -1 for errors 2019-10-11T23:05:14+00:00 Heinrich Schuchardt xypron.glpk@gmx.de 2019-09-12T17:19:30+00:00 f13683816b9d0aada2546343d77bb87925505c46 If out of memory, return -1 and not -ENOMEM from get_contents(). Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> 
If out of memory, return -1 and not -ENOMEM from get_contents().

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
fs: fat: treat invalid FAT clusters as errors 2019-10-11T23:05:14+00:00 Heinrich Schuchardt xypron.glpk@gmx.de 2019-09-12T17:19:29+00:00 c7a86d1645325697372b404f0b8cadac8a722ce9 When hitting an invalid FAT cluster while reading a file always print an error message and return an error code. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> 
When hitting an invalid FAT cluster while reading a file always print an
error message and return an error code.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
fat: FAT filesystem premature release of info struct. 2019-08-26T15:46:21+00:00 Martin Vystrčil martin.vystrcil@m-linux.cz 2019-08-20T20:18:30+00:00 d7af2a863017be1f5fd1b65a858ddc7e87d7b876 File was found on specified location. Info about file was read, but then immediately destroyed using 'free' call. As a result file size was set to 0, hence fat process didn't read any data. Premature 'free' call removed. Resources are freed right before function return. File is read correctly. Signed-off-by: Martin Vystrcil <martin.vystrcil@m-linux.cz> 
File was found on specified location. Info about file was read,
but then immediately destroyed using 'free' call. As a result
file size was set to 0, hence fat process didn't read any data.

Premature 'free' call removed. Resources are freed right before
function return. File is read correctly.

Signed-off-by: Martin Vystrcil <martin.vystrcil@m-linux.cz>
jffs2: remove unused code files 2019-08-20T16:20:33+00:00 Uwe Kleine-König u.kleine-koenig@pengutronix.de 2019-08-14T20:07:29+00:00 ad49488ffb0dd6357139f74a6b88c0b51e1ac215 I failed to find where these two files are used and a few test compile runs with JFFS2 enabled succeeded also without these. 
I failed to find where these two files are used and a few test compile
runs with JFFS2 enabled succeeded also without these.
cbfs: Rename camel-case variables 2019-08-18T13:54:10+00:00 Simon Glass sjg@chromium.org 2019-08-15T01:56:15+00:00 ad79d603aa68a7a523005ce694ee4b43efdf7382 Rename some camel-case variables to match U-Boot style. Camel case is not generally allowed in U-Boot. Rename this variable to fit in with the style. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Tested-by: Bin Meng <bmeng.cn@gmail.com> 
Rename some camel-case variables to match U-Boot style.

Camel case is not generally allowed in U-Boot. Rename this variable to fit
in with the style.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Tested-by: Bin Meng <bmeng.cn@gmail.com>
cbfs: Add functions to support multiple CBFSs 2019-08-18T13:54:10+00:00 Simon Glass sjg@chromium.org 2019-08-15T01:56:14+00:00 630b2f39ddabd43a27a98f0356b948df18e97d88 Sometimes an image has multiple CBFS. The current CBFS API is limited to handling only one at time. Also it keeps track of the CBFS internally in BSS, which does not work before relocation, for example. Add a few new functions to overcome these limitations. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Tested-by: Bin Meng <bmeng.cn@gmail.com> 
Sometimes an image has multiple CBFS. The current CBFS API is limited to
handling only one at time. Also it keeps track of the CBFS internally in
BSS, which does not work before relocation, for example.

Add a few new functions to overcome these limitations.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Tested-by: Bin Meng <bmeng.cn@gmail.com>
cbfs: Move result variable into the struct 2019-08-18T13:54:10+00:00 Simon Glass sjg@chromium.org 2019-08-15T01:56:13+00:00 c7f16934749b054ce1f0b75bd664d22af8b7c588 Move the result variable into the struct also, so that it can be used when BSS is not available. Add a function to read it. Note that all functions sill use the BSS version of the data. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Tested-by: Bin Meng <bmeng.cn@gmail.com> 
Move the result variable into the struct also, so that it can be used when
BSS is not available. Add a function to read it.

Note that all functions sill use the BSS version of the data.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Tested-by: Bin Meng <bmeng.cn@gmail.com>