Date: Mon, 12 Apr 1999 20:06:31 +0900 From: Tomoaki NISHIYAMA <tomoaki@biol.s.u-tokyo.ac.jp> To: dfr@nlsystems.com Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: Any success with CirrusLogic 6729/6730??? Message-ID: <19990412200631T.tomoaki@moss.nibb.ac.jp> In-Reply-To: <Pine.BSF.4.05.9904121100510.74823-100000@herring.nlsystems.com> References: <Pine.BSF.4.05.9904121100510.74823-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Doug Rabson <dfr@nlsystems.com>
Subject: Re: Any success with CirrusLogic 6729/6730???
Date: Mon, 12 Apr 1999 11:03:44 +0100 (BST)
Message-ID: <Pine.BSF.4.05.9904121100510.74823-100000@herring.nlsystems.com>
dfr> This is not correct. A driver can be trivially split up into attachment
dfr> points and implementations. The interface definition system can actually
dfr> make this easier (IMHO of course). The mcclock driver in FreeBSD/alpha
dfr> (derived from the NetBSD driver) does this.
More precicely, is the split driver *dynamically* loadable?
The bus independent part, mcclock.c seemes to be linked statically,
putting aside whethere there is any merit to load the clock dynamically.
--------
Tomoaki Nishiyama
e-mail:tomoaki@biol.s.u-tokyo.ac.jp
Department of Biological Sciences,
Graduate School of Science, The University of Tokyo
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990412200631T.tomoaki>