On Wed, Jan 31, 2018 at 4:13 AM, Marcel Apfelbaum wrote:
> On 30/01/2018 19:49, Andrey Smirnov wrote:
>> On Tue, Jan 30, 2018 at 5:18 AM, Marcel Apfelbaum
>> wrote:
>>> Hi Andrei,
>>>
>>> Sorry for letting you wait,
>>> I have some comments/questions below.
>>>
>>>
>>> On 16/01/2018 3:37, Andrey
On 30/01/2018 19:49, Andrey Smirnov wrote:
> On Tue, Jan 30, 2018 at 5:18 AM, Marcel Apfelbaum
> wrote:
>> Hi Andrei,
>>
>> Sorry for letting you wait,
>> I have some comments/questions below.
>>
>>
>> On 16/01/2018 3:37, Andrey Smirnov wrote:
>>>
>>> Add code needed to get a functional PCI subsyt
On Tue, Jan 30, 2018 at 5:18 AM, Marcel Apfelbaum
wrote:
> Hi Andrei,
>
> Sorry for letting you wait,
> I have some comments/questions below.
>
>
> On 16/01/2018 3:37, Andrey Smirnov wrote:
>>
>> Add code needed to get a functional PCI subsytem when using in
>> conjunction with upstream Linux gues
Hi Andrei,
Sorry for letting you wait,
I have some comments/questions below.
On 16/01/2018 3:37, Andrey Smirnov wrote:
Add code needed to get a functional PCI subsytem when using in
conjunction with upstream Linux guest (4.13+). Tested to work against
"e1000e" (network adapter, using MSI interr
Hi Andrey,
On Wed, Jan 17, 2018 at 1:12 PM, Andrey Smirnov
wrote:
> On Wed, Jan 17, 2018 at 7:23 AM, Marcel Apfelbaum
> wrote:
>> That being said, if Andrey can point me to the PCI spec for the Designware
>> PCI host bridge and what parts they implemented for it I can have a look,
>> sure.
>> (I
On 17/01/2018 18:12, Andrey Smirnov wrote:
On Wed, Jan 17, 2018 at 7:23 AM, Marcel Apfelbaum
wrote:
Hi Peter,
On 16/01/2018 16:34, Peter Maydell wrote:
On 16 January 2018 at 01:37, Andrey Smirnov
wrote:
Add code needed to get a functional PCI subsytem when using in
conjunction with upst
On 17/01/2018 17:35, Peter Maydell wrote:
On 17 January 2018 at 15:23, Marcel Apfelbaum wrote:
On 16/01/2018 16:34, Peter Maydell wrote:
On 16 January 2018 at 01:37, Andrey Smirnov
I'm not familiar enough with our PCI code to be able to review
this, I'm afraid. MST and Marcel are our PCI sub
On Wed, Jan 17, 2018 at 7:23 AM, Marcel Apfelbaum
wrote:
>
> Hi Peter,
>
>
> On 16/01/2018 16:34, Peter Maydell wrote:
>>
>> On 16 January 2018 at 01:37, Andrey Smirnov
>> wrote:
>>>
>>> Add code needed to get a functional PCI subsytem when using in
>>> conjunction with upstream Linux guest (4.13
On 17 January 2018 at 15:23, Marcel Apfelbaum wrote:
>
> On 16/01/2018 16:34, Peter Maydell wrote:
>> On 16 January 2018 at 01:37, Andrey Smirnov
>> I'm not familiar enough with our PCI code to be able to review
>> this, I'm afraid. MST and Marcel are our PCI subsystem maintainers --
>> could one
Hi Peter,
On 16/01/2018 16:34, Peter Maydell wrote:
On 16 January 2018 at 01:37, Andrey Smirnov wrote:
Add code needed to get a functional PCI subsytem when using in
conjunction with upstream Linux guest (4.13+). Tested to work against
"e1000e" (network adapter, using MSI interrupts) as well
On 16 January 2018 at 01:37, Andrey Smirnov wrote:
> Add code needed to get a functional PCI subsytem when using in
> conjunction with upstream Linux guest (4.13+). Tested to work against
> "e1000e" (network adapter, using MSI interrupts) as well as
> "usb-ehci" (USB controller, using legacy PCI i
Add code needed to get a functional PCI subsytem when using in
conjunction with upstream Linux guest (4.13+). Tested to work against
"e1000e" (network adapter, using MSI interrupts) as well as
"usb-ehci" (USB controller, using legacy PCI interrupts).
Cc: Peter Maydell
Cc: Jason Wang
Cc: Philippe
12 matches
Mail list logo
