On 19/07/2017 21:56, Konrad Rzeszutek Wilk wrote:
On Wed, Jul 19, 2017 at 09:38:50PM +0300, Alexander Bezzubikov wrote:
2017-07-19 21:18 GMT+03:00 Konrad Rzeszutek Wilk :
On Wed, Jul 19, 2017 at 05:14:41PM +, Alexander Bezzubikov wrote:
ср, 19 июля 2017 г. в
On Wed, Jul 19, 2017 at 09:38:50PM +0300, Alexander Bezzubikov wrote:
> 2017-07-19 21:18 GMT+03:00 Konrad Rzeszutek Wilk :
>
> > On Wed, Jul 19, 2017 at 05:14:41PM +, Alexander Bezzubikov wrote:
> > > ср, 19 июля 2017 г. в 16:57, Konrad Rzeszutek Wilk <
> >
2017-07-19 21:18 GMT+03:00 Konrad Rzeszutek Wilk :
> On Wed, Jul 19, 2017 at 05:14:41PM +, Alexander Bezzubikov wrote:
> > ср, 19 июля 2017 г. в 16:57, Konrad Rzeszutek Wilk <
> konrad.w...@oracle.com>:
> >
> > > On Wed, Jul 19, 2017 at 04:20:12PM +0300, Aleksandr
On Wed, Jul 19, 2017 at 05:14:41PM +, Alexander Bezzubikov wrote:
> ср, 19 июля 2017 г. в 16:57, Konrad Rzeszutek Wilk :
>
> > On Wed, Jul 19, 2017 at 04:20:12PM +0300, Aleksandr Bezzubikov wrote:
> > > Now PCI bridges (and PCIE root port too) get a bus range number in
ср, 19 июля 2017 г. в 16:57, Konrad Rzeszutek Wilk :
> On Wed, Jul 19, 2017 at 04:20:12PM +0300, Aleksandr Bezzubikov wrote:
> > Now PCI bridges (and PCIE root port too) get a bus range number in
> system init,
> > basing on currently plugged devices. That's why when one
On 19/07/2017 16:56, Konrad Rzeszutek Wilk wrote:
On Wed, Jul 19, 2017 at 04:20:14PM +0300, Aleksandr Bezzubikov wrote:
In case of RedHat PCI bridges reserve additional buses, which number is provided
It is "Red Hat"
in a vendor-specific capability.
And perhaps also a #define ?
Right,
On 19/07/2017 16:20, Aleksandr Bezzubikov wrote:
Add a capability lookup function which gets bdf instead of pci_device
as its first argument. It may be useful when we have bdf,
but don't have the whole pci_device structure.
Signed-off-by: Aleksandr Bezzubikov
---
On Wed, Jul 19, 2017 at 04:20:14PM +0300, Aleksandr Bezzubikov wrote:
> In case of RedHat PCI bridges reserve additional buses, which number is
> provided
It is "Red Hat"
> in a vendor-specific capability.
And perhaps also a #define ?
>
> Signed-off-by: Aleksandr Bezzubikov
On Wed, Jul 19, 2017 at 04:20:12PM +0300, Aleksandr Bezzubikov wrote:
> Now PCI bridges (and PCIE root port too) get a bus range number in system
> init,
> basing on currently plugged devices. That's why when one wants to hotplug
> another bridge,
> it needs his child bus, which the parent is
In case of RedHat PCI bridges reserve additional buses, which number is provided
in a vendor-specific capability.
Signed-off-by: Aleksandr Bezzubikov
---
src/fw/pciinit.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/src/fw/pciinit.c
Now PCI bridges (and PCIE root port too) get a bus range number in system init,
basing on currently plugged devices. That's why when one wants to hotplug
another bridge,
it needs his child bus, which the parent is unable to provide.
The suggested workaround is to have vendor-specific capability
Add a capability lookup function which gets bdf instead of pci_device
as its first argument. It may be useful when we have bdf,
but don't have the whole pci_device structure.
Signed-off-by: Aleksandr Bezzubikov
---
src/hw/pcidevice.c | 24
On Tue, 2017-07-18 at 13:51 +0200, Paul Menzel wrote:
> Dear Gerd,
>
>
> On 07/18/17 13:36, Gerd Hoffmann wrote:
> > xhci controllers have two virtual ports per (usb3 capable) physical
> > port, one for usb2 and one for usb3 devices. Add a hub portmap
> > callback
> > to map the virtual ports
13 matches
Mail list logo