Earlier quoted context omitted.
Longer than that. Raspberry Pi isn't that old, it only launched in 2012.
And first arm64 device was released in 2013
Ha, touche! But it worked on ARM long before that :)
Bringing Chrome to ARM64 Linux Devices
61–70 of 78 posts
Re: Bringing Chrome to ARM64 Linux Devices
#62Surely are more ARM64 Linux Devices running Chrome then any other Arch-Kernel combo in history? Not packaging it for common distros when they have built two empires off the kernel was just a choice.
Re: Bringing Chrome to ARM64 Linux Devices
#63a lot of people seem to not understand what used to go into running chrome on arm64 devices, this blog goes over it pretty well https://www.da.vidbuchanan.co.uk/blog/netflix-on-asahi.html
sudo apt install chromium (or chromium-browser in the past)
Re: Bringing Chrome to ARM64 Linux Devices
#64Re: Bringing Chrome to ARM64 Linux Devices
#65Does that mean Widevine DRM will be supported officially? Does anyone know?
Re: Bringing Chrome to ARM64 Linux Devices
#66Earlier quoted context omitted.
This one is so frustrating because aarch64 android would work great under kvm, but it's a pain to set up without the NDK cooperating.
What specifically doesn't work?
I'm not aware of anything specific other than the fact that it's not officially supported as a build target so you have to hack up the build system to make it work. Example: https://github.com/SnowNF/ndk-aarch64-linux
Re: Bringing Chrome to ARM64 Linux Devices
#67Most interesting here is the possibility of Arm64 Widewine libraries appearing?
Re: Bringing Chrome to ARM64 Linux Devices
#68Earlier quoted context omitted.
Why is it easier to run a Linux ARM64 binary on Android than to run an Android ARM64 binary on Linux? My guess is that the reason is the same reason that there aren't official updated Android containers
I don't know what you mean by an "Android ARM64 binary". If you make an ELF file containing ARM64 machine code, it doesn't matter to Linux whether you meant for it to run on Linux in an Android system, on Linux in a desktop GNU system, or on Linux in some environment with without much of a userspace at all (such as a stripped down initramfs environment). If you mean something like an Android app, the answer is that t…
.
CC= clang
CXX=clang++
$CC hello.c -o hello_android_c
$CXX hello.cpp -o hello_android_cpp -static-libstdc++
$CXX hello_asm.cpp -o hello_android_cpp_asm_syscalls_only -ffreestanding -nostdlib -fuse-ld=lld
find -name hello_android -exec readelf -l {} \;
Re: Bringing Chrome to ARM64 Linux Devices
#69Earlier quoted context omitted.
Regular YouTube works as is (but has performance issues on my weak phone.) It's m.youtube.com that seems to require the DRM thing, at least for me. Have you tried that?
m.youtube.com works fine in both Epiphany and Firefox on my Librem 5 with PureOS.
Turns out you’re right. I just uninstalled the CDM and YouTube indeed works!
I’m still absolutely, positively sure that m.youtube.com started gating it for me last August without a doubt. [0]
Maybe they pulled some temporary A/B experiment on me? I’ll probably never know. Thanks for the correction.
Re: Bringing Chrome to ARM64 Linux Devices
#70Earlier quoted context omitted.
Just like any other Ubuntu machine, really. Just lots (128GB) of RAM and relatively lots of cores (10 efficiency, 10 performance). It's not screaming fast, but it's absolutely fast enough for anything I need to do and it's got insanely fast networking options if I need them. I like it, and the local AI options make it fun enough, too. Apart from a few hassles. No pre-packaged Discord or Slack or Chromium or Spotify a…
Chromium has been pre-packaged for ARM in Ubuntu for more than a decade now. Did they throw it away with Snaps?
I’m developing on an Nvidia Orin which requires Ubuntu 22.04. Snaps are broken on this platform. I used an alternative ppa that provided a chromium.deb.