Re: Fwd: [Bug 42606] New: PCI I/O range not assigned under newer kernels

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jan 23, 2012 at 10:55 AM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
> Windows shows the [io  0xf000-0xffff] range as being available under
> both host bridges, and the fact that those ports actually work under
> both bridges means they must actually be routed both places.

Oops, this is wrong.  We can't tell whether the [io  0xf000-0xffff]
range is routed to PCI0, because when the card under that bridge, the
BIOS puts it at [io  0xdc00-0xdcff] instead.

This is probably a BIOS bug (the resource assignment part puts the
card in the right area, but the ACPI _CRS doesn't match).  But the
fact remains that Windows does accept this _CRS and Linux doesn't but
probably should.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux