| 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
| ||
|
Message-ID: <20140409134121.7ce4e7a4@alan.etchedpixels.co.uk> Date: Wed, 9 Apr 2014 13:41:21 +0100 From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk> To: Guenter Roeck <linux@...ck-us.net> Cc: David Cohen <david.a.cohen@...ux.intel.com>, wim@...ana.be, tglx@...utronix.de, mingo@...hat.com, hpa@...or.com, x86@...nel.org, linux-kernel@...r.kernel.org, linux-watchdog@...r.kernel.org, Eric Ernst <eric.ernst@...el.com> Subject: Re: [PATCH 1/2] watchdog: add Intel MID watchdog driver support On Tue, 08 Apr 2014 17:17:34 -0700 Guenter Roeck <linux@...ck-us.net> wrote: > On 04/08/2014 01:59 PM, David Cohen wrote: > > Add initial Intel MID watchdog driver support. > > > > This driver is an initial implementation of generic Intel MID watchdog > > driver. Currently it supports Intel Merrifield platform. > > How does this compare with the existing SCU watchdog driver > (intel_scu_watchdog) ? The watchdog IPC message (0xf8) seems > to be the same, so there must be at least some overlap. > Would it be possible to have just one watchdog driver > serving the different SCU based devices ? There are enough differences that we'd end up with one spaghetti driver full of conditionals rather than two simple clean drivers. Alan -- 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/
Powered by blists - more mailing lists