安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題
Nowadays all Optimus laptops are build without a multiplexer (MUX-less), that means the Nvidia GPU has no physical connection whatsoever to the laptop screen. The driver has to cooperate with the driver of the Intel GPU, as the Intel GPU is the only one that can put *anything* on the display.
Bumblebee is actually just starting a second X Server using an OpenGL wrapper library and uses your primary X Server for displaying its stuff. This is very inefficient. The most efficient way of realizing this cooperation is to create a buffer sharing mechanism right on driver/kernel level. However, there are some serious legal barriers as this mechanism is rather invasive - and I don't see this clearing up in the near future, Wayland will probably put everything into chaos first with its requirements for KMS and EGL.
As far as I can tell most AMD based hybrid systems (as well as a few of the first Optimus ones) actually still have a multiplexer. It makes things rather simple and efficient, you just need to support the multiplexer to tell it what GPU to use and AMD actually has some kind of support for it in their proprietary driver (using some dirty script voodoo to switch between OpenGL libs etc when combined with a Intel GPU). The only drawback is that each switch requires a restart of the X Server as it is not (yet?) able to switch GPUs on-the-fly.