mk48txx

[M. Warner Losh]

In message: <20061209210629.GG86517 at alchemy.franken.de>
            Marius Strobl <marius at alchemy.franken.de> 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