- Dec 21, 2023
-
-
Tom Rini authored
In order to make it easier to move on to dropping common.h from code directly, remove common.h inclusion from the rest of the header file which had been including it. Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Oct 24, 2023
-
-
Current code allows up to 3 MBR partitions without extended one. If more than 3 partitions are required, then extended partition(s) must be used. This commit allows up to 4 primary MBR partitions without the need for extended partition. Add mbr test unit. In order to run the test manually, mmc6.img file of size 12 MiB or greater is required in the same directory as u-boot. Test also runs automatically via ./test/py/test.py tool. Running mbr test is only supported in sandbox mode. Signed-off-by:
Alex Gendin <agendin@matrox.com> [ And due to some further changes for testing ] Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Prepare a rkmtd UCLASS in use for writing Rockchip boot blocks in combination with existing userspace tools and rockusb command. Signed-off-by:
Johan Jonker <jbx6244@gmail.com> Reviewed-by:
Kever Yang <kever.yang@rock-chips.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Oct 10, 2023
-
-
Print out the blkmap device type when showing partition header for a blkmap device. Signed-off-by:
Bin Meng <bmeng@tinylab.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
It's helpful to output the device uclass id for unknown devices during the debugging process. Signed-off-by:
Bin Meng <bmeng@tinylab.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Sep 24, 2023
-
-
This old patch was marked as deferred. Bring it back to life, to continue towards the removal of common.h Move this out of the common header and include it only where needed. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Sep 11, 2023
-
-
Rename disk_partition_type_uuid to disk_partition_type_guid. Provide function descriptions for the getter and setter. Fixes: bcd64542 ("part: Add accessors for struct disk_partition type_uuid") Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Aug 25, 2023
-
-
Add a little more debugging for the initial signature check. Drop the pointless check for NULL. Also set a log category while we are here. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This field is only present when a CONFIG is set. To avoid annoying #ifdefs in the source code, add accessors. Update all code to use it. Note that the accessor is optional. It can be omitted if it is known that the option is enabled. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
This field is only present when a CONFIG is set. To avoid annoying #ifdefs in the source code, add accessors. Update all code to use it. Note that the accessor is optional. It can be omitted if it is known that the option is enabled. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Some internal functions could do with a few comments, to explain what they do. Add these, to make the code easier to follow. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The dev_ prefix is a hangover from the pre-driver model days. The device is now a different thing, with driver model. Update the mac code to just use 'desc'. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The dev_ prefix is a hangover from the pre-driver model days. The device is now a different thing, with driver model. Update the iso code to just use 'desc'. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The dev_ prefix is a hangover from the pre-driver model days. The device is now a different thing, with driver model. Update the efi code to just use 'desc'. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The dev_ prefix is a hangover from the pre-driver model days. The device is now a different thing, with driver model. Update the dos code to just use 'desc'. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The dev_ prefix is a hangover from the pre-driver model days. The device is now a different thing, with driver model. Update the amiga code to just use 'desc'. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
The dev_ prefix is a hangover from the pre-driver model days. The device is now a different thing, with driver model. Update the partition code to just use 'desc', as is done with driver model. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Aug 22, 2023
-
-
Block devices with 4k sectors imply the MBR sectors are also 4k instead of regular 512B. Avoid hard-coding the 512B sector size and isntead read the current block device sector size from it, and if the sector size is larger than 512B, use the block device sector size. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Move part_create_block_devices() to blk uclass and unexpose the function. This can now be internal to the block uclass. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
The behavior of the part_blk_*() functions is now identical to disk_blk_*() functions, switch the former to the later. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
Check whether access is out of bounds of the partition and return an error. This way there is no danger of esp. write or erase outside of the confines of partition. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
Convert the read/write/erase offset from one within a partition to one within a block device, to correctly access the data on the block device for both write and erase operations. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
These two functions are basically identical, just call the blk_*() functions from disk_blk_*() functions. The only difference is that the disk_blk_*() functions have to use parent block device as the udevice implementing block device operations. Add documentation on what those functions really do. The documentation is not wrong even though it likely does look that way. The write/erase functions really do not take into account the partition offset. This will be fixed in the next patch. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
The disk_blk_read() can be simplified using blk_read(), the only things which needs to be handled are the read offset based on the partition properties, and the block device ops which are coming from the parent udevice, not the partition udevice. The later is currently not implemented correctly as far as I can tell, since the current code extracts block device descriptor from the parent udevice which is OK, but extracts block device operations from the partition udevice, which does not seem OK. Switching to the blk_read() fixes that too. The dev_get_blk() usage is simplified using UCLASS_PARTITION check. Add non-confusing documentation what this really does. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
if (device_get_uclass_id(dev) == UCLASS_PARTITION) is always true, because this disk_blk_read() function calls dev_get_blk() above and checks its return value for non-NULL. The dev_get_blk() performs the same device_get_uclass_id(dev) check and returns NULL if not UCLASS_PARTITION. Drop the duplicate check. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
- Jul 30, 2023
-
-
Heinrich Schuchardt authored
In SPL environment variables may not be enabled. Suggested-by:
Tom Rini <trini@konsulko.com> Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
- Jul 25, 2023
-
-
Since commit 56670d6f ("disk: part: use common api to lookup part driver") part_get_info_by_name_type() ignores the part_type parameter used to restrict the partition table type. omap_mmc_get_part_size() and part_get_info_by_name() are the only consumers. omap_mmc_get_part_size() calls with part_type = PART_TYPE_EFI because at the time of implementation a speed up could be gained by passing the partition table type. After 5 years experience without this restriction it looks safe to keep it that way. part_get_info_by_name() uses PART_TYPE_ALL. Move the logic of part_get_info_by_name_type() to part_get_info_by_name() and replace the function in omap_mmc_get_part_size(). Fixes: 56670d6f ("disk: part: use common api to lookup part driver") Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Jul 17, 2023
-
-
Adds part_driver_get_type() API which can be used to force a specific driver to be used when getting partition information instead of relying on auto detection. Signed-off-by:
Joshua Watt <JPEWhacker@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Set default y based on common BOOT_DEFAULTS instead of DISTRO_DEFAULTS. No change is intended, affected options is already implied for DISTRO and BOOTSTD due to BOOT_DEFAULTS imply DOS_PARTITION (USB_STORAGE), EFI_PARTITION and ISO_PARTITION. Fixes: a0c739c1 ("boot: Create a common BOOT_DEFAULTS for distro and bootstd") Signed-off-by:
Jonas Karlman <jonas@kwiboo.se> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Some devices have multiple partition types available on the same media. It is sometimes useful to see these to check that everything is working correctly. Provide a way to manually set the partition-table type, avoiding the auto-detection process. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
- Apr 05, 2023
-
-
Add a frontend for the blkmap subsystem. In addition to the common block device operations, this allows users to create and destroy devices, and map in memory and slices of other block devices. With that we support two primary use-cases: - Being able to "distro boot" from a RAM disk. I.e., from an image where the kernel is stored in /boot of some filesystem supported by U-Boot. - Accessing filesystems not located on exact partition boundaries, e.g. when a filesystem image is wrapped in an FIT image and stored in a disk partition. Signed-off-by:
Tobias Waldekranz <tobias@waldekranz.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Apr 03, 2023
-
-
Tom Rini authored
Per Takahiro Akashi this is not an equivalent rework, so revert it. This reverts commit d87bdb82. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Mar 30, 2023
-
-
Reduce the duplicated code slightly by using a helper function to handle the common code. This reduces the code size very slightly. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Mar 02, 2023
-
-
This is selected by PARTITION_UUIDS which has a separate option for SPL. Add an SPL option for LIB_UUID also, so that we can keep them consistent. Also add one for PARTITION_TYPE_GUID to avoid a build error in part_efi.c which wants to call a uuid function in SPL. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Feb 10, 2023
-
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_PARTITION_TYPE_GUID defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Feb 09, 2023
-
-
This converts 1 usage of this option to the non-SPL form, since there is no SPL_CMD_MBR defined in Kconfig Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Jan 23, 2023
-
-
If a disk has a bootable partition we are expected to use it to locate the boot files. Add a function to find it. To test this, update mmc1 to have two paritions, fixing up other tests accordingly. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Dec 02, 2022
-
-
Heinrich Schuchardt authored
blk_get_device_part_str() should always initialize all info fields including sys_ind. As a side effect the code is simplified. Replace '(0 ==' by '(!' to conform with Linux coding style. Fixes: 4d907025 ("sandbox: restore ability to access host fs through standard commands") Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Heiko Schocher <hs@denx.de>
-
- Nov 07, 2022
-
-
Simon Glass authored
Update the sandbox implementation to use UCLASS_HOST and adjust all the pieces to continue to work: - Update the 'host' command to use the new API - Replace various uses of UCLASS_ROOT with UCLASS_HOST - Disable test_eficonfig since it doesn't work (this should have a unit test to allow this to be debugged) - Update the blk test to use the new API - Drop the old header file Unfortunately it does not seem to be possible to split this change up further. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Oct 31, 2022
-
-
The use of 'block_dev' in this context is confusing, since it is not a pointer to a device, just to some information about it. Rename this to 'desc', as is more commonly used, since it is a block descriptor. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Heinrich Schuchardt <xypron.glplk@gmx.de>
-