nuxdriverproject.org; o...@aepfle.de; a...@canonical.com
> > Subject: Re: [PATCH v2 1/1] drivers:hv:vmbus drivers:hv:vmbus Allow for more
> > than one MMIO range for children
> >
> > Sorry for beeing late with this message but I'm seeing issues with this
> > commit. I added s
ical.com
> Subject: Re: [PATCH v2 1/1] drivers:hv:vmbus drivers:hv:vmbus Allow for more
> than one MMIO range for children
>
> Jake Oshins writes:
>
> > This set of changes finds the _CRS object in the ACPI namespace
> > that contains memory address space descriptors,
Jake Oshins writes:
> This set of changes finds the _CRS object in the ACPI namespace
> that contains memory address space descriptors, intended to convey
> to VMBus which ranges of memory-mapped I/O space are available for
> child devices, and then builds a resource list that contains all
>
: Re: [PATCH v2 1/1] drivers:hv:vmbus drivers:hv:vmbus Allow for more
than one MMIO range for children
snip
Sorry for beeing late with this message but I'm seeing issues with this
commit. I added some debug to figure out what's going on and here is
what I see:
With Gen1 VM we end up
Jake Oshins ja...@microsoft.com writes:
This set of changes finds the _CRS object in the ACPI namespace
that contains memory address space descriptors, intended to convey
to VMBus which ranges of memory-mapped I/O space are available for
child devices, and then builds a resource list that
: [PATCH v2 1/1] drivers:hv:vmbus drivers:hv:vmbus Allow for more
than one MMIO range for children
Jake Oshins ja...@microsoft.com writes:
This set of changes finds the _CRS object in the ACPI namespace
that contains memory address space descriptors, intended to convey
to VMBus which ranges
6 matches
Mail list logo
