Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 6 Dec 2000 14:39:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 6 Dec 2000 14:38:55 -0500 Received: from mailhst2.its.tudelft.nl ([130.161.34.250]:22291 "EHLO mailhst2.its.tudelft.nl") by vger.kernel.org with ESMTP id ; Wed, 6 Dec 2000 14:38:51 -0500 Date: Wed, 6 Dec 2000 20:08:03 +0100 From: Erik Mouw To: Linus Torvalds Cc: Erik Mouw , Kernel Mailing List Subject: Re: test12-pre6 Message-ID: <20001206200803.C847@arthur.ubicom.tudelft.nl> In-Reply-To: <20001206190850.A847@arthur.ubicom.tudelft.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from torvalds@transmeta.com on Wed, Dec 06, 2000 at 10:38:51AM -0800 Organization: Eric Conspiracy Secret Labs X-Eric-Conspiracy: There is no conspiracy! Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 06, 2000 at 10:38:51AM -0800, Linus Torvalds wrote: > On Wed, 6 Dec 2000, Erik Mouw wrote: > > So at first the PCI code can't allocate an IRQ for devices 00:00.1 > > (audio), 00:07.2 (USB), and 00:09.0 (winmodem), but after the audio and > > USB modules get inserted, IRQ 5 and 11 get allocated. > > No, the irq stuff is a two-stage process: at first it only _reads_ the irq > config stuff for every device - whether they have a driver or not - and at > this stage it will not ever actually allocate and set up a new route. It > will just see if a route has already been set up by the BIOS. > > Then, when a driver actually does a pci_enable_device(), it will do the > second stage of PCI irq routing, which is to actually set up a route if > none originally existed. So this is why you first se "failed" messages > (the generic "test if there is a route" code) and then later when loading > the module you see "allocated irq XX" messages. Thanks for explaining. > So your dmesg output looks fine, and everything is ok at that level. The > fact that something still doesn't work for you indicates that we still > have problems, of course. > > Can you tell me what device it is that doesn't work for you? The USB controller. That's device 00:07.2: 00:07.2 USB Controller: Intel Corporation 82440MX USB Universal Host Controller (prog-if 00 [UHCI]) Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-