From owner-freebsd-current@FreeBSD.ORG Mon Dec 11 06:12:08 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9E7616A47E for ; Mon, 11 Dec 2006 06:12:08 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2683D43CA7 for ; Mon, 11 Dec 2006 06:10:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kBB6AelQ084169; Sun, 10 Dec 2006 23:10:41 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 10 Dec 2006 23:11:37 -0700 (MST) Message-Id: <20061210.231137.-1749707382.imp@bsdimp.com> To: marius@alchemy.franken.de From: "M. Warner Losh" In-Reply-To: <20061209210629.GG86517@alchemy.franken.de> References: <20061209185539.GA34399@alchemy.franken.de> <20061209201438.B42195@localhost> <20061209210629.GG86517@alchemy.franken.de> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 10 Dec 2006 23:10:41 -0700 (MST) Cc: nick@van-laarhoven.org, current@freebsd.org Subject: Re: mk48txx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2006 06:12:08 -0000 In message: <20061209210629.GG86517@alchemy.franken.de> Marius Strobl writes: : On Sat, Dec 09, 2006 at 08:19:29PM +0100, Nick Hibma wrote: : > >On platforms which don't use genclock(4), yet, sys/kern/subr_rtc.c : > >will clash with the MD RTC driver, f.e. with sys/i386/isa/clock.c. : > >So far mk48txx(4) is only used on FreeBSD/sparc64 and requires : > >eeprom(4) and genclock(4) to be actually usable. For compile- : > >testing changes to mk48txx(4) on another platform, cross-compiling : > >the sparc64 GENERIC is probably the simplest approach. : > >AFAICT the reset pin of the MK48Txx watchdog is only connected to : > >something in Sun E250, E450 and Exx00 but one can actually test : > >the watchdog support in the driver in any sun4u machine where : > >eeprom(4) attaches by observing the MK48TXX_FLAGS_WDF bit. : > : > Sun? Enlightning. : > : > >>What's it do anyway? No manpage. : > > : > >I didn't get around to adapt the NetBSD mk48txx.4 so far but : > >the user point of view is covered by eeprom.4. : > : > I would like to suggest that you spend two hours putting in a very basic : > man page. Rip out the guts of an existing one and fill in the blanks : > with a few details. It makes the driver so much more finished and it : > might just be that someone updates the page. : : I favor having no man page over having something incomplete : or inadequate like f.e. esp.4 or bus_space.9 as IMO wrong : information can confuse way more and leaves a worse impression : than no information at all. bus_space.9 isn't incomplete. The problem is that it is too complete and general, if anything. It is hard to penetrate. Warner