From owner-freebsd-arch Tue Oct 8 7:57:19 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5359E37B401 for ; Tue, 8 Oct 2002 07:57:18 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67BE743E6A for ; Tue, 8 Oct 2002 07:57:17 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g98Ev5pS028319; Tue, 8 Oct 2002 16:57:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "David Christensen" Cc: arch@FreeBSD.ORG Subject: Re: Device Driver Overview In-Reply-To: Your message of "Tue, 08 Oct 2002 07:34:12 PDT." Date: Tue, 08 Oct 2002 16:57:05 +0200 Message-ID: <28318.1034089025@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , "David Ch ristensen" writes: >1) After completing step 6, is the disk usable (accessible through its >device node)? >2) In the cdevsw structure for the drives, what do the physread and >physwrite entries mean? They point to generic routines which will do some tedious work and call the driver back trhough the strategy routine. >3) How do actual read/write requests make it to the device driver? Which is the answer to this question: though the strategy routine. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message