From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fed1rmmtao10.cox.net (fed1rmmtao10.cox.net [68.230.241.29]) by ozlabs.org (Postfix) with ESMTP id A985F67A6B for ; Thu, 3 Mar 2005 10:15:42 +1100 (EST) Date: Wed, 2 Mar 2005 16:15:30 -0700 From: Matt Porter To: Kumar Gala Message-ID: <20050302161530.D31614@cox.net> References: <20050302105201.C31614@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from kumar.gala@freescale.com on Wed, Mar 02, 2005 at 05:06:31PM -0600 Cc: ppcembed Subject: Re: PowerPC4xx Watchdog List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Mar 02, 2005 at 05:06:31PM -0600, Kumar Gala wrote: > Matt, > > [snip] > > > What do you see as the advantage to having a watchdog driver > > that uses the booke hardware watchdog facility over a generic > > timebase driven driver? > > I would think the watchdog would be useful in cases that the normal > decrementer exceptions gets disabled when MSR[EE] = 0. That's the only thing I can think of. I guess my question then is whether people think this is important enough in practice to have the hardware watchdog as an alternative. My guess is yes, but I don't have a strong opinion. -Matt