From owner-freebsd-hackers Thu Oct 30 19:40:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA06979 for hackers-outgoing; Thu, 30 Oct 1997 19:40:56 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA06973 for ; Thu, 30 Oct 1997 19:40:51 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id TAA22085; Thu, 30 Oct 1997 19:40:45 -0800 (PST) Message-ID: <19971030194044.15908@hydrogen.nike.efn.org> Date: Thu, 30 Oct 1997 19:40:44 -0800 From: John-Mark Gurney To: Chris Csanady Cc: Chris Vance , freebsd-hackers@FreeBSD.ORG Subject: Re: LKM Interface References: <19971030180558.63267@hydrogen.nike.efn.org> <199710310308.VAA01889@bob.scl.ameslab.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199710310308.VAA01889@bob.scl.ameslab.gov>; from Chris Csanady on Thu, Oct 30, 1997 at 09:08:59PM -0600 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chris Csanady scribbled this message on Oct 30: > >actually.. Doug Rabson did some work to get a kernel linker and module > >design up and running (sys/kern_{module,linker}.c, sys/link_aout.c) and > >it works quite nicely... utilities to load/unload/stat are kld* in > >/sbin... > > Wow.. I didn't realize that this was in current already. :) How do I > go about converting my PCI device driver to use it? Also, are there well.. basicly look at the definition of DECLARE_MODULE.. only problem is that I don't know if the pci bus code can rescan the bus for "new" drivers as they loaded... > any plans for a transition to the new module system? (elf as well?) well.. I'm working on getting the code to run... and once that is done I'll start importing the parts... > >actually... I'm going to be also redesigning the bus/device system.. > >right now each bus has it's own code, and there is no way to easily > >have one bus be attached to another bus (i.e. pci to isa bridge)... > > > >right now my spec so far is: > >http://resnet.uoregon.edu:6971/~jmg/FreeBSD/busdevice.html > >but it still needs a lot of work... > > Have you taken a look at NetBSD's bus code? They seem to have abstracted > things fairly well.. Also, it might be interesting to look into their > bus dma framework as well. I have a bit (not much).. and I didn't link what I saw (I should look closer).. but with this new code, dma is provided by a device driver and not as part of the bus code... who knows why type of isa bus we might encounter in the future? :) also, the design is really quit basic, so the code for it won't be very complex.. the most complex part is supporting the basic abus (address) and bbus (bus) types of busses... abus is a buss where each device is able to be addressed specificily... some examples are pci, isa pnp, mca, eisa, and pccard... a bbus is a bus that really is a bus.. you post information, and any one can consume it.. only bus that I know of that's like this is isa... read the spec... send me comments... :) -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD