From owner-freebsd-current Sun Feb 20 10: 6:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from Brigada-A.Ethereal.RU (Brigada-A.ethereal.ru [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 6487C37BF4F for ; Sun, 20 Feb 2000 10:06:45 -0800 (PST) (envelope-from nms@Brigada-A.Ethereal.RU) Received: by Brigada-A.Ethereal.RU (Postfix, from userid 1002) id 180CC1FC; Sun, 20 Feb 2000 21:06:43 +0300 (MSK) Received: from Brigada-A.Ethereal.RU (localhost [127.0.0.1]) by Brigada-A.Ethereal.RU (Postfix) with ESMTP id F10631D6; Sun, 20 Feb 2000 21:06:42 +0300 (MSK) From: Nikolai Saoukh To: Martin Husemann Cc: current@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: Your message of "Sun, 20 Feb 2000 17:44:04 +0100." <200002201644.RAA01128@rumolt.teuto.de> Date: Sun, 20 Feb 2000 21:06:37 +0300 Message-Id: <20000220180643.180CC1FC@Brigada-A.Ethereal.RU> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Depends. If the drivers allocation is coherent with the vendors description > in the PnP configuration data, it's a newbus error (it shouldn't try to > allocate the card there in the first place). If the PnP info differs from > the drivers view of the card, it's either the vendors fault for providing wrong > infos (this wouldn't be the only card suffering) [fix: provide a quirk entry], > or the drivers fault: it should obey what the vendor tells PnP about the > card. Which case applies? Simple: if it's possible to change the driver to > obey the cards infos, that should be done. If the driver couldn't be made > to work support for that card should be removed :-) Well, current PnP code has own problems with parsing card data: * wrong calculation of memory range size (PR: kern/16712 with path). This bug will hit any card with io memory (ed driver for example). * inability to parse a little bit complicated config like in 'IBM Auto 16/4 Token-Ring ISA Adapter' -- I am still fighting with this bug. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message