Just curious to know if the UNI( for HII ) also need to have similar language
codes to be order to comply with spec?
#string STR_BUS_DEV_FUNC #language en-US "Bus:Dev:Func"
#language fr-FR
"*********."
From: Richardson, Brian [mailto:[email protected]]
Sent: Tuesday, September 18, 2012 12:43 AM
To: [email protected]
Subject: Re: [edk2] Driver name listed as UNKNOWN in shell2
Yes, the ISO language code is different between the two protocols, which
matched changes in the UEFI 2.1 spec related to languages.
Thanks ... br
---
Brian Richardson --
[email protected]<mailto:[email protected]> -- Twitter:
intel_brian
From: Prakash, Sathya [mailto:[email protected]]
Sent: Monday, September 17, 2012 3:01 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [edk2] Driver name listed as UNKNOWN in shell2
Looks like using "en" instead of "en-US" make the "drivers" to display the name
properly.
Thanks
Sathya
From: Prakash, Sathya
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Monday, September 17, 2012 12:30 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [edk2] Driver name listed as UNKNOWN in shell2
Brian,
I have a CompName2 implemented in the driver.
Sameer,
I am using "en-US", should I try with "en"
Thanks
Sathya
From: Richardson, Brian [mailto:[email protected]]
Sent: Monday, September 17, 2012 11:25 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [edk2] Driver name listed as UNKNOWN in shell2
EDK Shell uses ComponentName protocol
Shell 2.0 uses ComponentName2 protocol
Any driver implementing UEFI 2.1+ should implement ComponentName2 protocol, but
I would recommend implementing both.
Use the UEFI Driver Wizard to generate an example implementation in EDK II.
Thanks ... br
---
Brian Richardson --
[email protected]<mailto:[email protected]> -- Twitter:
intel_brian
From: Prakash, Sathya [mailto:[email protected]]
Sent: Monday, September 17, 2012 12:37 PM
To: [email protected]<mailto:[email protected]>
Subject: [edk2] Driver name listed as UNKNOWN in shell2
When I run drivers command my driver's name is listed as UNKNOWN in the shell2.
But with shel1 the same driver shows proper driver name. Is there a need for
drivers to support some additional protocol or interface to support this for
shell2?
Thanks
Sathya
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
