diff options
| author | Stephen Warren <swarren@nvidia.com> | 2012-10-05 13:17:39 +0000 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2012-10-08 11:15:04 -0700 |
| commit | bd1a7e3034006ec121d35d745fd455212a56f7fd (patch) | |
| tree | 37a9db40647839234105a220d0f075acb30f9b9a /nand_spl/nand_boot.c | |
| parent | 03eecab9a1ba5f0226987a6ea58eb75a41d23408 (diff) | |
| download | u-boot-imx-bd1a7e3034006ec121d35d745fd455212a56f7fd.zip u-boot-imx-bd1a7e3034006ec121d35d745fd455212a56f7fd.tar.gz u-boot-imx-bd1a7e3034006ec121d35d745fd455212a56f7fd.tar.bz2 | |
FAT: check for partition 0 not 1 for whole-disk fs
The recent switch to use get_device_and_partition() from do_fat_ls()
broke the ability to access a FAT filesystem directly on a whole device;
FAT only works within a partition on a device.
This change makes e.g. "fatls mmc 0:0" work; explicitly requesting
partition ID 0 is something that get_device_and_partition() fully
supports. However, fat_register_device() expects partition ID 1 to be
used in the full-disk case; partition ID 1 was previously implicitly
specified when the user didn't actually specify a partition ID. Update
fat_register_device() to expect the correct ID.
This change does imply that if a user explicitly executes "fatls mmc 0:1"
then this will fail, and may be a change in behaviour.
Note that this still prevents "fatls mmc 0:auto" from working. The next
patch will fix that.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Diffstat (limited to 'nand_spl/nand_boot.c')
0 files changed, 0 insertions, 0 deletions