On 11/06/13 07:04, Jordan Justen wrote:
On Wed, Oct 30, 2013 at 5:12 PM, Laszlo Ersek ler...@redhat.com wrote:
So, I found no regressions in my usual environment (after fixing the
ASSERT() with the attached patch).
Does my current ovmf-nvvars branch also fix this issue?
On Wed, Oct 30, 2013 at 5:12 PM, Laszlo Ersek ler...@redhat.com wrote:
On 10/28/13 22:27, Jordan Justen wrote:
Previously we would only search for MMIO regions that were also
above every EfiGcdMemoryTypeReserved and EfiGcdMemoryTypeSystemMemory
region.
Yes.
More verbosely, the previous
On Wed, Oct 30, 2013 at 5:12 PM, Laszlo Ersek ler...@redhat.com wrote:
So, I found no regressions in my usual environment (after fixing the
ASSERT() with the attached patch).
Does my current ovmf-nvvars branch also fix this issue?
https://github.com/jljusten/edk2.git ovmf-nvvars
I updated
On 10/28/13 22:27, Jordan Justen wrote:
Previously we would only search for MMIO regions that were also
above every EfiGcdMemoryTypeReserved and EfiGcdMemoryTypeSystemMemory
region.
Now we just search for the largest EfiGcdMemoryTypeMemoryMappedIo
region.
This will allow us to mark the
On Thu, Oct 31, 2013 at 2:40 AM, Laszlo Ersek ler...@redhat.com wrote:
On 10/28/13 22:27, Jordan Justen wrote:
Previously we would only search for MMIO regions that were also
above every EfiGcdMemoryTypeReserved and EfiGcdMemoryTypeSystemMemory
region.
Now we just search for the largest
On 10/31/13 18:53, Jordan Justen wrote:
On Thu, Oct 31, 2013 at 2:40 AM, Laszlo Ersek ler...@redhat.com wrote:
On 10/28/13 22:27, Jordan Justen wrote:
Previously we would only search for MMIO regions that were also
above every EfiGcdMemoryTypeReserved and EfiGcdMemoryTypeSystemMemory
region.
Previously we would only search for MMIO regions that were also
above every EfiGcdMemoryTypeReserved and EfiGcdMemoryTypeSystemMemory
region.
Now we just search for the largest EfiGcdMemoryTypeMemoryMappedIo
region.
This will allow us to mark the flash memory as a runtime memory
region in order
