From owner-freebsd-current Mon Sep 4 22:33:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.11/8.6.6) id WAA02828 for current-outgoing; Mon, 4 Sep 1995 22:33:17 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.11/8.6.6) with ESMTP id WAA02780 for ; Mon, 4 Sep 1995 22:33:05 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id KAA13927 for ; Mon, 4 Sep 1995 10:59:52 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA17848; Mon, 4 Sep 1995 10:57:57 -0700 From: "Rodney W. Grimes" Message-Id: <199509041757.KAA17848@gndrsh.aac.dev.com> Subject: Re: devinfo - Houston, we have a small crisis here.. To: freebsd-current@FreeBSD.org Date: Mon, 4 Sep 1995 10:57:56 -0700 (PDT) Cc: jhay@mikom.csir.co.za In-Reply-To: <199509041159.NAA23475@uriah.heep.sax.de> from "J Wunsch" at Sep 4, 95 01:59:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2214 Sender: current-owner@FreeBSD.org Precedence: bulk > > As John Hay wrote: > > > > You can use "lsdev -c -t scsi" to show the scsi disks. > > > > | zibbi:/ns/dist/src # lsdev -c -t scsi > > | # This listing automatically generated by lsdev(1) > > | sd0 at SCSI bus 0:0:0 > > | sd1 at SCSI bus 0:1:0 > > | sd2 at SCSI bus 0:2:0 > > | st0 at SCSI bus 0:3:0 > > | cd0 at SCSI bus 0:6:0 > > However, this will also yield all soldering irons, automatic guns, > windmills etc. that are connected via a SCSI bus. Can I get a copy of your scsi bus driver for the soldering iron? :-) :-) And where do I find one of the scsi bus equiped windmills???? Holland didn't want to seem to export one last time I asked :-). In all seriousnous, lsdev is very limited in scope, and semi-self conflicting with respect to ``scsi'' vs ``disk''. To get what Jordan really needs I think someone should sit down with chapters 7 and 12 of ``Writting Device Drivers: Tutorial and Reference'' by Tim Burke, etc al, Digital Press, ISBN 1-55558-141-2. If the device registration stuff continues to be handled as an optional call back to a registration routine FreeBSD will suffer from the problem of driver writters leaving this stuff out. IMHO this belongs in what is now called a isa_device structure (really should be a generic device structure). The sighted material is a good starting point in collapsing the ISA/EISA/PCI/MCA into a complete and coherhent autoconfiguration scheme with full support for loading and unloading drivers. This book is based on digital Unix, but that particular chunk of digital unix looks very much like OSF/1, tastes like OSF/1 and feels like OSF/1. The nice thing about what is described is that you end up with a fully linked tree structure that describes the current running hardware configuation in what appears to me to be complete detail and by adding a few fields here and there the devinfo could be folded right into this structure elimination redundant coding and mandating that all drivers be registered (autoconf would register them, load and unload would register them). Later, -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD