Update Balrog rules to push x86 Widevine CDM to Firefox 67+ on Windows on ARM64
Categories
(Release Engineering :: Release Requests, enhancement)
Tracking
(Not tracked)
People
(Reporter: cpearce, Assigned: jlund)
References
Details
The plan for Firefox on Windows on ARM64 is to use the x86 Widevine CDM on that platform, as we don't have a native aarch64 Widevine CDM.
So we'd like the Balrog rules to be updated so that when Firefox on Windows 10 running on ARM64 polls for an update, we tell Firefox to download the same CDM as used by x86 (32 bit) Windows 10.
So please can we update the Balrog rules so that we download the same Widevine CDM on Firefox on Windows 10 on ARM64, as on x86 Windows 10?
We'd like to start serving the x86 CDM to Windows 10 on ARM64 from Firefox versions 67 or later.
Here's what I think we need to be serving to Firefox67 and later on Windows 10 on ARM64:
<updates>
<addons>
<addon id="gmp-widevinecdm"
URL="https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1146.0-win-ia32.zip"
hashFunction="sha512"
hashValue="d00fb1ce1b7d359ac0f06480d83960fc9aae25f6933e736483c7e27f86ad70a2ca7bfe45027874d1b619d3b72944372d5a7fb124ade4978efdcaeff0cc6c415b"
size="3554840"
version="4.10.1146.0"
/>
</addons>
</updates>
For reference, the GMP download URL that my Lenovo C630 polls running Nightly is:
https://aus5.mozilla.org/update/3/GMP/67.0a1/20190310095404/WINNT_aarch64-msvc-aarch64/en-US/nightly/Windows_NT%2010.0.0.0.17134.590%20(aarch64)/default/default/update.xml
Notes:
- At this time we don't want to be serving an OpenH264 GMP to Firefox on Windows on ARM64.
- Widevine on Windows on ARM64 is currently not visible in the addons UI. We'd like to push the balrog rule update now so that we can enabled it ASAP, should all the other pieces fall into place.
- For testing on an ARM64 Windows laptop, to make Widevine visible in the addons UI, create the prefs media.gmp-widevinecdm.visible=true, and media.gmp-widevinecdm.enabled=true. Note that even if you download a CDM, it won't play EME video until bug 1530245 and bug 1529194 have landed and are in Nightly.
| Reporter | ||
Comment 1•7 years ago
|
||
Release drivers email: https://mail.mozilla.org/private/release-drivers/2019-March/039695.html
| Reporter | ||
Comment 2•7 years ago
|
||
Chris Atlee: Are we able to find someone to look at this please?
| Assignee | ||
Updated•7 years ago
|
| Assignee | ||
Comment 3•7 years ago
•
|
||
(In reply to Chris Pearce [:cpearce (GMT+13)] from comment #0)
The plan for Firefox on Windows on ARM64 is to use the x86 Widevine CDM on that platform, as we don't have a native aarch64 Widevine CDM.
So we'd like the Balrog rules to be updated so that when Firefox on Windows 10 running on ARM64 polls for an update, we tell Firefox to download the same CDM as used by x86 (32 bit) Windows 10.
So please can we update the Balrog rules so that we download the same Widevine CDM on Firefox on Windows 10 on ARM64, as on x86 Windows 10?
We'd like to start serving the x86 CDM to Windows 10 on ARM64 from Firefox versions 67 or later.
Here's what I think we need to be serving to Firefox67 and later on Windows 10 on ARM64:
<updates> <addons> <addon id="gmp-widevinecdm" URL="https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1146.0-win-ia32.zip" hashFunction="sha512" hashValue="d00fb1ce1b7d359ac0f06480d83960fc9aae25f6933e736483c7e27f86ad70a2ca7bfe45027874d1b619d3b72944372d5a7fb124ade4978efdcaeff0cc6c415b" size="3554840" version="4.10.1146.0" /> </addons> </updates>For reference, the GMP download URL that my Lenovo C630 polls running Nightly is:
https://aus5.mozilla.org/update/3/GMP/67.0a1/20190310095404/WINNT_aarch64-msvc-aarch64/en-US/nightly/Windows_NT%2010.0.0.0.17134.590%20(aarch64)/default/default/update.xml
I've set this up against the nightlytest channel. If you change your update channel, you can test this out prior to 67.0+ rollout.
Verified working by resolving:
https://aus5.mozilla.org/update/3/GMP/67.0a1/20190310095404/WINNT_aarch64-msvc-aarch64/en-US/nightlytest/Windows_NT%2010.0.0.0.17134.590%20(aarch64)/default/default/update.xml
<updates><addons><addon id="gmp-widevinecdm" URL="https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1146.0-win-ia32.zip" hashFunction="sha512" hashValue="d00fb1ce1b7d359ac0f06480d83960fc9aae25f6933e736483c7e27f86ad70a2ca7bfe45027874d1b619d3b72944372d5a7fb124ade4978efdcaeff0cc6c415b" size="3554840" version="4.10.1146.0"/></addons></updates>
@cpearce - when you give the greenlight, I can roll this out in production.
note: We are currently in merge week which means 67.0 is now on mozilla-beta already. First 67.0 devedition goes out tomorrow, March 12th, first 67.0 beta goes out next Tues, March 19th. Should we target just 67.0 nightly users at first or both nightly and beta?
| Reporter | ||
Comment 4•7 years ago
|
||
Jordan: I've tested on the nightlytest channel, and it's working as expected.
I think these rules are best targeted as Firefox versions, rather than release channels. So best to target 67, rather than 67 Nightly or Beta. Then we can pref it on in the build of 67 beta if we think it's stable there. If it's not prefed on, Firefox won't download the plugin.
| Assignee | ||
Comment 5•7 years ago
|
||
on slack, cpearce said we could: go ahead and enable aarch64 support via win32 on the updater (balrog) side for all channels and users that are >=67.0?
doing that now
| Assignee | ||
Comment 6•7 years ago
|
||
This is now live on the updater side.
@cpearce - could you resolve this bug if this works for you as expected?
| Reporter | ||
Comment 7•7 years ago
|
||
I've verified with aarch64 Nightly on my Lenovo C630 that this is working as expected.
Description
•