Hi Masahisa,
On fre, jul 14, 2023 at 14:44, Masahisa Kojima
wrote:
> This series introduces the EFI_RAM_DISK_PROTOCOL implementation.
> The major purpose of this series is a preparation for EFI HTTP(S) boot.
>
> Now U-Boot can download the distro installer ISO image
> via wget or tftpboot comm
On tis, sep 26, 2023 at 16:43, Bin Meng wrote:
> At present if a device to map has a block size other than 512,
> the blkmap map process just fails. There is no reason why we
> can't just use the block size of the mapped device.
Won't this be very confusing to the user?
The blkmap device uses a
ps://docs.kernel.org/admin-guide/device-mapper/index.html
Tobias Waldekranz (8):
image: Fix script execution from FIT images with external data
cmd: blk: Allow generic read/write operations to work in sandbox
blk: blkmap: Add basic infrastructure
blk: blkmap: Add memory mapping support
blk
Update the script loading code to recognize when script data is stored
externally from the FIT metadata (i.e., built with `mkimage -E`).
Signed-off-by: Tobias Waldekranz
---
boot/image-board.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/boot/image-board.c b/boot/image
Ensure that the memory destination/source addresses of block
read/write operations are mapped in before access. Currently, this is
only needed on sandbox builds.
Signed-off-by: Tobias Waldekranz
---
cmd/blk_common.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff
vices. Subsequent changes will extend this to add
support for actual mappings.
Signed-off-by: Tobias Waldekranz
---
MAINTAINERS | 6 +
disk/part.c | 1 +
drivers/block/Kconfig| 18 ++
drivers/block/Makefile | 1 +
drivers/bloc
Allow a slice of RAM to be mapped to a blkmap. This means that RAM can
now be accessed as if it was a block device, meaning that existing
filesystem drivers can now be used to access ramdisks.
Signed-off-by: Tobias Waldekranz
---
drivers/block/blkmap.c | 106
Allow a slice of an existing block device to be mapped to a
blkmap. This means that filesystems that are not stored at exact
partition boundaries can be accessed by remapping a slice of the
existing device to a blkmap device.
Signed-off-by: Tobias Waldekranz
---
drivers/block/blkmap.c | 71
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
---
M
Verify that:
- Block maps can be created and destroyed
- Mappings aren't allowed to overlap
- Multiple mappings can be attached and be read/written from/to
Signed-off-by: Tobias Waldekranz
---
MAINTAINERS | 1 +
configs/sandbox_defconfig| 1 +
test/py/
Explain block maps by going through two common use-cases.
Signed-off-by: Tobias Waldekranz
---
MAINTAINERS | 1 +
doc/usage/blkmap.rst | 109 +++
doc/usage/index.rst | 1 +
3 files changed, 111 insertions(+)
create mode 100644 doc/usage
On ons, feb 01, 2023 at 13:20, Simon Glass wrote:
> Hi Tobias,
Hi Simon,
Thanks for the review!
> On Wed, 1 Feb 2023 at 11:10, Tobias Waldekranz wrote:
>>
>> blkmaps are loosely modeled on Linux's device mapper subsystem. The
>> basic idea is that you can creat
On fre, feb 03, 2023 at 17:20, Simon Glass wrote:
> Hi Tobias,
>
> On Fri, 3 Feb 2023 at 02:38, Tobias Waldekranz wrote:
>>
>> On ons, feb 01, 2023 at 13:20, Simon Glass wrote:
>> > Hi Tobias,
>>
>> Hi Simon,
>>
>> Thanks for the review!
On mån, feb 06, 2023 at 21:02, Simon Glass wrote:
> Hi Tobias,
>
> On Mon, 6 Feb 2023 at 01:30, Tobias Waldekranz wrote:
>>
>> On fre, feb 03, 2023 at 17:20, Simon Glass wrote:
>> > Hi Tobias,
>> >
>> > On Fri, 3 Feb 2023 at 02:38, Tobias Wal
Update the script loading code to recognize when script data is stored
externally from the FIT metadata (i.e., built with `mkimage -E`).
Signed-off-by: Tobias Waldekranz
Reviewed-by: Simon Glass
---
boot/image-board.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/boot
ps://docs.kernel.org/admin-guide/device-mapper/index.html
v1 -> v2:
- Change internal API to use device pointers
- Convert test suite from Python to C
- Various cosmetic fixes
Tobias Waldekranz (9):
image: Fix script execution from FIT images with external data
cmd: blk: Allow generic r
Allow a slice of an existing block device to be mapped to a
blkmap. This means that filesystems that are not stored at exact
partition boundaries can be accessed by remapping a slice of the
existing device to a blkmap device.
Signed-off-by: Tobias Waldekranz
---
drivers/block/blkmap.c | 71
Ensure that the memory destination/source addresses of block
read/write operations are mapped in before access. Currently, this is
only needed on sandbox builds.
Signed-off-by: Tobias Waldekranz
Reviewed-by: Simon Glass
---
cmd/blk_common.c | 15 +++
1 file changed, 11 insertions
Verify that:
- Block maps can be created and destroyed
- Mappings aren't allowed to overlap
- Multiple mappings can be attached and be read/written from/to
Signed-off-by: Tobias Waldekranz
---
MAINTAINERS | 1 +
configs/sandbox_defconfig | 1 +
test/dm/Makefile
Allow a slice of RAM to be mapped to a blkmap. This means that RAM can
now be accessed as if it was a block device, meaning that existing
filesystem drivers can now be used to access ramdisks.
Signed-off-by: Tobias Waldekranz
---
drivers/block/blkmap.c | 105
Explain block maps by going through two common use-cases.
Signed-off-by: Tobias Waldekranz
---
MAINTAINERS | 1 +
doc/usage/blkmap.rst | 111 +++
doc/usage/index.rst | 1 +
3 files changed, 113 insertions(+)
create mode 100644 doc/usage
vices. Subsequent changes will extend this to add
support for actual mappings.
Signed-off-by: Tobias Waldekranz
---
MAINTAINERS| 6 +
drivers/block/Kconfig | 18 ++
drivers/block/Makefile | 1 +
drivers/block/blk-uclass.c | 1 +
drivers/block/blkmap.c
Create a distinct EFI device path for each blkmap device.
Signed-off-by: Tobias Waldekranz
---
include/efi_loader.h | 4
lib/efi_loader/efi_device_path.c | 30 ++
2 files changed, 34 insertions(+)
diff --git a/include/efi_loader.h b/include
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
---
M
On fre, jan 24, 2025 at 13:39, Ilias Apalodimas
wrote:
> Heinrich, Tobias
>
> There's a slight problem that I forgot when commenting v2.
>
> Heinrich's idea of plugging this into blkmap is eventually the right
> thing to do.
>
> However, when I started coding this I only added the pmem memory as
On mån, jan 20, 2025 at 16:20, Sughosh Ganu wrote:
> Add information about the type of blkmap device in the blkmap
> structure. Currently, the blkmap device is used for mapping to either
> a memory based block device, or another block device (linear
> mapping). Put information in the blkmap struct
On tis, jan 21, 2025 at 00:55, Sughosh Ganu wrote:
> On Mon, 20 Jan 2025 at 21:50, Tobias Waldekranz wrote:
>>
>> On mån, jan 20, 2025 at 21:10, Sughosh Ganu wrote:
>> > On Mon, 20 Jan 2025 at 20:06, Tobias Waldekranz
>> > wrote:
>> >>
>
On mån, jan 20, 2025 at 19:30, Sughosh Ganu wrote:
> On Mon, 20 Jan 2025 at 17:55, Tobias Waldekranz wrote:
>>
>> On mån, jan 20, 2025 at 16:20, Sughosh Ganu wrote:
>> > Add information about the type of blkmap device in the blkmap
>> > structure. Current
On mån, jan 20, 2025 at 21:10, Sughosh Ganu wrote:
> On Mon, 20 Jan 2025 at 20:06, Tobias Waldekranz wrote:
>>
>> On mån, jan 20, 2025 at 19:30, Sughosh Ganu wrote:
>> > On Mon, 20 Jan 2025 at 17:55, Tobias Waldekranz
>> > wrote:
>> >>
>
On fre, feb 21, 2025 at 20:55, Ilias Apalodimas
wrote:
> Hi Sughosh
>
> This generally looks ok, but I don't love the idea of unconditionally
> preserving all slices regardless of their usage.
> Basically, if a user doesn't unmap that slice it will end in kernel
> memory. My fear is that someone
can then be used to take specific action based on
> the type of the blkmap slice.
>
> Signed-off-by: Sughosh Ganu
> ---
Reviewed-by: Tobias Waldekranz
sh Ganu
> ---
This turned out great!
Reviewed-by: Tobias Waldekranz
off-by: Sughosh Ganu
> ---
If a v6 is needed for some other reason (you seemed to indicate that),
then see my small comments below. Either way:
Reviewed-by: Tobias Waldekranz
> Changes since V4:
> * Reword the commit message
> * Add a helper function blkmap_get_preserved_pmem_slice()
&g
t; http://lists.denx.de/mailman/listinfo/u-boot
>
--
Hälsningar/Regards
Tobias Waldekranz
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
ices.com/c/a/Linux-For-Devices-Articles/Introduction-to-Das-UBoot-the-universal-open-source-bootloader/
>
> Now trying to figure out this using the above document... Not very
> clear... as to how to do this ... will read the README of u-boot ..
> Let me know !
> Thanks and Regards
> Va
35 matches
Mail list logo
