Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 1 Feb 2003 05:23:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 1 Feb 2003 05:23:57 -0500 Received: from matrix.roma2.infn.it ([141.108.255.2]:30602 "EHLO matrix.roma2.infn.it") by vger.kernel.org with ESMTP id ; Sat, 1 Feb 2003 05:23:55 -0500 Message-ID: <32788.62.98.209.28.1044095590.squirrel@webmail.roma2.infn.it> Date: Sat, 1 Feb 2003 11:33:10 +0100 (CET) Subject: Re: yenta-cardbus IRQ0 From: "Emiliano Gabrielli" To: In-Reply-To: References: <55699.141.108.7.31.1044021002.squirrel@webmail.roma2.infn.it> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > On Friday 31 January 2003 08:50, you wrote: >> >> >> > i have been trying to set up a cardbus card on my thinkpad 760ED for about the >> last month and it keeps coming up with IRQ0 and telling me it cant find a irq for >> pin A. what would be causing this and how do I correct it i have already tried >> APCI and it does not work on my laptop so that is no help. I have compiled SMP >> into the kernel though I dont have a dual processor (of course) to gain the added >> functionality. I have recompiled my kernel about 150 times with different setting >> hoping it might just be a conflict in the kernel with no luck. I looked at the >> yenta driver it's self and noticed that it accepts IRQ0 as a valid irq but that >> appears to mean no irq at all. which config file would i use to force it to set a >> irq? >> > >> > >> > Thanx for any assistanc you might give >> >> plz send an lspci -vv -xxx -s *your dev* >> >> what kernel are you using ? > > i am using 2.4.18 and here is lspci uhmm, 1th try to upgrade to a newer one, then I experienced the same problem with a custom board... the problem was triggered by the Base Address too high: Region 0: Memory at 10812000 (32-bit, non-prefetchable) [size=4K] moving id_sel (in the PCI core of the board) in order to obtain a lower bar all worked. BTW, has anybody there ever heared about such a costraint in the PCI specification ?? Why I got this strange behaviour ??? -- Emiliano Gabrielli dip. di Fisica 2? Universit? di Roma "Tor Vergata" - 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/