Searched hist:"51735 ae0" (Results 1 – 4 of 4) sorted by relevance
/openbmc/u-boot/lib/efi_loader/ |
H A D | Kconfig | 51735ae0 Wed May 11 11:25:48 CDT 2016 Alexander Graf <agraf@suse.de> efi_loader: Add bounce buffer support Some hardware that is supported by U-Boot can not handle DMA above 32bits. For these systems, we need to come up with a way to expose the disk interface in a safe way. This patch implements EFI specific bounce buffers. For non-EFI cases, this apparently was no issue so far, since we can just define our environment variables conveniently. Signed-off-by: Alexander Graf <agraf@suse.de>
|
H A D | efi_disk.c | 51735ae0 Wed May 11 11:25:48 CDT 2016 Alexander Graf <agraf@suse.de> efi_loader: Add bounce buffer support Some hardware that is supported by U-Boot can not handle DMA above 32bits. For these systems, we need to come up with a way to expose the disk interface in a safe way. This patch implements EFI specific bounce buffers. For non-EFI cases, this apparently was no issue so far, since we can just define our environment variables conveniently. Signed-off-by: Alexander Graf <agraf@suse.de>
|
H A D | efi_memory.c | 51735ae0 Wed May 11 11:25:48 CDT 2016 Alexander Graf <agraf@suse.de> efi_loader: Add bounce buffer support Some hardware that is supported by U-Boot can not handle DMA above 32bits. For these systems, we need to come up with a way to expose the disk interface in a safe way. This patch implements EFI specific bounce buffers. For non-EFI cases, this apparently was no issue so far, since we can just define our environment variables conveniently. Signed-off-by: Alexander Graf <agraf@suse.de>
|
/openbmc/u-boot/include/ |
H A D | efi_loader.h | 51735ae0 Wed May 11 11:25:48 CDT 2016 Alexander Graf <agraf@suse.de> efi_loader: Add bounce buffer support Some hardware that is supported by U-Boot can not handle DMA above 32bits. For these systems, we need to come up with a way to expose the disk interface in a safe way. This patch implements EFI specific bounce buffers. For non-EFI cases, this apparently was no issue so far, since we can just define our environment variables conveniently. Signed-off-by: Alexander Graf <agraf@suse.de>
|