From owner-freebsd-hackers Wed May 10 13:05:21 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA02815 for hackers-outgoing; Wed, 10 May 1995 13:05:21 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA02807 for ; Wed, 10 May 1995 13:05:14 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id QAA01278; Wed, 10 May 1995 16:05:42 -0400 From: Peter Dufault Message-Id: <199505102005.QAA01278@hda.com> Subject: Re: A question of downloading device drivers To: terry@cs.weber.edu (Terry Lambert) Date: Wed, 10 May 1995 16:05:42 -0400 (EDT) Cc: hm@altona.hamburg.com, freebsd-hackers@FreeBSD.org In-Reply-To: <9505101706.AA25853@cs.weber.edu> from "Terry Lambert" at May 10, 95 11:06:27 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 893 Sender: hackers-owner@FreeBSD.org Precedence: bulk Terry Lambert writes: > > > > > Really, it should be done with kernel level vnode I/O, just like the > > > > UFS disk quotas. > > > > Do you mean that the device driver code should access a file in the > > filesystem directly ? > > Yes; at attach time, it should do the download by reading a download > file from the root FS. Not at interrupt level, of course. > > You could actually delay until first open. Like a "touch" instance in > /etc/rc, or whatever. Or have a standard monitor daemon that monitors a request queue for service, and the drivers can send it requests. I thought about this when I was thinking about downloading the SCSI type drivers for drivers that you don't need until somewhere in /etc/rc. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267