Date: Sat, 9 Dec 2006 19:55:39 +0100 From: Marius Strobl <marius@alchemy.franken.de> To: Nick Hibma <nick@van-laarhoven.org> Cc: FreeBSD CURRENT Mailing List <current@freebsd.org> Subject: Re: mk48txx Message-ID: <20061209185539.GA34399@alchemy.franken.de> In-Reply-To: <20061209154559.B1408@localhost> References: <20061209154559.B1408@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 09, 2006 at 03:47:54PM +0100, Nick Hibma wrote: > What devices are needed to make the mk48txx driver work? It contains a > watchdog and I am trying to verify a few changes to that part. But > whatever I do I bump into errors. > > device mk48txx > > shouts about clock_if.h not being found. Adding > > device genclock > > produces duplicate symbols (resettodr). > 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. > > 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. Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061209185539.GA34399>