Yes. But when the system goes back to Legacy Environment we need to change the
timer interval to 54ms as this is IBM standard .
Thanks,
Ramesh
From: galla rao [mailto:gallagnv@gmail.com]
Sent: Monday, September 16, 2013 6:55 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] SetTime
Hi,
Tracking down a crash I am seeing shows that I am effectively calling
FreePool() with a NULL pointer. The system then ASSERTS and hangs.
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 cu
Hi,
So are the handles you get back from LocateHandleBuffer when searching for
say the gEfiSimpleFileSystemProtocolGuid or gEfiBlockIoProtocolGuid
considered "controller handles"?
so when you disconnectcontroller you do it on the child, then
connectcontroller on the parent giving the child sufix?
Hi Feng,
Yes, it is good. I was also thinking that 0 may be right value. (not in my
case).
Sergey.
On 17.09.2013, at 7:00, "Tian, Feng" wrote:
> Hi, Sergey
>
> Please help review the patch.
>
> The patch has a little different with yours as value 0 may be the correct
> return value for so
.. while I can remember .. Under OVMF (would guess it's using shared code
others would be), if you have a EFI_SIMPLE_FILE_SYSTEM_PROTOCOL you want to
try and coexist with direct access to drive in a way safe from hot-swap
there are issue. If you attempt to open that device path (returned with
Loca
Hi, Sergey
Please help review the patch.
The patch has a little different with yours as value 0 may be the correct
return value for some XHCI cards which supports USB Legacy Support Capability.
Thanks
Feng
From: Tian, Feng
Sent: Monday, September 16, 2013 15:57
To: edk2-devel@lists.sourceforge
Hi,
I open exclusive access to the device path for a given block io device. I
want to ensure the structure (protocol) doesn't go away while in a
routine. Meanwhile a support routine will take a handle to a mounted file
system on that same block io device and attempt to use the
DevicePathFromHand
Is there a reason that you are writing a drive and not a UEFI Shell application?
-Jaben
From: Murali Selvaraj [mailto:murali.selvaraj2...@gmail.com]
Sent: Monday, September 16, 2013 9:25 AM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] PCI-SAS controller
Hi All,
My intel board has multip
Hi All,
My intel board has multiple PCIe slots,one of slots connected with PCI
Express to 4-Port Serial Attached SCSIController.On this SAS controller
I have connected three SCSI devices from the on board SAS slots.
I need to write a driver which will display the connected scsi devices with
the f
Are you planning to write a UEFI Shell Application, UEFI Application (without
shell), or a UEFI Driver?
There are many possible methods to do what you're trying to do.
-Jaben
From: parmeshwr_pra...@dell.com [mailto:parmeshwr_pra...@dell.com]
Sent: Monday, September 16, 2013 8:03 AM
To: edk2-dev
On Sep 16, 2013, at 11:11 AM, "Richardson, Brian"
wrote:
> OVMF is the best option for development in an emulator.
>
Well that kind of depends what you are developing. But it is a good
opportunity to discuss the differences.
The Nt32Pkg and EmulatorPkg are OS Applications that produc
Hi Jaben,
Is there a reason that you are writing a drive and not a UEFI
Shell application?
I don't have any specific reason.Please help on my query?
On Mon, Sep 16, 2013 at 9:59 PM,
wrote:
> Send edk2-devel mailing list submissions to
> edk2-devel@lists.sourceforge.net
>
> To subs
On Sep 16, 2013, at 1:16 PM, Laszlo Ersek wrote:
> On 09/16/13 21:50, Andrew Fish wrote:
>
>> OVMF:
>> Limitations: Requires QEMU, serial port debugging (not well
>> documented), more complex setup.
>
> I agree that the setup is complex.
>
> Regarding serial port debugging... Could you sugges
On 09/16/13 17:57, Josh Triplett wrote:
>> The edk2 commit that flipped the memory type underneath the image data
>> from EfiReservedMemoryType to EfiBootServicesData is:
>>
>> https://github.com/tianocore/edk2/commit/4c58575e
>>
>> I think this commit is wrong. It's fine for OSPM to release t
On 09/16/13 12:59, Matt Fleming wrote:
> On Fri, 13 Sep, at 02:38:12PM, jerry.hoem...@hp.com wrote:
>> Matt,
>>
>> We have hit an issue on our new platform in development related to the
>> call of efi_reserve_boot_services() from setup_arch().
>>
>> The reservation can interfere with allocation of
On Mon, Sep 16, 2013 at 06:25:22PM +0200, Laszlo Ersek wrote:
> Or are you alluding to UEFI firmware that's not based on TianoCore?
Most BGRT implementations are IBV specific rather than coming from
Tiano. The ACPI spec says that the image should be stored in
EfiBootServicesData, and most imple
On Fri, 13 Sep, at 02:38:12PM, jerry.hoem...@hp.com wrote:
> Matt,
>
> We have hit an issue on our new platform in development related to the
> call of efi_reserve_boot_services() from setup_arch().
>
> The reservation can interfere with allocation of the crash kernel.
Jerry, thanks for bringin
On 09/16/13 20:20, Andrew Fish wrote:
>
> On Sep 16, 2013, at 6:43 AM, "okosmy...@kraftway.ru
>> /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info):
>> relocation 19 has invalid symbol index 12
>> /usr/bin/ld:
>> /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info):
>> relocation
On 09/16/13 21:50, Andrew Fish wrote:
> OVMF:
> Limitations: Requires QEMU, serial port debugging (not well
> documented), more complex setup.
I agree that the setup is complex.
Regarding serial port debugging... Could you suggest how / where to
improve the documentation? "OvmfPkg/README" says
The Platform choses a timer granularity. In a PI platform it is the Timer Arch
Protocol that choses. So the producer of gEfiTimerArchProtocolGuid picks.
In general EFI does not specify these kind of requirements. So basically the
contract is you will not get called faster than the timer period,
On Sep 16, 2013, at 6:43 AM, "okosmy...@kraftway.ru"
wrote:
> /usr/bin/ld: /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info):
> relocation 0 has invalid symbol index 10
> /usr/bin/ld: /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info):
> relocation 1 has invalid symbol inde
OVMF is the best option for development in an emulator.
Thanks ... br
---
Brian Richardson -- brian.richard...@intel.com -- Twitter: intel_brian
-Original Message-
From: Blibbet [mailto:blib...@gmail.com]
Sent: Monday, September 16, 2013 2:08 PM
To: edk2-devel@lists.sourceforge.net
Subj
On Sep 16, 2013, at 11:07 AM, Blibbet wrote:
> Hi,
>
> I've only used the NT-based emulator, and am now trying to get the
> proper emulator to run on Linux (Ubuntu 12.x).
>
> Sorry for a newbie question, but which is the proper direction to be
> trying, UnixPkg or EmulatorPkg? Long term it s
Hi,
I've only used the NT-based emulator, and am now trying to get the
proper emulator to run on Linux (Ubuntu 12.x).
Sorry for a newbie question, but which is the proper direction to be
trying, UnixPkg or EmulatorPkg? Long term it sounds like Emulator, but
what works better today?
I haven't
Murali,
Map names in the shell are like "FS0" or "FS1" and represent each file system.
Unless you need to do raw writing, it's a lot easier to let the other
drivers/applications help you.
I would use ShellProtocol functions:
GetDevicePathFromMap() (for each map item)
Then determine which devi
Dell - Internal Use - Confidential
Hi All,
I need to search the SCSI in system and then want to write some data on HDD.
Can anybody help me how to proceed with that.
Some idea I have like
1- From gBS openprotocol for scsi
2- Then get device type
Required
1- How to get HDD ID t
/usr/bin/ld: /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info):
relocation 0 has invalid symbol index 10
/usr/bin/ld: /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info):
relocation 1 has invalid symbol index 11
/usr/bin/ld: /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_
Thanks Ramesh for your inputs
Does it mean that if platform BIOS supports HPET timer
I can have a callback for lesser granularity than 54ms
Hope this is what you are trying to convey
Thanks Ramesh & Sergey for your inputs
I would try and see if it helps me
On Mon, Sep 16, 2013 at 5:49 PM, Rame
Hello Ranga,
The Legacy environment assumed that 18.4 times Timer 0 gets generated per
Second. It means Timer 0 IRQ raised for every 54ms.
By using the HPET timer we could change the timer frequency to lesser values
and when we switch to Legacy environment we could change it back to 54ms as
Hello,
I'll recommend you to look into
edk2/DuetPkg/Library/DuetTimerLib
that uses more precise AcpiTimer
Hope ti helps,
Sergey
On 16.09.2013, at 14:52, galla rao wrote:
> Hello All,
>
> Can anyone help me understand what is the minimum Timer Granularity for
> gBS->SetTimer
> When i have wri
Hello All,
Can anyone help me understand what is the minimum Timer Granularity for
gBS->SetTimer
When i have written a callback with 50ms(milli seconds), The calls seems to
be taking a value close
to 50ms
In the 8254Timerdxe the following comments are given about timer ticks
//
// The PCAT 8253/
Thanks for your reply Jordan
On Fri, Sep 13, 2013 at 12:39 PM, Jordan Justen wrote:
> On Thu, Sep 12, 2013 at 12:18 AM, galla rao
> wrote:
> > Dear All,
> >
> > I ported a OptionRom Code from EDK to UDK and found my .efi output file
> has
> > increased from ~700k to ~1100k
> >
> > Building Cod
Thanks Garrett for your contribution,
I have reviewed and submitted your patch in SVN rev14675.
Olivier
From: Kirkendall, Garrett [mailto:garrett.kirkend...@amd.com]
Sent: 13 September 2013 17:40
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] AARCH64 patch: Fix address calculation over
Yes, you are right. Usb Legacy Support Capability is optional, we should ignore
it if the XHCI controller doesn't support this feature.
I will follow up it as soon as possible.
From: Sergey Isakov [mailto:isakov...@bk.ru]
Sent: Monday, September 16, 2013 15:33
To: edk2-devel@lists.sourceforge.ne
Dear sirs,
I found new issue with XhciDxe driver.
I have USB3 PCIe adapter with chip VIA VL800-Q8. It works but the code
Xhc->UsbLegSupOffset = XhcGetLegSupCapAddr (Xhc);
returns Zero.
And then in procedure
--
VOID
XhcSetBiosOwnership (
IN USB_XHCI_INSTANCE*X
35 matches
Mail list logo
