Re: [PATCH] vgaarb: use bridges to control VGA routing where possible. (v2)

2010-12-20 Thread Jesse Barnes
On Mon, 20 Dec 2010 10:10:09 +1000 Dave Airlie wrote: > - * @change_bridge: traverse ancestors and change bridges > + * @change_bridge_flags: traverse ancestors and change bridges > + * CHANGE_BRIDGE_ONLY / CHANGE_BRIDGE > */ > int pci_set_vga_state(struct pci_dev *dev, bool decode, > -

[PATCH] vgaarb: use bridges to control VGA routing where possible. (v2)

2010-12-20 Thread Jesse Barnes
On Mon, 20 Dec 2010 10:10:09 +1000 Dave Airlie wrote: > - * @change_bridge: traverse ancestors and change bridges > + * @change_bridge_flags: traverse ancestors and change bridges > + * CHANGE_BRIDGE_ONLY / CHANGE_BRIDGE > */ > int pci_set_vga_state(struct pci_dev *dev, bool decode, > -

[PATCH] vgaarb: use bridges to control VGA routing where possible. (v2)

2010-12-20 Thread Dave Airlie
From: Dave Airlie So in a lot of modern systems, a GPU will always be below a parent bridge that won't share with any other GPUs. This means VGA arbitration on those GPUs can be controlled by using the bridge routing instead of io/mem decodes. The problem is locating which GPUs share which ups

[PATCH] vgaarb: use bridges to control VGA routing where possible. (v2)

2010-12-19 Thread Dave Airlie
From: Dave Airlie So in a lot of modern systems, a GPU will always be below a parent bridge that won't share with any other GPUs. This means VGA arbitration on those GPUs can be controlled by using the bridge routing instead of io/mem decodes. The problem is locating which GPUs share which ups