Announcement

Collapse
No announcement yet.

Google Chrome/Chromium Begins Landing POWER PPC64LE Patches

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    starshipeleven
    Premium Supporter

  • starshipeleven
    replied
    Originally posted by ms178 View Post

    Yes, some distros took the blue pill and do ship their Chromium builds with the VAAPI patches included and enabled by default. But I'd rather like to see Google taking the patches and maintain them than pushing the maintanance work to the distros.
    I see more likely to have a community effort that maintains all the stuff Google can't be bothered to accept upstream. Something like "Tuxium".

    Leave a comment:

  • starshipeleven
    Premium Supporter

  • starshipeleven
    replied
    Originally posted by mzs.112000 View Post
    I am thinking about getting one, and maybe it can be used to compile packages for POWER4 Linux. In fact, I wonder how much work it would be to compile Ubuntu 18.04 for PowerPC(I am thinking, compile the packages needed for a base 18.04 install, and then maybe the top 100 extra packages)
    Don't. It runs like crap. It's a decade that runs like crap.

    Leave a comment:

  • starshipeleven
    Premium Supporter

  • starshipeleven
    replied
    Originally posted by schmidtbag View Post
    All that being said, if Chrome/Chromium spent less time implementing bloated features nobody asked for, they could spend more time with things people actually care about like optimizations, architecture-specific patches, and video acceleration.
    The point here is that Google is paying the bills with the additional features, not people using Chromium on Linux.

    Leave a comment:

  • starshipeleven
    Premium Supporter

  • starshipeleven
    replied
    Originally posted by ms178 View Post
    I can't decide yet what will happen sooner, Google accepting the VAAPI patches or POWER9 gaining traction in the consumer desktop segment again.
    Hell will freeze over and pigs will fly

    Leave a comment:

  • ms178
    Senior Member

  • ms178
    replied
    Originally posted by Charlie68 View Post

    In openSUSE, VAAPI hardware acceleration in Chromium is enabled by default and works well on my PCs.
    Yes, some distros took the blue pill and do ship their Chromium builds with the VAAPI patches included and enabled by default. But I'd rather like to see Google taking the patches and maintain them than pushing the maintanance work to the distros.

    Leave a comment:

  • Charlie68
    Senior Member

  • Charlie68
    replied
    Originally posted by -MacNuke- View Post

    Pretty normal for the Chromium Team at Google when it comes to Linux. Look at the VAAPI patches. They are not accepting them for years not even behind a feature flag (except for ChromeOS) because whatever, f*** y** I guess. Distributions became so annoyed that they patch VAAPI in anyways.
    In openSUSE, VAAPI hardware acceleration in Chromium is enabled by default and works well on my PCs.

    Leave a comment:

  • schmidtbag
    Senior Member

  • schmidtbag
    replied
    Originally posted by darkbasic View Post
    I got my hands on a old PowerMac and I tried to use Gentoo on it. For nowadays standards it's waaay slower than you could imagine, so I don't suggest you to buy one. I couldn't make anything useful out of it.
    Haha I could imagine. Pentium 4 is when Intel started to outperform PPC and by around 2004, P4s were already feeling slow.

    Leave a comment:

  • darkbasic
    Senior Member

  • darkbasic
    replied
    Originally posted by mzs.112000 View Post

    The problem is, POWER9 never had traction in the consumer desktop segment. PowerMac's did, but their G5/970MP CPU was POWER4-based.
    Of course, PowerMacs are still the only way to get an affordable POWER development or desktop system, and that's unfortunate because there are no modern GPU's for them(CPU's are still powerful enough to be a reasonable desktop system).

    I am thinking about getting one, and maybe it can be used to compile packages for POWER4 Linux. In fact, I wonder how much work it would be to compile Ubuntu 18.04 for PowerPC(I am thinking, compile the packages needed for a base 18.04 install, and then maybe the top 100 extra packages)
    I got my hands on a old PowerMac and I tried to use Gentoo on it. For nowadays standards it's waaay slower than you could imagine, so I don't suggest you to buy one. I couldn't make anything useful out of it.

    Leave a comment:

  • edwaleni
    Senior Member

  • edwaleni
    replied
    I don't think its laziness on Google's part, its just a matter of priorities. And the datacenter POWER systems are seriously not needing anything from Chromium.

    When Mozilla stopped OS/2 builds, a team forked it into Warpzilla and so it continues.

    The important thing for Chrome on PPC64 LE desktop is getting the codec support along with the vector stuff finished.

    Leave a comment:

  • mzs.112000
    Senior Member

  • mzs.112000
    replied
    Originally posted by ms178 View Post
    I can't decide yet what will happen sooner, Google accepting the VAAPI patches or POWER9 gaining traction in the consumer desktop segment again.
    The problem is, POWER9 never had traction in the consumer desktop segment. PowerMac's did, but their G5/970MP CPU was POWER4-based.
    Of course, PowerMacs are still the only way to get an affordable POWER development or desktop system, and that's unfortunate because there are no modern GPU's for them(CPU's are still powerful enough to be a reasonable desktop system).

    I am thinking about getting one, and maybe it can be used to compile packages for POWER4 Linux. In fact, I wonder how much work it would be to compile Ubuntu 18.04 for PowerPC(I am thinking, compile the packages needed for a base 18.04 install, and then maybe the top 100 extra packages)

    Leave a comment:

Working...
X