From owner-freebsd-hackers Sat May 27 12: 5:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 9040937B9A4 for ; Sat, 27 May 2000 12:05:20 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id PAA20241; Sat, 27 May 2000 15:08:59 -0400 (EDT) Message-Id: <200005271908.PAA20241@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 27 May 2000 15:09:40 -0400 To: John Hay From: Dennis Subject: Re: 4.0 - Isa devices not being probed Cc: hackers@FreeBSD.ORG In-Reply-To: <200005270754.e4R7stT63383@zibbi.mikom.csir.co.za> References: <200005262147.PAA92719@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:54 AM 5/27/00 +0200, John Hay wrote: >> In message <200005261723.NAA16495@etinc.com> Dennis writes: >> : My 4.0 system doesnt probe ISA devices on my system. >> : >> : Whats the trick? Is there a config requirement with old-style drivers? >> >> They probe great for me. what, specifically, isn't probing? > >He is probably talking about their own driver. In that case you have to >add it to /sys/i386/isa/isa_compat.* or bite the bullet and new-busify >it. Yes....Whose brainstorm was it to use the new convoluted bus nonsense in FreeBSD 4.0? Clearly someone who never wrote a driver with a complex controller with indexed memory mapped registers.Whats next, assembler drivers? isa_compat.h? LOL...what college freshman thought of that? Is it really that difficult to have the prefix_probe() function called based on the config file? Its seems rather humorous that the "generic" bus implementation requires that isa drivers be hacked into the kernel with a build-time include. Very humorous indeed. Is this a temporary condition as was the deboggle in v3.0? any docs on this junk? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message