On 8/29/21 2:44 PM, Nikita Ermakov wrote:
Btw, I have a minor suggestion [1] for your patch.
AFAIK hartid terminology and /chosen/boot-hartid are RISC-V specifics.
So, I think, we should not emit the warning and change DTB with a null
boot-hartid value. If get_hartid is not defined then we should
Btw, I have a minor suggestion [1] for your patch.
AFAIK hartid terminology and /chosen/boot-hartid are RISC-V specifics. So,
I think, we should not emit the warning and change DTB with a null
boot-hartid value. If get_hartid is not defined then we should, probably,
just skip this boot-hartid thing
