linux-kernel - Re: [PATCH RFC] watchdog: add a new driver for VIA chipsets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4ecd075d.2YyTTCA13zxwZmwT%marc.vertes@sigfox.com>
Date:	Wed, 23 Nov 2011 15:46:53 +0100
From:	Marc Vertes <marc.vertes@...fox.com>
To:	wim@...ana.be, broonie@...nsource.wolfsonmicro.com
Cc:	w.sang@...gutronix.de, linux-watchdog@...r.kernel.org,
	linux-kernel@...r.kernel.org, HaraldWelte@...tech.com
Subject: Re: [PATCH RFC] watchdog: add a new driver for VIA chipsets

Wim Van Sebroeck <wim@...ana.be> wrote:

> Hi Marc,
>
> Coming back to now: if the driver incorporates the timer (like all other
> devices that can be started but not stopped once started do), then the start
> and stop functions are not empty.
> The timer (with the example that I prepared as part of the generic code) is
> not so difficult and will be a good solution for the time being. (Unless
> Dmitry Artamonow's comment about the fact that the watchdog could perhaps
> be started and stopped is correct... This should be investigated first imho).
>
The watchdog can not be started and stopped from the driver. This is
what I investigated first and found impossible (and explains why this
driver is still missing).

I do not fully understand yet what has to be done with the timer.

Regards,
--
Marc
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/