From: Andi Kleen <ak@suse.de>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.18-git] Lost all PCI devices
Date: Sat, 30 Sep 2006 20:11:13 +0200 [thread overview]
Message-ID: <200609302011.13457.ak@suse.de> (raw)
In-Reply-To: <20060930174247.GA31793@dreamland.darkstar.lan>
On Saturday 30 September 2006 19:42, Luca Tettamanti wrote:
> Hi Andi,
> I'm testing current git on my notebook, but kernel doesn't find any
> PCI device: no video card, no IDE, nothing.
Can you test it with this patch please?
-Andi
Fix PCI BIOS config space access
Got broken by a earlier change.
Signed-off-by: Andi Kleen <ak@suse.de>
Index: linux/arch/i386/pci/direct.c
===================================================================
--- linux.orig/arch/i386/pci/direct.c
+++ linux/arch/i386/pci/direct.c
@@ -256,6 +256,8 @@ static int __init pci_check_type2(void)
void __init pci_direct_init(int type)
{
+ if (type == 0)
+ return;
printk(KERN_INFO "PCI: Using configuration type %d\n", type);
if (type == 1)
raw_pci_ops = &pci_direct_conf1;
Index: linux/arch/i386/pci/init.c
===================================================================
--- linux.orig/arch/i386/pci/init.c
+++ linux/arch/i386/pci/init.c
@@ -28,6 +28,10 @@ static __init int pci_access_init(void)
#ifdef CONFIG_PCI_DIRECT
pci_direct_init(type);
#endif
+ if (!raw_pci_ops)
+ printk(KERN_ERR
+ "PCI: Fatal: No config space access function found\n");
+
return 0;
}
arch_initcall(pci_access_init);
next prev parent reply other threads:[~2006-09-30 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 17:42 [2.6.18-git] Lost all PCI devices Luca Tettamanti
2006-09-30 18:11 ` Andi Kleen [this message]
2006-09-30 20:22 ` Luca Tettamanti
2006-09-30 20:34 ` Andi Kleen
2006-09-30 22:06 ` Luca Tettamanti
2006-09-30 22:13 ` Andi Kleen
2006-10-01 15:46 ` Luca Tettamanti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609302011.13457.ak@suse.de \
--to=ak@suse.de \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox