Firefox Nightly Expands To Linux On ARM64 (betanews.com) 4
BrianFagioli shares a report from BetaNews: Mozilla has announced Firefox Nightly for ARM64. This release will cater to the growing demand for support on ARM64 platforms, commonly referred to as AArch64. Feedback from the community has led Mozilla to expand the availability of Firefox Nightly. Users can now access the browser as both .tar archives and .deb packages, depending on their preference and requirements for installation.
For those who favor traditional methods, the .tar.bz2 binaries are accessible through Mozilla's downloads page by selecting the option for Firefox Nightly for Linux ARM64/AArch64. Meanwhile, users looking to utilize updates and installation through Mozilla's APT repository can follow specific instructions to install the firefox-nightly package.
For those who favor traditional methods, the .tar.bz2 binaries are accessible through Mozilla's downloads page by selecting the option for Firefox Nightly for Linux ARM64/AArch64. Meanwhile, users looking to utilize updates and installation through Mozilla's APT repository can follow specific instructions to install the firefox-nightly package.
How does this affect Pi? (Score:2)
so if I have things straight, this is the up-and-coming arch that the raspberry pi os uses, so this would seem to be a good development for pi users?
all I know is that pi seems to have great acceleration/codec support for all sorts of stored media files, but falls pretty flat when it comes to streaming youtube. At least through the default browser. App smtube has great codec implementation or acceleration to watch youtube, but is crappy to navigate.
I know Pi foundation is on a budget and all, but it seems n
Re: (Score:2)
I know Pi foundation is on a budget and all, but it seems non-choppy playback of youtube would be high on the list of things to get working after the controlling thermostats and robots part of the work is done.
The various Pis don't have the right hw codecs to accelerate AV1. The best thing it will hw decode is HEVC (H.265). (Pi 4 also does H.264; Pi 5, weirdly, does not.) The raspi people aren't in charge of implementing that or not. Perhaps a future raspi will have a SoC that will do it. If you have to do software decode, the decoder and the browser are then competing for the same resources. That's why static playback is fine but browser-streaming playback is not.
Re: (Score:2)
The various Pis don't have the right hw codecs to accelerate AV1.
yeah except it does have decent playback in a different app (smtube) and I have a hard time believing that's all due to the difference in program overhead, and not at least partly from some difference in the SW decoding.
(Pi 4 also does H.264; Pi 5, weirdly, does not.)
that is strange. I wonder if they were primarily cutting costs or space. Probably costs.