Language Selection

English French German Italian Portuguese Spanish

Plans for Chromebooks

Filed under
GNU
Linux
Google
Hardware
  • AMD Zen+ Chromebooks a Step Closer, Thanks to Google Coreboot Support

    Google has recently been working on bringing Fuchsia (a new operating system the company has been developing) and Chrome OS support to multiple AMD processors. The latest to receive support in the open source Coreboot firmware were AMD’s 7th gen Stoney Ridge APUs which were used in HP’s first-ever AMD-based Chromebooks.
    In January, AMD announced the Picasso APU series, which uses a Zen+ CPU and Vega graphics. According to recent rumors, Google was already working on adding support in Chrome OS for a reference design board called Zork that used the Picasso APU. The latest news about Picasso being supported in Coreboot reinforces the idea that we’ll soon see some Chromebooks using AMD’s latest generation of mobile APUs..

  • Will somebody make me a Chromebook with a 'real' graphics card? [Ed: Will you purchase a 'real' computer rather than rent one from Google (for Google to remotely control)?]

    The inclusion of packaged Linux applications for Chrome has changed that. Now, if you're a developer who uses a Linux desktop to write, compile, and test code, a Chromebook is an excellent choice. You'll appreciate a model with a new-ish Intel CPU and 8 or even 16 GB of RAM when it comes to doing all that, and when you're not being productive, you have the same entertainment options through the web and Google Play that every Chromebook has. It's a pretty sweet setup. But there's still one piece of the puzzle missing that would make a Chromebook even better: a high-end GPU.

More in Tux Machines

today's howtos

KDE Frameworks 5.61, Applications 19.08 in FreeBSD

Recent releases were KDE Frameworks 5.61 and KDE Applications 19.08. These have both landed in the official FreeBSD ports tree, after Tobias did most of the work and I pushed the big red button. Your FreeBSD machine will need to be following current ports – not the quarterly release branches, since we don’t backport to those. All the modern bits have arrived, maintaining the KDE-FreeBSD team’s commitment to up-to-date software for the FreeBSD desktop. The one thing we’re currently lagging on is Qt 5.13. There’s a FreeBSD problem report tracking that update. Read more

Dev branch moving towards Qt 6

As you know, Qt 5.14 will be branched pretty soon. After that I would expect that most new development work would start to be aimed towards Qt 6. As it looks right now, 5.15 will be a smaller release where we polish what we have in 5.14, and prepare some things for Qt 6. To reflect that and help us all understand that the development focus is now towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6 back into dev). We can then either create a 5.15 branch at the same time, or slightly later, once 5.14 has stabilised a bit more (e.g. after the beta or RC). Read more Also: Qt's Development Branch To Begin Forming Qt 6

Today in Techrights