Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
But why bringing discussion about kernel and glibc patches here?
Are there any problems with getting those changes accepted into upstream by corresponding project maintainers?
I find myself wondering if anybody is testing these changes on a AMD APU based Chromebook using Steam installed through ChromeOS's native Debian Package support?
I doubt anyone is testing this particular configuration, since it's quite extraordinary, but you can be the one to test and report issues. That's how Free Software actually work. Must add, I presume, those issues should be driver related, not Proton related.
Also, while common, this is pretty perverted configuration for a GNU/Linux PC.
May I ask what's your reason of using it. Is getting something better not an option for you?