Announcement

Collapse
No announcement yet.

Google Does Coreboot For "Stout" Chromebook

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Google Does Coreboot For "Stout" Chromebook

    Phoronix: Google Does Coreboot For "Stout" Chromebook

    Google has published Coreboot support for the Stout Chromebook...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Seriously what's with all these crippled Celeron Chromebooks that either have crappy battery life or cost twice as much as they should for their performance level? Just put a quad core Cortex A15 in there, a decent IPS screen, make it $250 and call it a day. It's not that hard, is it?!

    So far the best selling Chromebook by far has been Samsung's ARM based one. It's been the #1 best selling notebook on Amazon [1] for half a year now, and has never lost its rank so far, and for good reason. You'd think all these other companies like Lenovo, HP and Acer who keep releasing these crappy Celeron Chromebooks would want to emulate that. But obviously they do not. Oh well, their loss if they keep wanting to remain Intel's b*tches, and put them first instead of the customer.

    [1] - http://www.amazon.com/gp/bestsellers...08/ref=sr_bs_1
    Last edited by Krysto; 18 March 2013, 05:31 PM.

    Comment


    • #3
      They need to make their OS platform agnostic, maybe pnacl could become more than a nice experiment someday. HTML5 is OK, but no enough.

      Linux itself need a platform independent binary standard (some kind of evolved ELF) too.

      Comment


      • #4
        Screen resolution

        Worse screen resolution than a phone!

        Comment


        • #5
          Originally posted by timofonic View Post
          Linux itself need a platform independent binary standard (some kind of evolved ELF) too.
          There was this guy who tried to develop something called "fatElf" which was basically like a container format where there was x86 and x64 binaries in the same file. You might want to look into what happened with that. (spoiler alert: it's not that good an idea really.)

          Comment


          • #6
            Originally posted by dee. View Post
            There was this guy who tried to develop something called "fatElf" which was basically like a container format where there was x86 and x64 binaries in the same file. You might want to look into what happened with that. (spoiler alert: it's not that good an idea really.)
            No, I mean about a very efficient JIT-like binary format in the style of pNaCl but for Linux.

            Comment


            • #7
              Originally posted by timofonic View Post
              No, I mean about a very efficient JIT-like binary format in the style of pNaCl but for Linux.
              Oh you mean like :
              • LLVM Bytecode
              • JVM Bytecode
              • Mono's CIL implementation


              I don't think we need YetAnotherBytecode

              Comment


              • #8
                Forgot PyPy and Lua... although I'm not sure if Lua uses bytecode at all...

                Comment


                • #9
                  Originally posted by uid313 View Post
                  Worse screen resolution than a phone!
                  Screen resolution is OVERBLOWN idea... To easy to sell crap notion to potential customers.

                  Its:

                  quality of your eyes VS pixel density * average distance from your eyes

                  So if you have bad eyesight than even current (non-"retina") pixel density may be good for you.

                  And you NEED LESS pixel density farther the device you use.

                  You use phones very up close. They need most pixel density.
                  You use tablets from some distance. They need a bit less pixel density.
                  You use ibm pc's from far away. They need LEAST pixel density.


                  And getting more on the right side of VS than on the left, DO NO GOOD. Just waste processing power (of GPU, CPU, memory, bus bandwith, etc.), and battery time that is used..

                  Comment


                  • #10
                    Originally posted by przemoli View Post
                    Screen resolution is OVERBLOWN idea... To easy to sell crap notion to potential customers.

                    Its:

                    quality of your eyes VS pixel density * average distance from your eyes

                    So if you have bad eyesight than even current (non-"retina") pixel density may be good for you.

                    And you NEED LESS pixel density farther the device you use.

                    You use phones very up close. They need most pixel density.
                    You use tablets from some distance. They need a bit less pixel density.
                    You use ibm pc's from far away. They need LEAST pixel density.


                    And getting more on the right side of VS than on the left, DO NO GOOD. Just waste processing power (of GPU, CPU, memory, bus bandwith, etc.), and battery time that is used..
                    Of course that's true, but the resolution is LOWER for a BIGGER screen. That means the pixel density is A LOT lower. Nobody asks for a laptop with the same pixel density as a phone (that would be what, a 4K screen?).
                    If you are holding your laptop, tablet and phone screen each at such a distance that they take about the same space of you view they should all have the same resolution for the same quality.

                    Comment

                    Working...
                    X