Date: Sat, 9 Dec 2006 20:19:29 +0100 (CET) From: Nick Hibma <nick@van-laarhoven.org> To: Marius Strobl <marius@alchemy.franken.de> Cc: FreeBSD CURRENT Mailing List <current@freebsd.org> Subject: Re: mk48txx Message-ID: <20061209201438.B42195@localhost> In-Reply-To: <20061209185539.GA34399@alchemy.franken.de> References: <20061209154559.B1408@localhost> <20061209185539.GA34399@alchemy.franken.de>
index | next in thread | previous in thread | raw e-mail
> 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. Nickhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061209201438.B42195>