On 05/13/14 01:22, Jordan Justen wrote:
> On Mon, May 12, 2014 at 2:35 PM, Laszlo Ersek wrote:
>> On 05/12/14 22:49, Jordan Justen wrote:
>>> On Mon, May 12, 2014 at 10:41 AM, Laszlo Ersek wrote:
On 05/12/14 18:03, Jordan Justen wrote:
> On Mon, May 12, 2014 at 6:18 AM, Laszlo Ersek
>>>
David,
Where do we initialize
UmaAddress/UmaSize/HiPermanentMemoryAddress/HiPermanentMemorySize?
And could you explain the purpose of these new fields?
Thanks
Elvin
-Original Message-
From: David Woodhouse [mailto:dw...@infradead.org]
Sent: Monday, May 12, 2014 10:00 PM
T
On 05/12/14 22:27, Mike Maslenkin wrote:
> I just wanted to point that since it is documented behavior may be a
> strict requirement for CSM is enough to run W7, W2K8R2, instead of
> having a bunch of code requiring a special compilation with NASM. But
> anyway, idea with shim is great.
Ah, OK, I
The design purpose of NET_BUF is to meet the buffer management requirement for
different network modules. For example, IP module supports reassemble and
fragment packets; NET_BUF provides the capability to wrap a list of buffers
into one buffer to avoid data copy in different layers.
Best Regar
Dear ShellPkg maintainer,
please find the attached patch that fixes the following error.
The function InternalShellExecuteDevicePath() did not differentiate
an error occuring during the preparation of an image and an error
occuring during its execution.
A use case of the issue wa
On Mon, May 12, 2014 at 2:35 PM, Laszlo Ersek wrote:
> On 05/12/14 22:49, Jordan Justen wrote:
>> On Mon, May 12, 2014 at 10:41 AM, Laszlo Ersek wrote:
>>> On 05/12/14 18:03, Jordan Justen wrote:
On Mon, May 12, 2014 at 6:18 AM, Laszlo Ersek
wrote:
> Additionally, there's another (
On 05/12/14 22:49, Jordan Justen wrote:
> On Mon, May 12, 2014 at 10:41 AM, Laszlo Ersek wrote:
>> On 05/12/14 18:03, Jordan Justen wrote:
>>> On Mon, May 12, 2014 at 6:18 AM, Laszlo Ersek
>>> wrote:
Additionally, there's another (similarly downstream only) patch
OvmfPkg: Don't b
On Mon, May 12, 2014 at 10:41 AM, Laszlo Ersek wrote:
> On 05/12/14 18:03, Jordan Justen wrote:
>> On Mon, May 12, 2014 at 6:18 AM, Laszlo Ersek
>> wrote:
>>> Additionally, there's another (similarly downstream only) patch
>>>
>>> OvmfPkg: Don't build in QemuVideoDxe when we have CSM
>>>
>>> Di
>
> On 05/12/14 18:21, Mike Maslenkin wrote:
> >
> >>
> + Segment0 = 0;
> + Segment0Pages = 1;
> + Status = gBS->AllocatePages (AllocateAddress, EfiReservedMemoryType,
> + Segment0Pages, &Segment0);
> + if (EFI_ERROR (Status)) {
> +goto
Mike Maslenkin [mailto:miha...@parallels.com] wrote:
[...]
]1. I'm curious why do you call w2k8 driver buggy.
]According to this document
]http://technet.microsoft.com/en-us/library/hh824898.aspx
While I can't speak for Laszlo, it is worth noting that
the INT10 requirement was not added to that
On 05/12/14 18:21, Mike Maslenkin wrote:
>
>>
+ Segment0 = 0;
+ Segment0Pages = 1;
+ Status = gBS->AllocatePages (AllocateAddress, EfiReservedMemoryType,
+ Segment0Pages, &Segment0);
+ if (EFI_ERROR (Status)) {
+goto RestorePam1;
+
On 05/12/14 18:03, Jordan Justen wrote:
> On Mon, May 12, 2014 at 6:18 AM, Laszlo Ersek
> wrote:
>> Additionally, there's another (similarly downstream only) patch
>>
>> OvmfPkg: Don't build in QemuVideoDxe when we have CSM
>>
>> Did you include the presence of this patch in your question?
>
> N
On 05/12/14 16:00, David Woodhouse wrote:
> The addition of UmaAddress/UmaSize fields allows the CSM to have
> writable memory between the top of the option ROMs and the start of
> its read-only code segment.
>
> The HiPermanentMemoryAddress/HiPermanentMemorySize fields added in the
> new spec are
>
> >> + Segment0 = 0;
> >> + Segment0Pages = 1;
> >> + Status = gBS->AllocatePages (AllocateAddress, EfiReservedMemoryType,
> >> + Segment0Pages, &Segment0);
> >> + if (EFI_ERROR (Status)) {
> >> +goto RestorePam1;
> >> + }
> >
> > If CSM is enabled, we will fail
On Mon, May 12, 2014 at 6:18 AM, Laszlo Ersek wrote:
> Additionally, there's another (similarly downstream only) patch
>
> OvmfPkg: Don't build in QemuVideoDxe when we have CSM
>
> Did you include the presence of this patch in your question?
No. I want to remove this patch from being needed, an
Yes I see NetbufAlloc(), NetbufAllocSpace(), NetbufBuildExt(), etc. I guess
I'm looking for more of a conceptual overview of the NET_BUF struct,
particularly in relation to the two scenarios I mentioned. The
documentation in the code describes the details, but doesn't really give an
overview or des
The addition of UmaAddress/UmaSize fields allows the CSM to have
writable memory between the top of the option ROMs and the start of
its read-only code segment.
The HiPermanentMemoryAddress/HiPermanentMemorySize fields added in the
new spec are also added to the table, but not yet supported.
Cont
On 05/10/14 00:49, Jordan Justen wrote:
> On Thu, May 8, 2014 at 10:45 AM, Laszlo Ersek wrote:
>> The Windows 2008 R2 SP1 UEFI guest's default video driver is buggy -- it
>> dereferences the real mode Int10h vector, loads the pointed-to handler
>> code, and executes what it thinks to be VGA BIOS s
Hi Rafael,
Thanks for your answer.
Smbiosview function in UEFI SHELL is exactly what i need. But i how can i put
this functionality into my application?
Regards,
Michał Ciesielski
From: Rafael Machado [mailto:rafaelrodrigues.mach...@gmail.com]
Sent: Friday, May 9, 2014 1:35 PM
T
19 matches
Mail list logo
