Added EnableVectorAcceleration key and description

@bluehomewu @btwise @droofy @socialskyo

Added EnableVectorAcceleration key and description
@bluehomewu @btwise @droofy @socialskyo
ee60cf60 · mackie100 · 4aee8ec7 · ee60cf60 · ee60cf60 · ee60cf60
5 changed file
--- a/Chinese, Simplified Localization (zh-Hans)/Sections/uefiController.strings
+++ b/Chinese, Simplified Localization (zh-Hans)/Sections/uefiController.strings
@@ -23,6 +23,9 @@
 /* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Reconnect console controllers after changing screen resolution.\n\nOn certain firmware, the controllers that produce the console protocols (simple text out) must be reconnected when the screen resolution is changed via GOP. Otherwise, they will not produce text based on the new resolution.\n\nNote: On several boards this logic may result in black screen when launching OpenCore from Shell and thus it is optional. In versions prior to 0.5.2 this option was mandatory and not configurable. Please do not use this unless required."; ObjectID = "1QT-lu-i79"; */
 "1QT-lu-i79.ibShadowedToolTip" = "有些固件在 GOP 分辨率改变后要求重新连接控制器才能输出文本, 开启这个选项会导致从 UEFI Shell 中启动 OpenCore 时直接黑屏, 尽量避免开启.\n如果你遇到开机直到登录界面之前一直是黑屏,请试试选择 YES.";

+/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms."; ObjectID = "2Bt-b4-cNE"; */
+"2Bt-b4-cNE.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms.";
+
 /* Class = "NSButtonCell"; title = "ForceResolution"; ObjectID = "2kV-J6-o4B"; */
 "2kV-J6-o4B.title" = "ForceResolution";

@@ -59,6 +62,9 @@
 /* Class = "NSTextFieldCell"; title = "CustomDelays"; ObjectID = "5zT-C9-V64"; */
 "5zT-C9-V64.title" = "CustomDelays";

+/* Class = "NSButtonCell"; title = "EnableVectorAcceleration"; ObjectID = "63M-Ew-u4v"; */
+"63M-Ew-u4v.title" = "EnableVectorAcceleration";
+
 /* Class = "NSButtonCell"; title = "JumpstartHotPlug"; ObjectID = "6B4-NA-lHR"; */
 "6B4-NA-lHR.title" = "JumpstartHotPlug";

@@ -458,7 +464,7 @@
 /* Class = "NSTextFieldCell"; title = "ExitBootServicesDelay"; ObjectID = "wxD-TC-lrQ"; */
 "wxD-TC-lrQ.title" = "ExitBootServicesDelay";

-/* Class = "NSTextField"; ibShadowedToolTip = "Type: plist integer\nFailsafe: 0\nDescription: Treat duplicate key presses as held keys if they arrive during this timeout, in 10 ms units. Only applies to systems using KeySupport.\n\nAppleKeyMapAggregator protocol is supposed to contain a fixed length buffer of currently pressed keys. However, the majority of the drivers which require KeySupport report key presses as interrupts, with automatically generated key repeat behaviour with some defined initial and subsequent delay. As a result, to emulate the raw key behaviour required by several Apple boot systems, we use a timeout to merge multiple repeated keys which are submitted within a small timeout window\n\nThis option allows setting this timeout based on the platform. The recommended value for the majority of platforms is from 5 (50 milliseconds) to 7 (70 milliseconds), although values up to 9 (90 milliseconds) have been observed to be required on some PS/2 systems.For reference, holding a key on VMware will repeat roughly every 20 milliseconds and the equivalent value for APTIO V is 30-40 milliseconds. KeyForgetThreshold should be configured to be longer than this. Thus, it is possible to configure a lower KeyForgetThreshold value on platforms with a faster native driver key repeat rate, for more responsive input, and it is required to set a higher value on slower platforms.\n\nPressing keys one after the other results in delays of at least 60 and 100 milliseconds for the same platforms. Ideally, KeyForgetThreshold should remain lower than this value, to avoid merging real key presses.\n\nNote}: If you wish to fine tune this value, a good heuristic is to use the 'set default' indicator within either OpenCanopy or the builtin picker. When KeyForgetThreshold is configured correctly, this indicator should flicker once, when first pressing and holding the CTRL key, and then after a further very brief interval should go on and stay on. (The initial flicker is an unavoidable artefact of using KeySupport to emulate raw keyboard data.) If KeyForgetThreshold is configured too low for the system, then the 'set default' indicator will continue to flicker while CTRL is held. Configure the lowest value which causes this indicator to go on and stay on after the first initial flicker."; ObjectID = "xNH-9V-3kd"; */
+/* Class = "NSTextField"; ibShadowedToolTip = "Type: plist integer\nFailsafe: 0\nDescription: Treat duplicate key presses as held keys if they arrive during this timeout, in 10 ms units. Only applies to systems using KeySupport.\n\nAppleKeyMapAggregator protocol is supposed to contain a fixed length buffer of currently pressed keys. However, the majority of the drivers which require KeySupport report key presses as interrupts, with automatically generated key repeat behaviour with some defined initial and subsequent delay. As a result, to emulate the raw key behaviour required by several Apple boot systems, we use a timeout to merge multiple repeated keys which are submitted within a small timeout window\n\nThis option allows setting this timeout based on the platform. The recommended value for the majority of platforms is from 5 (50 milliseconds) to 7 (70 milliseconds), although values up to 9 (90 milliseconds) have been observed to be required on some PS/2 systems.For reference, holding a key on VMware will repeat roughly every 20 milliseconds and the equivalent value for APTIO V is 30-40 milliseconds. KeyForgetThreshold should be configured to be longer than this. Thus, it is possible to configure a lower KeyForgetThreshold value on platforms with a faster native driver key repeat rate, for more responsive input, and it is required to set a higher value on slower platforms.\n\nPressing keys one after the other results in delays of at least 60 and 100 milliseconds for the same platforms. Ideally, KeyForgetThreshold should remain lower than this value, to avoid merging real key presses.\n\nTuning the value of KeyForgetThreshold is necessary for accurate and responsive keyboard input on systems on which KeySupport is enabled, and it is recommended to follow the instructions below to tune it correctly for your system.\n\nNote 1: To tune KeyForgetThreshold, you may use the 'set default' indicator within either OpenCanopy or the builtin picker. If KeyForgetThreshold is too low then the 'set default' indicator will continue to flicker while CTRL or =/+ is held down. You should configure the lowest value which avoids this flicker. On some systems (e.g. Aptio IV and potentially other systems using AMI KeySupport mode) you will be able to find a minimum KeyForgetThreshold value at which the 'set default' indicator goes on and stays on with no flicker at all - if so, use this value. On most other systems using KeySupport, you will find that the 'set default' indicator will flicker once, when first pressing and holding the CTRL or =/+ key, and then after a further very brief interval will go on and stay on. On such systems, you should chose the lowest value of KeyForgetThreshold at which you see only one initial flicker and then no subsequent flickering. (Where this happens, it is an unavoidable artefect on those systems of using KeySupport to emulate raw keyboard data, which is not made available by UEFI.)\n\nNote 2: KeyForgetThreshold should never need to be more than about 9 or 10 at most. If it is set to a value much higher than this, it will result in noticeably unresponsive keyboard input. Therefore, for overall key responsiveness, it is strongly recommended to configure a relatively lower value, at which the 'set default' indicator flickers once and then does not flicker, rather than using a much higher value (i.e. significantly greater than 10), which you may be able to find but should not use, where the 'set default' indicator does not flicker at all."; ObjectID = "xNH-9V-3kd"; */
 "xNH-9V-3kd.ibShadowedToolTip" = "按住按键后每个键之间的时间间隔 (单位: 毫秒)\n此选项允许根据您的平台设置此超时. 在大多数平台上均可使用的建议值为5毫秒. 作为参考,在VMware上按住一个键大约每2毫秒重复一次,而APTIO V的相同值是3-4毫秒. 因此,可以在较快的平台上设置稍低的值,而在较慢的平台上设置稍高的值,以提高响应速度.";

 /* Class = "NSButtonCell"; title = "CustomDelays"; ObjectID = "xPB-Sk-c8h"; */

--- a/Chinese, Traditional Localization (zh-Hant)/Sections/uefiController.strings
+++ b/Chinese, Traditional Localization (zh-Hant)/Sections/uefiController.strings
@@ -23,6 +23,9 @@
 /* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Reconnect console controllers after changing screen resolution.\n\nOn certain firmware, the controllers that produce the console protocols (simple text out) must be reconnected when the screen resolution is changed via GOP. Otherwise, they will not produce text based on the new resolution.\n\nNote: On several boards this logic may result in black screen when launching OpenCore from Shell and thus it is optional. In versions prior to 0.5.2 this option was mandatory and not configurable. Please do not use this unless required."; ObjectID = "1QT-lu-i79"; */
 "1QT-lu-i79.ibShadowedToolTip" = "有些韌體在 GOP 解析度改變後要求重新連接控制器才能輸出文字, 開啟這個選項會導致從 UEFI Shell 中啟動 OpenCore 時直接黑畫面, 盡量避免開啟。\n如果你遇到開機直到登入界面之前一直是黑畫面，請試試選擇 YES。";

+/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms."; ObjectID = "2Bt-b4-cNE"; */
+"2Bt-b4-cNE.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms.";
+
 /* Class = "NSButtonCell"; title = "ForceResolution"; ObjectID = "2kV-J6-o4B"; */
 "2kV-J6-o4B.title" = "ForceResolution";

@@ -59,6 +62,9 @@
 /* Class = "NSTextFieldCell"; title = "CustomDelays"; ObjectID = "5zT-C9-V64"; */
 "5zT-C9-V64.title" = "CustomDelays";

+/* Class = "NSButtonCell"; title = "EnableVectorAcceleration"; ObjectID = "63M-Ew-u4v"; */
+"63M-Ew-u4v.title" = "EnableVectorAcceleration";
+
 /* Class = "NSButtonCell"; title = "JumpstartHotPlug"; ObjectID = "6B4-NA-lHR"; */
 "6B4-NA-lHR.title" = "JumpstartHotPlug";


--- a/English Localization (en)/Sections/uefiController.strings
+++ b/English Localization (en)/Sections/uefiController.strings
@@ -23,6 +23,9 @@
 /* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Reconnect console controllers after changing screen resolution.\n\nOn certain firmware, the controllers that produce the console protocols (simple text out) must be reconnected when the screen resolution is changed via GOP. Otherwise, they will not produce text based on the new resolution.\n\nNote: On several boards this logic may result in black screen when launching OpenCore from Shell and thus it is optional. In versions prior to 0.5.2 this option was mandatory and not configurable. Please do not use this unless required."; ObjectID = "1QT-lu-i79"; */
 "1QT-lu-i79.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nDescription: Reconnect console controllers after changing screen resolution.\n\nOn certain firmware, the controllers that produce the console protocols (simple text out) must be reconnected when the screen resolution is changed via GOP. Otherwise, they will not produce text based on the new resolution.\n\nNote: On several boards this logic may result in black screen when launching OpenCore from Shell and thus it is optional. In versions prior to 0.5.2 this option was mandatory and not configurable. Please do not use this unless required.";

+/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms."; ObjectID = "2Bt-b4-cNE"; */
+"2Bt-b4-cNE.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms.";
+
 /* Class = "NSButtonCell"; title = "ForceResolution"; ObjectID = "2kV-J6-o4B"; */
 "2kV-J6-o4B.title" = "ForceResolution";

@@ -59,6 +62,9 @@
 /* Class = "NSTextFieldCell"; title = "CustomDelays"; ObjectID = "5zT-C9-V64"; */
 "5zT-C9-V64.title" = "CustomDelays";

+/* Class = "NSButtonCell"; title = "EnableVectorAcceleration"; ObjectID = "63M-Ew-u4v"; */
+"63M-Ew-u4v.title" = "EnableVectorAcceleration";
+
 /* Class = "NSButtonCell"; title = "JumpstartHotPlug"; ObjectID = "6B4-NA-lHR"; */
 "6B4-NA-lHR.title" = "JumpstartHotPlug";


--- a/French Localization (fr)/Sections/uefiController.strings
+++ b/French Localization (fr)/Sections/uefiController.strings
@@ -23,6 +23,9 @@
 /* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Reconnect console controllers after changing screen resolution.\n\nOn certain firmware, the controllers that produce the console protocols (simple text out) must be reconnected when the screen resolution is changed via GOP. Otherwise, they will not produce text based on the new resolution.\n\nNote: On several boards this logic may result in black screen when launching OpenCore from Shell and thus it is optional. In versions prior to 0.5.2 this option was mandatory and not configurable. Please do not use this unless required."; ObjectID = "1QT-lu-i79"; */
 "1QT-lu-i79.ibShadowedToolTip" = "Certains micrologiciels nécessitent de reconnecter le contrôleur pour afficher le texte après la modification de la résolution GOP. L'activation de cette option entraînera la disparition de l'écran lors du démarrage d'OpenCore à partir du shell UEFI. \n Si vous rencontrez un écran noir jusqu'à l'écran de connexion, veuillez essayer de sélectionner OUI.";

+/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms."; ObjectID = "2Bt-b4-cNE"; */
+"2Bt-b4-cNE.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms.";
+
 /* Class = "NSButtonCell"; title = "ForceResolution"; ObjectID = "2kV-J6-o4B"; */
 "2kV-J6-o4B.title" = "ForceResolution";

@@ -59,6 +62,9 @@
 /* Class = "NSTextFieldCell"; title = "CustomDelays"; ObjectID = "5zT-C9-V64"; */
 "5zT-C9-V64.title" = "CustomDelays";

+/* Class = "NSButtonCell"; title = "EnableVectorAcceleration"; ObjectID = "63M-Ew-u4v"; */
+"63M-Ew-u4v.title" = "EnableVectorAcceleration";
+
 /* Class = "NSButtonCell"; title = "JumpstartHotPlug"; ObjectID = "6B4-NA-lHR"; */
 "6B4-NA-lHR.title" = "JumpstartHotPlug";


--- a/Korean Localization (ko)/Sections/uefiController.strings
+++ b/Korean Localization (ko)/Sections/uefiController.strings
@@ -23,6 +23,9 @@
 /* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Reconnect console controllers after changing screen resolution.\n\nOn certain firmware, the controllers that produce the console protocols (simple text out) must be reconnected when the screen resolution is changed via GOP. Otherwise, they will not produce text based on the new resolution.\n\nNote: On several boards this logic may result in black screen when launching OpenCore from Shell and thus it is optional. In versions prior to 0.5.2 this option was mandatory and not configurable. Please do not use this unless required."; ObjectID = "1QT-lu-i79"; */
 "1QT-lu-i79.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nDescription: Reconnect console controllers after changing screen resolution.\n\nOn certain firmware, the controllers that produce the console protocols (simple text out) must be reconnected when the screen resolution is changed via GOP. Otherwise, they will not produce text based on the new resolution.\n\nNote: On several boards this logic may result in black screen when launching OpenCore from Shell and thus it is optional. In versions prior to 0.5.2 this option was mandatory and not configurable. Please do not use this unless required.";

+/* Class = "NSButton"; ibShadowedToolTip = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms."; ObjectID = "2Bt-b4-cNE"; */
+"2Bt-b4-cNE.ibShadowedToolTip" = "Type: plist boolean\nFailsafe: false\nDescription: Enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms.";
+
 /* Class = "NSButtonCell"; title = "ForceResolution"; ObjectID = "2kV-J6-o4B"; */
 "2kV-J6-o4B.title" = "ForceResolution";

@@ -59,6 +62,9 @@
 /* Class = "NSTextFieldCell"; title = "CustomDelays"; ObjectID = "5zT-C9-V64"; */
 "5zT-C9-V64.title" = "CustomDelays";

+/* Class = "NSButtonCell"; title = "EnableVectorAcceleration"; ObjectID = "63M-Ew-u4v"; */
+"63M-Ew-u4v.title" = "EnableVectorAcceleration";
+
 /* Class = "NSButtonCell"; title = "JumpstartHotPlug"; ObjectID = "6B4-NA-lHR"; */
 "6B4-NA-lHR.title" = "JumpstartHotPlug";