From owner-freebsd-current Wed Jul 28 10:33:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id E003614D70 for ; Wed, 28 Jul 1999 10:33:27 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id TAA48306 for current@freebsd.org; Wed, 28 Jul 1999 19:32:02 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199907281732.TAA48306@zibbi.mikom.csir.co.za> Subject: a little newbus problem To: current@freebsd.org Date: Wed, 28 Jul 1999 19:32:02 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been trying to get my ar(4) and sr(4) drivers going again on -current, but it seems that the newbus code doesn't like my little trick that worked for so long. :-( Basically the drivers are called ar0 in the kernel config file, but in the isa_driver struct I call them arc and not ar, because the chip that is used actually have 2 ports and I register them seperately as ar0 and ar1 during the attach phase. From what I can see now, it looks like the newbus code doesn't even call the arprobe routine. I have even added a printf right in the start of it, but it never prints anything. Just as a test I changed my kernel config file and files.i386 from ar to arc and then it works. So what should I do? Can the newbus code be fixed to work in this case too or should I newbusify the drivers and will that help? Won't that create a clash because of the isa compatabilty shim? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message