From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 20 06:03:57 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E32B16A4CE for ; Sun, 20 Mar 2005 06:03:57 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id B175F43D49 for ; Sun, 20 Mar 2005 06:03:56 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j2K62CfO086551; Sat, 19 Mar 2005 23:02:12 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 19 Mar 2005 23:02:30 -0700 (MST) Message-Id: <20050319.230230.35850068.imp@bsdimp.com> To: dodell@offmyserver.com From: "M. Warner Losh" In-Reply-To: <20050319080215.GX51688@smp500.sitetronics.com> References: <20050318160528.GQ51688@smp500.sitetronics.com> <20050318.155553.41699848.imp@bsdimp.com> <20050319080215.GX51688@smp500.sitetronics.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: Ziatech 5503 watchdog driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 06:03:57 -0000 In message: <20050319080215.GX51688@smp500.sitetronics.com> "Devon H. O'Dell " writes: : 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 :). : : > > options ZT5503 : > : > That's not a good enough reason to make it an option, it should really : > be a device. Users that want it can add it to their kernel config. : > In fact, they'd have to add it either way, so why make it weird for : > them. : > : > Put this device on the ISA bus, give it an identify routine that : > always adds it (this isn't GENERIC safe, but since there's no way to : > know the device is there, you are stuck with that). : : OK. I don't know a hell of a lot about how the ISA bus works, though : I suppose that I remember that things using the old SB 16 cards : (Wolfenstein, anyone?) would simply probe various I/O ports. :-) Yes. Usually one does try to probe for things, but the devices must be cooperative. : Unfortunately, in my case, there are really no board specific I/O : registers that will give me information I can detect (or so it seems : from the manufacturer's manuals), though I am going to write a : couple of tests today to read some of these registers and see if : there is any useful information contained within them which I : might use to probe. Right. That's too bad, but with somehardware that's what you get. : Assuming no useful information exists, is it enough to let the : device attach regardless if the user has : : device zt5503 : : in the configuration file? Maxime suggested that I use device hints : to gather the port and such. Where should I put these hints? NOTES? /boot/device.hints and also NOTES. : If I understand correctly, to hook this up into the build, I will : still have a line in files which will look something like: : : dev/ziatech/zt5503.c optional zt5503 Yes. : Hm, Ziatech is now Performance Technologies. Should that perhaps be : dev/pt then instead? We generally don't have directories for manufacturers. : Thanks for the help! No problem. Warner