From owner-freebsd-current@FreeBSD.ORG  Sat Dec  9 18:55:42 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E7E4016A40F
	for <current@freebsd.org>; Sat,  9 Dec 2006 18:55:42 +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 E6B8F43C9E
	for <current@freebsd.org>; Sat,  9 Dec 2006 18:54:36 +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
	kB9ItdAd034641; Sat, 9 Dec 2006 19:55:39 +0100 (CET)
	(envelope-from marius@alchemy.franken.de)
Received: (from marius@localhost)
	by alchemy.franken.de (8.13.8/8.13.8/Submit) id kB9ItdV2034640;
	Sat, 9 Dec 2006 19:55:39 +0100 (CET) (envelope-from marius)
Date: Sat, 9 Dec 2006 19:55:39 +0100
From: Marius Strobl <marius@alchemy.franken.de>
To: Nick Hibma <nick@van-laarhoven.org>
Message-ID: <20061209185539.GA34399@alchemy.franken.de>
References: <20061209154559.B1408@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20061209154559.B1408@localhost>
User-Agent: Mutt/1.4.2.2i
Cc: FreeBSD CURRENT Mailing List <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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Dec 2006 18:55:43 -0000

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