From: "Ng, Wei Tee"
Upgrade intel-gpu-tools recipe to version 1.19
Signed-off-by: Ng, Wei Tee
---
.../{intel-gpu-tools_1.18.bb => intel-gpu-tools_1.19.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename
In the future more secure boot implementations will be offered, with
each one needing the signing method. Instead of repeating a forty line
block of code across several recipes, just use a configurable bbclass.
Signed-off-by: California Sullivan
---
On 07/18/2017 01:58 PM, Patrick Ohly wrote:
On Tue, 2017-07-18 at 13:32 -0700, Cal Sullivan wrote:
On 07/16/2017 11:26 PM, Patrick Ohly wrote:
On Fri, 2017-07-14 at 19:11 -0700, California Sullivan wrote:
I'm not sure why I never tried just signing the kernel and systemd-boot,
but it works.
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 Tue, 2017-07-18 at 13:32 -0700, Cal Sullivan wrote:
>
> On 07/16/2017 11:26 PM, Patrick Ohly wrote:
> > On Fri, 2017-07-14 at 19:11 -0700, California Sullivan wrote:
> >> I'm not sure why I never tried just signing the kernel and systemd-boot,
> >> but it works. If either one is not signed, it
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
On 07/16/2017 11:26 PM, Patrick Ohly wrote:
On Fri, 2017-07-14 at 19:11 -0700, California Sullivan wrote:
I'm not sure why I never tried just signing the kernel and systemd-boot,
but it works. If either one is not signed, it causes gives a security
violation error.
A con of this
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.
On Thu, 2017-07-06 at 18:30 -0700, California Sullivan wrote:
> +python do_uefiapp() {
> +import glob, re
> +from subprocess import check_call
> +
> +build_dir = d.getVar('B')
> +deploy_dir_image = d.getVar('DEPLOY_DIR_IMAGE')
> +
> +cmdline = '%s/cmdline.txt' % build_dir
> +