From owner-freebsd-current Wed Mar 6 15:42:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA10404 for current-outgoing; Wed, 6 Mar 1996 15:42:47 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA10384 Wed, 6 Mar 1996 15:42:39 -0800 (PST) Message-Id: <199603062342.PAA10384@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: imb@scgt.oz.au, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 2842 and the disappearing file-system :-( In-reply-to: Your message of "Wed, 06 Mar 1996 15:54:48 MST." <199603062254.PAA11994@phaeton.artisoft.com> Date: Wed, 06 Mar 1996 15:42:39 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG Precedence: bulk >> How are they kludged? I haven't seen a single report of eisaconf >> without detected devices causing problems in a system. Furthermore, >> if you don't have a 2842 or and eisa machine, you can disable the >> eisa0 device in your config file. If you do have a 2842, you'd >> have to read the same bytes of the I/O address space, so it buys >> you nothing to have a separate probe for it. > >Maybe I'm missing something. I would guess you didn't even look. Have you looked at eisaconf.c? or aic7770.c? >Why do you have to have a seperate probe? RTSL >Why can't you use the same probe routine address in two "driver instances"? Eisaconf doesn't work that way at all. >And wouldn't this fix the interrrupt attach problem introduced by the >eisaconf code in the VLB Adaptec case? Because the bug wasn't even in eisaconf. It was in i386/isa/isa.c. >You keep saying you need to duplicate cade -- I don't see it. I see >that there is a need to duplicate ~32 bytes of data structure to get >an EISA and non-EISA device instance. Tell me why Im wrong... Right now the code for dealing with the 2842 and the 2742 is one and the same. To do what you propose would mean adding an isa probe and doing the same looping through the slots that the eisaconf code does already, although the 2842 probe would have to do it once for each card probe instead of just creating the device nodes once like the eisaconf code does. There is simply no reason to break the probe up. It only adds complexity and code. > > > Regards, > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================