From owner-freebsd-ports  Fri Dec  3 13: 4:51 1999
Delivered-To: freebsd-ports@freebsd.org
Received: from ns.skylink.it (ns.skylink.it [194.177.113.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5B21215288; Fri,  3 Dec 1999 13:04:42 -0800 (PST)
	(envelope-from hibma@skylink.it)
Received: from skylink.it (va-154.skylink.it [194.185.55.154])
	by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA09971;
	Fri, 3 Dec 1999 22:04:34 +0100
Received: from localhost (localhost [127.0.0.1])
	by skylink.it (8.9.3/8.9.3) with ESMTP id PAA00309;
	Fri, 3 Dec 1999 15:36:48 +0100 (CET)
	(envelope-from hibma@skylink.it)
Date: Fri, 3 Dec 1999 15:36:47 +0100 (CET)
From: Nick Hibma <hibma@skylink.it>
X-Sender: n_hibma@henny.jrc.it
Reply-To: Nick Hibma <hibma@skylink.it>
To: FreeBSD CURRENT Mailing List <current@FreeBSD.ORG>,
	FreeBSD Ports Mailing List <ports@FreeBSD.ORG>
Subject: modules in ports
Message-ID: <Pine.BSF.4.20.9912031533180.268-100000@henny.jrc.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Has anyone ever devised a good way to put a module in a port?

Like so:

	module usio
		<support for Entrega serial devices>
	firmware in hex and source format.

They are strongly connected in that the API in the firmware might
change.


Maybe it is the more general question of how to relate modules to
other parts of the base system, like the kernel, downloadable firmware
files, etc.

Nick
--
hibma@skylink.it
n_hibma@freebsd.org                                          USB project
http://www.etla.net/~n_hibma/




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message