From owner-freebsd-current Mon Sep 29 21:50:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA02105 for current-outgoing; Mon, 29 Sep 1997 21:50:13 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA02100 for ; Mon, 29 Sep 1997 21:50:06 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id VAA23888 for ; Mon, 29 Sep 1997 21:41:59 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd023882; Tue Sep 30 04:41:53 1997 Message-ID: <343082D9.41C67EA6@whistle.com> Date: Mon, 29 Sep 1997 21:40:57 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: buf struct & scsi disk IO availability. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have hit a point on which I am not on firm ground.. I would like to do some IO from a disk at PROBE time. In my original SCSI code, this would have been ok, as long as I didn't need interrupts. I thought I should check the following points with thre readers of -current before I go further however.. 1/ is the buf system set up fully by this time, i.e. can I user getebuf()? david? bruce? john? 2/ Jason, if I use the disk as a direct result of the scsi_attach() routine, does that catch you off guard in the aic driver? In other words, when you call scsi_attach() and friends, are you set up enough to handle that routine looping back and in turn asking you to perform IO (e.g. to read the fdisk table). If this is not the case, I have a work-around which would be to queue further configuration to occur at some later time (but before mounting root), but it wouldn't be so clean. julian