Oh I see now, it is the efi loader that arms the watchdog not the kernel. 
Makes sense now.

On Thursday, February 1, 2018 at 1:43:07 AM UTC-5, Jan Kiszka wrote:
>
> [CC list again] 
>
> On 2018-02-01 00:47, Dmitri Toubelis wrote: 
> > Jan, 
> > 
> > Thanks for the reply. We use VMware images for internal testing, not for 
> > production. Right now I'm trying to figure it to what kernel modules 
> > those drivers that you currently support translate. So far I've got 
> > this: 
> > 
> > Intel Quark: CONFIG_ITCO_WDT=y 
> > Intel i6300esb: CONFIG_I6300ESB_WDT=y 
> > TCO: CONFIG_IE6XX_WDT=y 
> > 
> > (I assume they need to be compiled into the kernel, not loaded as 
> > modules.) 
>
> Nope, modules are fine as well. You just have to ensure that the kernel 
> driver takes over the watchdog prior to the expiry that efibootguard sets. 
>
> > 
> > Does this sound right? It would be nice to have this somewhere in 
> > README. 
>
> Feel free to send a patch the correlates the watchdog names with the 
> kernel config switches, and maybe also the hints that i6300esb is 
> available through QEMU/KVM (makes a nice test case) and that Quark as 
> well as the i6300esb watchdogs have a no-way-out feature while iTCO does 
> not (slightly less safe). 
>
> Thanks, 
> Jan 
>
> > 
> > -Dmitri 
> > 
> > ------ Original Message ------ 
> > From: "Jan Kiszka" <[email protected] <javascript:>> 
> > To: "Dmitri Toubelis" <[email protected] <javascript:>>; 
> "EFI Boot 
> > Guard" <[email protected] <javascript:>> 
> > Sent: 2018-01-31 4:18:15 PM 
> > Subject: Re: Watchod drivers support 
> > 
> >> On 2018-01-31 22:06, [email protected] <javascript:> 
> wrote: 
> >>> Hi, 
> >>> 
> >>> We build images with Yocto project for several different platforms 
> >>> including VMware and I'm trying to use efibootguard + swupdate for 
> >>> handling firmware updates. However, I'm having troubles with watchdog 
> >>> driver not being found. So, is there a way to have support for generic 
> >>> driver? Something like `softdog` that can be used on platforms with no 
> >>> hardware watchdog. 
> >> 
> >> Is VMware a testing or production target? In the former case, adding 
> >> some null watchdog might be fine (with a big-fat warning). In the 
> >> latter 
> >> case, you need to study if there is any virtual watchdog support on 
> >> VMware and write some driver. QEMU/KVM does have this, and 
> >> efi-bootguard 
> >> supports that. 
> >> 
> >> Jan 
> >> 
> >> -- 
> >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE 
> >> Corporate Competence Center Embedded Linux 
>
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE 
> Corporate Competence Center Embedded Linux 
>

-- 
You received this message because you are subscribed to the Google Groups "EFI 
Boot Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/efibootguard-dev/517baf4a-5b36-4299-bef0-bffa90ffa490%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to