mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-11 13:56:30 +00:00
67bc59df05
When passing a data buffer back from a function, it is not always clear who owns the buffer, i.e. who is responsible for freeing the memory used. An example of this is where multiple files are decompressed from the firmware image, using a temporary buffer for reading (since the compressed data has to live somewhere) and producing a temporary or permanent buffer with the resuilts. Where the firmware image can be memory-mapped, as on x86, the compressed data does not need to be buffered, but the complexity of having a buffer which is either allocated or not, makes the code hard to understand. Introduce a new 'abuf' which supports simple buffer operations: - encapsulating a buffer and its size - either allocated with malloc() or not - able to be reliably freed if necessary - able to be converted to an allocated buffer if needed This simple API makes it easier to deal with allocated and memory-mapped buffers. Signed-off-by: Simon Glass <sjg@chromium.org> |
||
|---|---|---|
| .. | ||
| abuf.c | ||
| asn1.c | ||
| cmd_ut_lib.c | ||
| efi_device_path.c | ||
| efi_image_region.c | ||
| getopt.c | ||
| hexdump.c | ||
| lmb.c | ||
| longjmp.c | ||
| Makefile | ||
| rsa.c | ||
| sscanf.c | ||
| string.c | ||
| strlcat.c | ||
| test_aes.c | ||
| test_crypt.c | ||
| test_errno_str.c | ||
| test_print.c | ||