Software > Applications and Porting

Chromium and Ungoogled Chromium DNF Repository

<< < (2/24) > >>

FlyingBlackbird:

--- Quote from: MauryG5 on February 10, 2020, 01:13:53 pm ---Sorry but are we obliged to register on the site just to download a patch? It seems excessive to me ... Now for example it denies me access ...

--- End quote ---

I guess the link is using the wrong path (perhaps to a private repo or the internal CI/CD artefacts).

Nevertheless I think you can find the patches here eg. in the master branch:

https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/tree/master/docker-root/patches/chrome

MauryG5:
Yes good Flying, with your link you will arrive direct. But the questions are 2 for me. First, what exactly is the Patch to activate the acceleration of the dedicated graphics card? Question 2, how do you...

MPC7500:
I'm wondering what do you want to patch?


--- Quote from: vddvss on December 14, 2019, 02:13:48 pm ---…
Notes on Binaries
This build includes a number of additional patches and features:
Patches Included
[*] Patch to enable GPU-accelerated video decoding
[*] Patch to change the browser's user agent string to be the same as the official Chrome build on Linux, which helps reduce the browser's fingerprinting surface
[*] Patch to enable use of POWER VSX instructions in the skia rendering engine
[/list]


--- End quote ---

madscientist159:
First, great job in doing this!  Much appreciated.


--- Quote from: vddvss on December 14, 2019, 02:13:48 pm ---[*] Patch to change the browser's user agent string to be the same as the official

--- End quote ---

While I understand why this is done, it will result in under-reporting of POWER hardware, and my main concern is that Google may look at (in the worst case) no one using POWER (due to the string reporting x86_64) and continue to reject patches.  I don't know if this is a real concern or not, but thought I'd throw it out there for comments.

Worst case the architecture will become just like the rest of the UA string -- spoofed into whatever is most commonly expected for compatibility reasons.  We're not there yet though in terms of market research.

MauryG5:
yes Tim is right, the use of Chromium Power must not be hidden from Google, we have to show that we are here too and that Power has real support is a community that loves and uses it ...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version