From owner-freebsd-hardware Thu Jan 11 05:57:37 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA24357 for hardware-outgoing; Thu, 11 Jan 1996 05:57:37 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA24352 for ; Thu, 11 Jan 1996 05:57:34 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id NAA14093 for ; Thu, 11 Jan 1996 13:55:38 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Thu, 11 Jan 1996 13:55:48 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id NAA13907; Thu, 11 Jan 1996 13:55:46 GMT From: Paul Richards Message-Id: <199601111355.NAA13907@cadair.elsevier.co.uk> Subject: Re: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575 To: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 11 Jan 1996 13:55:46 +0000 (GMT) Cc: dlhodge@netcom.com, hardware@FreeBSD.org In-Reply-To: <199601111307.AA29433@Sysiphos> from "Stefan Esser" at Jan 11, 96 02:07:53 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.org Precedence: bulk In reply to Stefan Esser who said > > } see it as a plain PCnet-PCI chip. It'll probably probe as a PCnet-VL > } chip though because of a known problem in the lance probe code for > } PCI (yes, I'll look at this soon :-) > > This would be fine. It has become a FAQ ... > I've looked into the Lance driver, and found that there > are MANY references to the isa device data structure. > But then, you can easily malloc one from the PCI probe > code ... :) Not surprising, it's an ISA driver :-) > Yes, there have been some success reports. The situation > is not that bad, as all that is required is to enter the > port address and irq into the boot config tool. But the > bad thing is, that the IRQ will not be printed in the PCI > probe message for an "unknown" device. Have considered to > change this... Hmmm, guess I will do it! All that's needed is to get the IRQ and port from the PCI code but I've been delaying fixing this because I don't really want to hack a specific fix into lnc0 for what is a generic problem i.e. many devices have a core set of code that works across a chipset family and needs different glue code to hook it into different buses (or even different architectures when we go down that road since the core lance code would be the same on a Sun platform). It needs some re-architecting though all through the device driver sub-system. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work)