Hi,
Regarding the sync() question. Does it actually do anything if I find all
Simple File Systems, open up the volume, run a .Flush then close them?
Thinking at that point any cached data, no matter who put it there whenever
they put it there, should be flushed (the volume is shared?) Or would
Hi All,
My Intel board is connected with PCI Express to SCSI controller and three
SCSI devices connected on PCI (SCSI controller)device.
>From EFI shell I would like to Display connected SCSI devices details (SCSI
device size,Speed of the Device)
I have started to implement as a UEFI driver for
Can you send with the "submitted-by:" and attestation to follow the standard
code-submission process?
Thanks
-Jaben
-Original Message-
From: Sergei Antonov [mailto:sap...@gmail.com]
Sent: Tuesday, September 17, 2013 5:17 AM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] ShellPkg p
On Sep 18, 2013, at 5:59 AM, "Cohen, Eugene" wrote:
> Ø I've noticed various seemingly "random" asserts like this before and
> suspect it may be related. Of course, the assert output never helps track
> down the culprit, but that's a different issue altogether.
>
> A call stack dump, either
Hello,
I am testing a GBE LAN 82579 using the Driver Diagnostics Protocol
implemented by the "UEFI Network Device Driver for IntelR Ethernet Network
Connections".
I downloaded the driver from
http://www.intel.com/support/ethernetcomponents/controllers/82579/sb/CS-0322
39.htm
The success rate of
Ø I've noticed various seemingly "random" asserts like this before and suspect
it may be related. Of course, the assert output never helps track down the
culprit, but that's a different issue altogether.
A call stack dump, either with a debugger or some additional crash handling
code should do
Rod,
On 09/18/13 01:24, Jordan Justen wrote:
> QEMU 1.6 enables using KVM READONLY memory regions. There
> appears to be a bug when page tables are stored in the
> READONLY memory region. To work-around this, we create
> page table entries in RAM. Since RAM is present in QEMU/KVM
> without any ini
On 09/17/13 18:54, Olivier Martin wrote:
> This patchset introduces the new protocol VIRTIO_DEVICE_PROTOCOL that
> abstracts the VirtIo transport layer.
> It allows to enable VirtIo on devices that do not have PCI support.
> These devices might use a memory mapped view of the VirtIo controller
> (s
On 09/18/13 11:22, Olivier Martin wrote:
>
>
>> -Original Message-
>> From: Jordan Justen [mailto:jljus...@gmail.com]
>> Sent: 18 September 2013 05:53
>> To: Olivier Martin; Laszlo Ersek
>> Cc: edk2-devel@lists.sourceforge.net
>> Subject: Re: [edk2] [PATCH 3/8] OvmfPkg/VirtioPciDeviceDxe:
> -Original Message-
> From: Jordan Justen [mailto:jljus...@gmail.com]
> Sent: 18 September 2013 05:53
> To: Olivier Martin; Laszlo Ersek
> Cc: edk2-devel@lists.sourceforge.net
> Subject: Re: [edk2] [PATCH 3/8] OvmfPkg/VirtioPciDeviceDxe: Implement
> VIRTIO_DEVICE_PROTOCOL for VirtIo Devi
Hi,
I'm doing a lot of DisconnectController/ConnectController against
gEfiSimpleFileSystemProtocolGuid and that's working fine, but I saw huge
memory leaks 4M on virtualbox 500K on physical machine, etc.. For a test I
stopped all/most of that but left the program end left part that will
locate Bl
11 matches
Mail list logo
