* XP PCI Contamination, GURR (Re: Care?)
[not found] <000501c1877f$87248b40$10105318@jeremy.bc.ca>
@ 2002-01-17 12:42 ` Andre Hedrick
2002-01-17 13:14 ` Jeff Garzik
2002-01-17 13:17 ` Dave Jones
0 siblings, 2 replies; 3+ messages in thread
From: Andre Hedrick @ 2002-01-17 12:42 UTC (permalink / raw)
To: Jeremy Freeman; +Cc: linux-kernel
It appears the folks up in redmond have succeeded in having the BIOS
people default disable PCI resources. Since XP will reject, or assume a
device is in use should the BAR's be allocated, the various archs may need
to have a broader setup table or a more generic ruleset.
Any thoughts on how best to address good hardare, which the BIOS does not
setup per redmond-rules.
On Mon, 17 Dec 2001, Jeremy Freeman wrote:
> Not sure if you care about this or not.. Probably seen it from someone else
> already.. Dual Athlon 1800+ MPs on a Tyain Thunder K7 BIOS 2.09.
>
> 2.4.16 kernel.
>
> <snip>
> AMD7411: IDE controller on PCI bus 00 dev 39
> PCI: Device 00:07.1 not available because of resource collisions
> AMD7411: chipset revision 1
> AMD7411: not 100% native mode: will probe irqs later
> AMD7411: IO baseregs (BIOS) are reported as MEM, report to
> <andre@linux-ide.org>.
> AMD7411: simplex device: DMA disabled
> ide1: AMD7411 Bus-Master DMA disabled (BIOS)
> hda: ATAPI 52X CDROM, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: ATAPI 48X CD-ROM drive, 128kB Cache
> <snip>
>
Andre Hedrick
Linux Disk Certification Project Linux ATA Development
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: XP PCI Contamination, GURR (Re: Care?)
2002-01-17 12:42 ` XP PCI Contamination, GURR (Re: Care?) Andre Hedrick
@ 2002-01-17 13:14 ` Jeff Garzik
2002-01-17 13:17 ` Dave Jones
1 sibling, 0 replies; 3+ messages in thread
From: Jeff Garzik @ 2002-01-17 13:14 UTC (permalink / raw)
To: Andre Hedrick; +Cc: Jeremy Freeman, linux-kernel
Andre Hedrick wrote:
>
> It appears the folks up in redmond have succeeded in having the BIOS
> people default disable PCI resources. Since XP will reject, or assume a
> device is in use should the BAR's be allocated, the various archs may need
> to have a broader setup table or a more generic ruleset.
>
> Any thoughts on how best to address good hardare, which the BIOS does not
> setup per redmond-rules.
pci_enable_enable, pci_set_master, and all the tools that the kernel
already provides...
--
Jeff Garzik | Alternate titles for LOTR:
Building 1024 | Fast Times at Uruk-Hai
MandrakeSoft | The Took, the Elf, His Daughter and Her Lover
| Samwise Gamgee: International Hobbit of Mystery
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: XP PCI Contamination, GURR (Re: Care?)
2002-01-17 12:42 ` XP PCI Contamination, GURR (Re: Care?) Andre Hedrick
2002-01-17 13:14 ` Jeff Garzik
@ 2002-01-17 13:17 ` Dave Jones
1 sibling, 0 replies; 3+ messages in thread
From: Dave Jones @ 2002-01-17 13:17 UTC (permalink / raw)
To: Andre Hedrick; +Cc: Jeremy Freeman, linux-kernel
On Thu, 17 Jan 2002, Andre Hedrick wrote:
> It appears the folks up in redmond have succeeded in having the BIOS
> people default disable PCI resources. Since XP will reject, or assume a
> device is in use should the BAR's be allocated, the various archs may need
> to have a broader setup table or a more generic ruleset.
> Any thoughts on how best to address good hardare, which the BIOS does not
> setup per redmond-rules.
Why do I have this sneaking suspicion that ACPI will play a part here.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-01-17 13:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <000501c1877f$87248b40$10105318@jeremy.bc.ca>
2002-01-17 12:42 ` XP PCI Contamination, GURR (Re: Care?) Andre Hedrick
2002-01-17 13:14 ` Jeff Garzik
2002-01-17 13:17 ` Dave Jones
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox