Hi Josh,
> >Now we only need someone that can look at the CONFIG_4xx cases still :-)
>
> It seems the FSL watchdog is much more flexible than the one found in 4xx
> cores. On 4xx, you basically have 4 static choices that represent specific
> times determined by the clock frequency. I'm concerne
On Thu, Aug 27, 2009 at 01:14:58PM +0200, Wim Van Sebroeck wrote:
>Hi Chris,
>
>> The WDIOC_SETTIMEOUT argument is supposed to be a "seconds" value.
>> However, the book E wdt currently treats it as a "period" which is
>> interpreted in a board-specific way.
>>
>> This patch allows the user to pas
Hi Chris,
> The WDIOC_SETTIMEOUT argument is supposed to be a "seconds" value.
> However, the book E wdt currently treats it as a "period" which is
> interpreted in a board-specific way.
>
> This patch allows the user to pass in a "seconds" value and the driver
> will set the smallest timeout tha
The WDIOC_SETTIMEOUT argument is supposed to be a "seconds" value.
However, the book E wdt currently treats it as a "period" which is
interpreted in a board-specific way.
This patch allows the user to pass in a "seconds" value and the driver
will set the smallest timeout that is at least as large
