Re: wdat_wdt: access width inconsistency

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 11 Feb 2020 18:37:53 +0200, Mika Westerberg wrote:
> On Tue, Feb 11, 2020 at 05:25:33PM +0100, Jean Delvare wrote:
> > On Tue, 11 Feb 2020 15:59:44 +0200, Mika Westerberg wrote:  
> > > If the default timeout is short then that might happen but I think WDAT
> > > spec had some "reasonable" lower limit.  
> > 
> > Could you please point me to the WDAT specification? Somehow my web
> > search failed to spot it.  
> 
> You can find it here:
> 
>   http://msdn.microsoft.com/en-us/windows/hardware/gg463320.aspx
> 
> Most of the ACPI related documents not part of the spec itself are
> listed in the following page:
> 
>   https://uefi.org/acpi

Great, thanks for the info.

As I read the specification, it is mandatory to have a timeout >= 5
minutes *if* the watchdog is enabled at boot time. Otherwise the 5
minutes is only a recommendation. I wouldn't be surprised if some
hardware vendors do not initialize the timeout value and assume the OS
will do it for them. Odds are that Windows does that.

Thanks again,
-- 
Jean Delvare
SUSE L3 Support



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux