On Wed, Dec 16, 2015 at 06:21:37PM +0530, Jayachandran C. wrote:
[...]
> > That list is there to manage hotplug bridges, what makes you think
> > it is not necessary ? Jiang (in CC) can certainly comment on that and
> > how that list handling can be updated/simplified, if possible.
>
> Looking t
On Wed, Dec 09, 2015 at 03:31:41PM +0530, Jayachandran C. wrote:
> [trimmed the cc list a bit]
> On Mon, Dec 07, 2015 at 02:31:17PM -0600, Bjorn Helgaas wrote:
> > On Tue, Oct 27, 2015 at 05:38:31PM +0100, Tomasz Nowicki wrote:
> [...]
> > >
> > > Tomasz Nowicki (10):
> > > x86, pci: Reorder log
On 10/27/2015 11:38 AM, Tomasz Nowicki wrote:
From the functionality point of view this series might be split into two logic
parts:
1. Making MMCONFIG code arch-agnostic which allows all architectures to collect
PCI config regions and used when necessary.
2. Using generic MMCONFIG code and
On Tue, Oct 27, 2015 at 05:38:31PM +0100, Tomasz Nowicki wrote:
> From the functionality point of view this series might be split into two
> logic parts:
> 1. Making MMCONFIG code arch-agnostic which allows all architectures to
> collect
>PCI config regions and used when necessary.
> 2. Using
Tested on AMD Seattle platform (Overdrive revB) w/ both MSI and legacy
interrupt.
Tested-by: Suravee Suthikulpanit
Thanks,
Suravee
On 10/27/15 11:38, Tomasz Nowicki wrote:
From the functionality point of view this series might be split into two logic
parts:
1. Making MMCONFIG code arch-agn
On 10/30/2015 05:07 AM, Jon Masters wrote:
Hi Tomasz,
Thanks for posting this series.
On 10/27/2015 12:38 PM, Tomasz Nowicki wrote:
From the functionality point of view this series might be split into two logic
parts:
1. Making MMCONFIG code arch-agnostic which allows all architectures to
Hi Jon,
On 2015/10/30 12:07, Jon Masters wrote:
> Hi Tomasz,
>
> Thanks for posting this series.
>
> On 10/27/2015 12:38 PM, Tomasz Nowicki wrote:
>
>> From the functionality point of view this series might be split into two
>> logic parts:
>> 1. Making MMCONFIG code arch-agnostic which allows al
Hi Tomasz,
Thanks for posting this series.
On 10/27/2015 12:38 PM, Tomasz Nowicki wrote:
> From the functionality point of view this series might be split into two
> logic parts:
> 1. Making MMCONFIG code arch-agnostic which allows all architectures to
> collect
>PCI config regions and use
>From the functionality point of view this series might be split into two logic
>parts:
1. Making MMCONFIG code arch-agnostic which allows all architectures to collect
PCI config regions and used when necessary.
2. Using generic MMCONFIG code and introducing ACPI based PCI hostbridge
initial
9 matches
Mail list logo