On 04/17/2015 09:52 AM, Mcdaniel, Daryl wrote:
>> I have a question about Python script.
>>
>> Could I call Boot Service function in Python script?
>> Such as:
>> Call BootServices->LocateHandle() in python script!
> Sorry, but that functionality is not yet ready.
> I am working on that right now a
On 05/14/2015 05:58 PM, Hao Wu wrote:
> UEFI 2.5 introduces EFI wireless MAC connection protocol. The header file
> will be added into MdePkg. Wi-Fi device path definition and its node/text
> conversion are added as well.
Hi,
[I'm trying to create a series of blog posts on UEFI 2.5 features (eg,
> I’m not a lawyer….
Here are the places to discuss Open Source Software (and Free Software)
licensing:
http://projects.opensource.org/pipermail/license-discuss/
https://lists.gnu.org/archive/html/gnu-misc-discuss/
--
O
Hi, Ray,
Thank you very much! I have tried your patch and it worked fine on my side.
As I stated in the previous email, the original issue I have with the standard
PciBus driver was in LocatePciExpressCapabilityRegBlock() function.
Regards,
Maurice
-Original Message-
From: Ni, Ruiyu
S
Hi, Ray and Jordan,
Thank you for looking into this.
For the PciBus driver with PcdPciDisableBusEnumeration, the issue was caused
by the deadloop in PciBus driver LocatePciExpressCapabilityRegBlock() function.
PciBus driver should check the return status for
PciIoDevice->PciIo.Pci.Read()
> On May 15, 2015, at 8:52 AM, S.Vieira wrote:
>
> I need get the DevicePath of the File, then i pass the FileName (CHAR16) and
> i want get return as DevicePath to use with LoadImage…
In general device paths are a space namespace that point to a boot device, and
they are a collection of nodes
> On May 15, 2015, at 9:14 AM, Ludovic Rousseau
> wrote:
>
> 2015-05-15 17:55 GMT+02:00 Andrew Fish :
>>
>> On May 15, 2015, at 6:57 AM, Ludovic Rousseau
>> wrote:
>>> - the previous work I reused (existing CCID driver) is licensed under
>>> GNU LGPL v2.1. The new files I wrote to use the pre
2015-05-15 17:55 GMT+02:00 Andrew Fish :
>
> On May 15, 2015, at 6:57 AM, Ludovic Rousseau
> wrote:
>> - the previous work I reused (existing CCID driver) is licensed under
>> GNU LGPL v2.1. The new files I wrote to use the previous driver with
>> UEFI are under the edk2 BSD licence.
>> Is that OK
The file path is the final node in the device path, not the whole thing. Does
your filename have the full path or just the file path? Where is FileName from?
-Jaben
> -Original Message-
> From: S.Vieira [mailto:jwvsan...@outlook.com]
> Sent: Friday, May 15, 2015 8:52 AM
> To: edk2-deve
> On May 15, 2015, at 6:57 AM, Ludovic Rousseau
> wrote:
>
> Hello,
>
> UEFI specification 2.5 now contains a new protocol:
> EFI_SMART_CARD_READER_PROTOCOL detailed in section 35.6.1 page 2241.
>
> I worked on an implementation of this protocol. The implementation is
> based on my existing C
I need get the DevicePath of the File, then i pass the FileName (CHAR16) and
i want get return as DevicePath to use with LoadImage...
I can not to use Shell Protocol.
VOID
GetDevicePathFromText (IN CHAR16* FileName,IN EFI_HANDLE ImageHandle)
{
EFI_GUID
Hello,
UEFI specification 2.5 now contains a new protocol:
EFI_SMART_CARD_READER_PROTOCOL detailed in section 35.6.1 page 2241.
I worked on an implementation of this protocol. The implementation is
based on my existing CCID driver [1].
The driver can (should be able to) use any compliant CCID [2]
The root cause is SerialPortDebugCommunicationLib returns NULL debug port
handle causing the CompressData() doesn't send the compressed data.
The fix doesn't rely on the debug port handle value and uses Send parameter to
indicate whether to send the compressed data.
Contributed-under: TianoCore
On Fri, 15 May 2015 16:57:02 +0530
Anindya Rai wrote:
> UEFI spec doesn't talk about the EFI_DISK_INFO_PROTOCOL. I am
> implementing a UEFI Option ROM for a pci based device. Do I need to
> install disk info protocol on my Option ROM Driver?
>
Apparently this protocol is defined in EFI 1.0 and
UEFI spec doesn't talk about the EFI_DISK_INFO_PROTOCOL. I am implementing
a UEFI Option ROM for a pci based device. Do I need to install disk info
protocol on my Option ROM Driver?
--
Regards:
Anindya Rai
--
One dashboar
Reviewed-by: Liming Gao
-Original Message-
From: Ruiyu Ni [mailto:ruiyu...@intel.com]
Sent: Friday, May 15, 2015 2:08 PM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] [Patch 0/6] Add UNI files for BDS core modules/libraries
Ruiyu Ni (6):
MdeModulePkg: Add UNI file for BdsDxe dr
16 matches
Mail list logo
