On Tue, 2017-07-18 at 15:42 -0700, Cal Sullivan wrote:
> >> Adding the signing portion like this would make my goal a bit harder.
> > The code can always be refactored, as long as the end-result is the same
> > (do_uefiapp_deploy puts signed bootx64.efi into the rootfs).
> Shouldn't be an issue.
On Tue, 2017-07-18 at 13:44 -0700, Cal Sullivan wrote:
> > -do_uefiapp_sign[depends] += "${PN}:do_uefiapp_deploy \
> > - sbsigntool-native:do_populate_sysroot"
> > +# This is intentionally split into different parts. This way,
> derived
> > +# classes or images can
On 07/18/2017 12:26 PM, Patrick Ohly wrote:
The original code in intel-iot-refkit allows to create more than one
UEFI combo app and uses that to create one for removable media and one
for fixed media (after installation), with different boot=PARTUUID=xxx
parameters. This way, an installed
The original code in intel-iot-refkit allows to create more than one
UEFI combo app and uses that to create one for removable media and one
for fixed media (after installation), with different boot=PARTUUID=xxx
parameters. This way, an installed image never ended up booting from
the install media.
