Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 25 Jul 2002 04:30:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 25 Jul 2002 04:30:57 -0400 Received: from [195.63.194.11] ([195.63.194.11]:3846 "EHLO mail.stock-world.de") by vger.kernel.org with ESMTP id ; Thu, 25 Jul 2002 04:30:57 -0400 Message-ID: <3D3FB6C8.1070409@evision.ag> Date: Thu, 25 Jul 2002 10:28:56 +0200 From: Marcin Dalecki Reply-To: martin@dalecki.de User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 X-Accept-Language: en-us, en, pl, ru MIME-Version: 1.0 To: Vojtech Pavlik CC: Alan Cox , William Lee Irwin III , linux-kernel@vger.kernel.org Subject: Re: [RFC/CFT] cmd640 irqlocking fixes References: <20020724225826.GF25038@holomorphy.com> <1027559111.6456.34.camel@irongate.swansea.linux.org.uk> <20020725095448.B21541@ucw.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1092 Lines: 25 Vojtech Pavlik wrote: > > The kernel functions are OK. The problem is that the kernel can use > PCIBIOS calls to set the registers. And certain old buggy BIOSes which > violate the PCI spec can use wrong size data transfers to set the > registers, which the CMD640 doesn't like. > > IMHO the best workaround here would be either to disable PCIBIOS calls > and revert to conf1 or conf2 in the PCI code if a CMD640 is present, or > just panic() in the CMD640 code and suggest to the user to use > "pci=nobios" on the kernel command line. I'd actually prefer the later. > From a long long time ago during the first days of this driver I remember that those chips could be wired to both PCI and VLB(ISA) bus. And this is the main reaons why the functions is question exist in first place -> "emulating" PCI configuration space access on VLB. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/