uki: describe .efifw section#131
Conversation
|
My general feeling is that this is too generic? Is there no expectations to the embedded blob? Is this all an implementation detail? And if it only an implementation detail, how often would this actually be used by others beyond the usecase in the systemd PR? |
|
I think being generic here is fine. What matters is that the firmware is in some format acceptable to the hardware. We can't really say much about it this point. If this becomes established, we can add additional details later. |
|
Sorry for dropping the ball on this. Could you please rebase this? We really should get this landed. Please follow the wording of the .dtbauto stuff regarding the matching. |
|
@ani-sinha ping |
|
I've rebased and updated this in #216, PTAL |
Sorry I too forgot about this. Let me try and get to this in the next few days. |
@poettering So I was trying to update the doc and looked at the code. I see that chid_match() is only called for |
Add description for the firmware section (`.efifw`) in the specs.
|
We now have two versions of this PR. Since this one was earlier, I'll merge it. If subsequent changes should be done, let's do that later. |
I have started a PR here: systemd/systemd#42570 Still in draft, I want to see if I introduced any regressions or not. |
Add description for the firmware section (
.efifw) in the specs.See also systemd/systemd#35091