Skip to content

fdt/builder: enforce BE datatypes on add_prop_array #777

@chris-oo

Description

@chris-oo

add_prop_array doesn't have any checks that the data is Big Endian. FDT requires that data is BE. Current usage kind of gets away with it, as we pass empty ranges or just u8 unformed entropy data.

Perhaps we should use zerocopy BE byte types for add_prop_array and also perhaps prop_array_iter?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions