From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 21:06:35 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 99DD416A407 for ; Sat, 9 Dec 2006 21:06:35 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54A6E43CA3 for ; Sat, 9 Dec 2006 21:05:24 +0000 (GMT) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.13.8/8.13.8/ALCHEMY.FRANKEN.DE) with ESMTP id kB9L6TXT035929; Sat, 9 Dec 2006 22:06:29 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.13.8/8.13.8/Submit) id kB9L6Tg1035928; Sat, 9 Dec 2006 22:06:29 +0100 (CET) (envelope-from marius) Date: Sat, 9 Dec 2006 22:06:29 +0100 From: Marius Strobl To: Nick Hibma Message-ID: <20061209210629.GG86517@alchemy.franken.de> References: <20061209154559.B1408@localhost> <20061209185539.GA34399@alchemy.franken.de> <20061209201438.B42195@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061209201438.B42195@localhost> User-Agent: Mutt/1.4.2.2i Cc: FreeBSD CURRENT Mailing List 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: Sat, 09 Dec 2006 21:06:35 -0000 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. Marius