From owner-freebsd-hackers@FreeBSD.ORG  Sat Feb 17 00:01:12 2007
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 224D416A401
	for <freebsd-hackers@freebsd.org>; Sat, 17 Feb 2007 00:01:12 +0000 (UTC)
	(envelope-from youshi10@u.washington.edu)
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu
	[140.142.33.19])
	by mx1.freebsd.org (Postfix) with ESMTP id 5E97C13C428
	for <freebsd-hackers@freebsd.org>; Sat, 17 Feb 2007 00:01:11 +0000 (UTC)
	(envelope-from youshi10@u.washington.edu)
Received: from hymn06.u.washington.edu (hymn06.u.washington.edu
	[140.142.15.177])
	by mxout4.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP
	id l1H01AJv014331
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <freebsd-hackers@freebsd.org>; Fri, 16 Feb 2007 16:01:10 -0800
Received: from localhost (localhost [127.0.0.1])
	by hymn06.u.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP
	id l1H01ACr030827
	for <freebsd-hackers@freebsd.org>; Fri, 16 Feb 2007 16:01:10 -0800
X-Auth-Received: from [192.55.52.1] by hymn06.u.washington.edu via HTTP;
	Fri, 16 Feb 2007 16:01:10 PST
Date: Fri, 16 Feb 2007 16:01:10 -0800 (PST)
From: youshi10@u.washington.edu
To: freebsd-hackers@freebsd.org
In-Reply-To: <Pine.BSF.4.58.0702161812270.32166@niwun.pair.com>
Message-ID: <Pine.LNX.4.43.0702161601100.22743@hymn06.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-PMX-Version: 5.3.0.289146, Antispam-Engine: 2.5.0.283055,
	Antispam-Data: 2007.2.16.154933
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SUPERLONG_LINE 0.05,
	NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0,
	__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
Subject: Re: Examples on using RTC
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Feb 2007 00:01:12 -0000

On Fri, 16 Feb 2007, Mike Silbersack wrote:

>
> On Fri, 16 Feb 2007 youshi10@u.washington.edu wrote:
>
>>> /usr/ports/emulators/rtc
>>>
>>> regards,
>>>
>>> usleep
>>
>> Already using / looked at that. I'm looking for something more in-depth.
>> -Garrett
>
> The rtc port's sole purpose is to make the vmware port happier.  As you
> probably saw, it just fakes the functions of the linux rtc device.
>
> What other rtc functions do you need?  Almost everything the linux rtc
> device does can be accomplished by raising your system hz and using
> usleep/select.
>
> Mike "Silby" Silbersack

Hmmm.. well, I can't seem to find equivalent definitions for the Linux kernel macro RTC_PIE_OFF for instance and the emulators/rtc port isn't sufficiently documented for me to determine how the original author found out what signals RTC_PIE_ON and RTC_IRQP_* (whatever macro is also defined in /usr/local/include/linux/rtc.h).

-Garrett