Date: Wed, 23 Mar 2005 14:24:54 -0500 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-hackers@FreeBSD.org Cc: "Devon H. O'Dell " <dodell@offmyserver.com> Subject: Re: Ziatech 5503 watchdog driver Message-ID: <200503231424.54258.jhb@FreeBSD.org> In-Reply-To: <20050319090402.GZ51688@smp500.sitetronics.com> References: <20050318160528.GQ51688@smp500.sitetronics.com> <20050319084341.GY51688@smp500.sitetronics.com> <20050319090402.GZ51688@smp500.sitetronics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 19 March 2005 04:04 am, Devon H. O'Dell wrote: > On Sat, Mar 19, 2005 at 09:43:41AM +0100, Devon H. O'Dell wrote: > > On Sat, Mar 19, 2005 at 09:02:15AM +0100, Devon H. O'Dell wrote: > > > On Fri, Mar 18, 2005 at 03:55:53PM -0700, Warner Losh wrote: > > > > > I'm busy writing a Ziatech 5503 watchdog driver for FreeBSD (and > > > > > porting all the watchdog stuff to DragonFly BSD) and Plan 9. For my > > > > > driver, I have no way to identify that the system has the driver, > > > > > so I wanted to make it conditional on > > > > > > Rather, I have no way to identify that the system has the device :). > > > > AHA! But I have finally found something that will make my life a > > little easier, I think. I just noticed a read only register with a > > default value of 0x80 and tested it. It returns 0x80. Is this enough > > to test on / probe for? > > > > --Devon > > Sorry, hate replying to myself. Turns out the value here is variable. > > Assuming I cannot find anything to identify the system, can I simply > attach the driver if it is enabled in the configuration file? Yes. See the identify routines for things like apm and pmtimer for examples. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503231424.54258.jhb>