hey it's sorta, based on, kinda of, open source, and you can root it and hack it so it's better than nothing... right?
I am asking people at FSF and even I made a petition at Change .org for PUBLIC DRIVERS for Linux OS based OSs.
I think that GPL must ask to any device with Linux preinstalled to be able to have dual boot or change your OS, and for that you need PUBLIC DRIVERS, even if they are blobs, obviously better if they are open source.
The use of the Linux kernel that Android and Chrome OS devices and the ARM SoCs SECRET DRIVERS, is against FREEDOM, and if not the FSF, or the GPL i think govs must do something.
At the end no more than 5% of users change or install their OSs, the most techie ones, Why this policy? Why cannot Samsung offer a dual boot ARM Chrome OS + Ubuntu Sabayon or Manjaro preinstalled? Why cannot do it myself without hacking, in a normal way as x86-64 processors.
Why Chrome OS cannot install GNU packages? when even MS WOS or OSX have their LO or GIMP versions and a lot of GNU multiplattform programs
As much as I'd love to see everything be open, it might not happen any time soon. But there is a commercial incentive for companies to do so.
In any case, to be pragmatic: I think chromebooks should run on top of android, and Ubuntu can (or soon will be able to) run as an Android app. This would make things SOOOO much nicer and integrated. The chromebook would boot a light android, and by default, load a maximized google-chrome "app". But you could switch to a maximixed Ubuntu app, or whatever.
Using FBDev for it's graphics driver means you'll have a better Linux experience on a Matrox G200 equiped Xenon server from Dell.
Can someone explain what this fbdev driver is exactly? Do user space drivers like DDX and OpenGL ES use this device file to access the GPU?
And why is this less than optimal?
All of us trying to run Ubuntu on this machine are having trouble getting hardware acceleration to work with Unity. We're running the same kernel as Chrome OS, and have copied over the necessary Mali drivers, but it's still not working. Could this be the issue?
Google is working on an own Chromebook, much like the Nexus series for Android. It might have just that.
Google has introduced it (Chromebook Pixel). Its utterly pointless with that pricetag and a processor that is just fast for something that is not required. They should have released something with next generation ARM A15 but a quad core, better GPU, and way better battery life.