Date: Thu, 17 Oct 2002 01:11:42 +0900 (JST) From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org> To: jhb@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: PCI problems with today's current Message-ID: <20021017.011142.23004863.iwasaki@jp.FreeBSD.org> In-Reply-To: <20021015193547.A88774@panzer.kdm.org> <20021003175706.A1221@panzer.kdm.org> References: <20021015130947.A86610@panzer.kdm.org> <20021016.045918.109976092.iwasaki@jp.FreeBSD.org> <20021015193547.A88774@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > If still NG, please try the attached patch against SupermicroP3TDE6.asl. > > > # _BBN is bridge bus number, my guess is 0x3. You can try to change it > > > # if failed. > > > > Maybe 0x2 is correct. > > I tried 2, and it seems to work correctly now. > > Thanks! Congratulations! # Now we can start discussing ACPI PCI vs. legacy PCI :) DSDT in ACPI BIOS on Supermicro P3TDE6 has obviously wrong _BBN value, but previous kernel can fall back to legacy PCI bridge probing even if PCI bridge probing by ACPI is failed. From: "Kenneth D. Merry" <ken@kdm.org> Subject: PCI problems with today's current Date: Thu, 3 Oct 2002 17:57:06 -0600 Message-ID: <20021003175706.A1221@panzer.kdm.org> > acpi_pcib1: <Host-PCI bridge> on acpi0 > acpi_pcib1: we have duplicate bus number 0 - not probing bus [snip] > pcib2: <ServerWorks host to PCI bridge> at pcibus 2 on motherboard > IOAPIC #1 intpin 8 -> irq 16 > pci2: <PCI bus> on pcib2 > ti0: <Netgear GA620 1000baseT Gigabit Ethernet> mem 0xfebfc000-0xfebfffff irq 16 at device 2.0 on pci2 I think that previous probing system is much more robust and safer in many cases, especially buggy ACPI BIOS. John, can we have previous PCI probing system again? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021017.011142.23004863.iwasaki>