[PATCH v2 0/1] Split VGA default nomination out from VGA arbiter · Daniel Axtens <hidden> · 2017-08-17
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · Daniel Axtens <hidden> · 2017-08-17
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · Daniel Vetter <hidden> · 2017-08-18
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · helgaas@kernel.org (Bjorn Helgaas) · 2017-08-19
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · benh@kernel.crashing.org (Benjamin Herrenschmidt) · 2017-08-20
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · helgaas@kernel.org (Bjorn Helgaas) · 2017-08-20
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · Lorenzo Pieralisi <hidden> · 2017-08-21
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · helgaas@kernel.org (Bjorn Helgaas) · 2017-08-22
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · Ard Biesheuvel <hidden> · 2017-08-23
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · helgaas@kernel.org (Bjorn Helgaas) · 2017-08-23
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · airlied@gmail.com (Dave Airlie) · 2017-08-24
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · Ard Biesheuvel <hidden> · 2017-08-24
[PATCH v2 1/1] Split VGA default device handler out of VGA arbiter · helgaas@kernel.org (Bjorn Helgaas) · 2017-08-24

STALE3289d

Revision v2 of 9 in this series.

Revisions (9)

2017-08-17 v2 [diff vs current]
2017-08-18 v2 [diff vs current]
2017-08-19 v2 [diff vs current]
2017-08-20 v2 current
2017-08-20 v2 [diff vs current]
2017-08-21 v2 [diff vs current]
2017-08-22 v2 [diff vs current]
2017-08-23 v2 [diff vs current]
2017-08-23 v2 [diff vs current]

Re: [PATCH v2 1/1] Split VGA default device handler out of VGA arbiter

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2017-08-20 19:08:20
Also in: dri-devel, linux-arm-kernel, linux-pci

On Sat, 2017-08-19 at 10:47 -0500, Bjorn Helgaas wrote:

So if ARM64 doesn't have these PCI legacy resources, does that mean an
ARM64 host bridge cannot generate these legacy addresses on PCI?  That
is, there's no host bridge window that maps to those PCI addresses?
That seems like a curious restriction on host bridges, but I guess it
would be possible.

It's rather common. For example on POWER8:

 - There is no IO space at all

 - We configure the 32-bit MMIO window to be around 3..4G (to avoid
overlapping with DMA space below it).

So we effectively have no path to the legacy areas, and that hasn't
been a problem so far.

Cheers,
Ben.