安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Yeah, works fine via windows. so who do we have to pester to get miracast support on the steamOS side of things?
The driver for Linux currently doesn't have P2P features - fairly common problem with Linux nearer the cutting edge of tech is the drivers are not all there, though eventually they tend to be. But its the other way round with windoze while its brand new the manufacturer creates the all singing and dancing driver for it but as soon as it gets a little too old drops it entirely so support starts getting spotty.
I'm hoping that gets patched in soon myself, as it would be great for making the deck hugely useful in so many other settings. For instance I have a little battery powered short throw projector it would be great to be able to use it with almost anywhere - huge screen and a decent keyboard would make the deck the portable desktop quality experience for so many things...
The _real_ problem likely has much more to do with closed unfriendly things Chromecast does or requires making it difficult to implement in a way that stays consistent with the values of Linux users. This is why Firefox does not yet have chromecast support.
Chromecast is a very different thing to Miracast/Wi-Fi-Direct display and in this case it is not about the cutting edge of software support as Wi-Fi display does work on Linux, it is the chipset in the Deck being a bit too new for all the peripheral to primary function bells and whistles to be working on Linux - companies obviously tend to priorities their Windoze driver initially. So even if they will sort out and properly support Linux with all the features the hardware supports, getting that driver into the mainline kernel simple takes longer, and if they don't choose to support it usually it just takes longer still as some poor dev ends up reverse engineering what is needed from the windoze driver.
ath9k from 2008 supports p2p client. IHV suck all around.
Do wonder if the OLED decks new chipset just fully works in linux, done some digging but got nothing useful. Would with the great value convince me to 'upgrade'- easier than sourcing and soldering a better supported chip, and not that much more expensive for a risk free option...