Originally posted by DoMiNeLa10
View Post
Announcement
Collapse
No announcement yet.
Linux 5.5 Adding Wake-On-Voice Support - Capable On Some Chromebook Hardware
Collapse
X
-
Originally posted by Danny3 View PostWhat is Wake-On-Voice ?
This looks to me like keeping the mike on even in sleep mode to listen for the wake up word, but I assume they care more about the spyware capability.
Hopefully I'm wrong.
Comment
-
Originally posted by archsway View Post"Ok Google, can you let me boot this time?"
"No Google, not into Chrome OS, can't you see that SD card with a "ChromeOS kernel" partition? I've set the priority flag on it just the way you like it."
"By the way, Google, why is there network activity to google.com when I'm not using Chrome OS and haven't got a browser open?"
I couldn't find any information on the MT6358, but the MT8183 uses a G72 GPU, which doesn't have good support in Mesa at the moment, AFAICT.
But whatever you do, stay away from the MT8173, which has PowerVR graphics.
Instead consider something with an RK3399 (a few Chromebooks, as well as the Pinebook Pro), which has pretty good GPU support in Mesa.
Comment
-
Originally posted by archsway View Post
If the driver was in userspace, how would the keyboard, suspend, RTC, pstore etc. work?
Comment
-
Originally posted by sandy8925 View Post
RK3399 has Mali GPU, and the only open source driver is the Lima driver which is also reverse engineered like all of the other GPUs shipped on ARM devices. How is that any better than the PowerVR GPU?
Comment
-
Originally posted by Michael View Post
Different topics, different articles.
Obviously I can't speak for everyone. The person who you replied to obviously has their own preference.
I only want to read a long, wordy, article if I'm actually studying a topic in detail. I read Phoronix more to stay up to date, learn about new things and just enjoy reading about technological advancements (particularly in Open Source, GNU/Linux and software in general).
Thanks.
Comment
-
Originally posted by Michael View Post
It needs to interact with the audio codecs and EC, so those bits need to be in the kernel. In user-space is the logic to load the language map and other bits into the kernel.Originally posted by Michael View Post
It needs to interact with the audio codecs and EC, so those bits need to be in the kernel. In user-space is the logic to load the language map and other bits into the kernel.
- Likes 1
Comment
-
Originally posted by sandy8925 View Post
RK3399 has Mali GPU, and the only open source driver is the Lima driver which is also reverse engineered like all of the other GPUs shipped on ARM devices. How is that any better than the PowerVR GPU?
As for why you should avoid PowerVR, look at this:
So someone leaked 2011 era PowerVR SGX microcode and user space... And now everyone is pissing themselves like a bunch of overexcited puppies... I've been fed links from several sides now, and i cannot believe how short-sighted and irresponsible people are, including a few people who should know…
tl;dr PowerVR doesn't have a reverse engineered driver, and very likely never will, and the coupling between components for the proprietary drivers (i.e. you can't mix and match versions) is even worse than everything else.
- Likes 1
Comment
-
Originally posted by DoMiNeLa10 View Post
EC doesn't have to handle the keyboard, and there could be 2 distinct connections, one for things that are already done in kernelspace, other for things that never should be.
The whole point of Google making their own EC was so they could do as much as possible on one chip rather than having multiple microcontrollers for different things.
It's not like there is even that much code relating to Chromebooks in the kernel.
From a grep for files with 'cros' or 'chrome' in the name (the ignored files are documentation and device tree files):
Code:72 text files. 72 unique files. 20 files ignored. github.com/AlDanial/cloc v 1.82 T=0.36 s (143.8 files/s, 61485.0 lines/s) ------------------------------------------------------------------------------- Language files blank comment code ------------------------------------------------------------------------------- C 41 2440 2075 11230 C/C++ Header 7 967 2660 2819 make 4 5 8 32 ------------------------------------------------------------------------------- SUM: 52 3412 4743 14081 -------------------------------------------------------------------------------
- Likes 1
Comment
-
Originally posted by archsway View Post
And how could that be done without increasing the hardware cost?
The whole point of Google making their own EC was so they could do as much as possible on one chip rather than having multiple microcontrollers for different things.
It's not like there is even that much code relating to Chromebooks in the kernel.
From a grep for files with 'cros' or 'chrome' in the name (the ignored files are documentation and device tree files):
Code:72 text files. 72 unique files. 20 files ignored. github.com/AlDanial/cloc v 1.82 T=0.36 s (143.8 files/s, 61485.0 lines/s) ------------------------------------------------------------------------------- Language files blank comment code ------------------------------------------------------------------------------- C 41 2440 2075 11230 C/C++ Header 7 967 2660 2819 make 4 5 8 32 ------------------------------------------------------------------------------- SUM: 52 3412 4743 14081 -------------------------------------------------------------------------------
Comment
Comment