Slashdot Mirror

← Back to Stories (view on slashdot.org)

Embedded Linux 1-Second Cold Boot To QT

Posted by timothy on from the why-does-my-phone-need-2-minutes? dept.

An anonymous reader writes "The blog post shows an embedded device cold booting Linux to a QT application all in just one second. This post also includes a link which describes what modifications were made to achieve this."

4 of 141 comments (clear)

  1. Re:Ermm.. by buchner.johannes · · Score: 5, Informative

    The have a slideshow here: http://www.slideshare.net/andrewmurraympc/elce-the , it's interesting starting at slide 19. Especially the executable reordering to defer loading of UI event handling code is impressive.

    --
    NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
  2. Re:Ain't that qute? by countSudoku() · · Score: 5, Informative

    I had the same reaction. The answer lies in the wikipedia, not in the unhelpful intermediate posts:

    http://en.wikipedia.org/wiki/Qt_(framework)

    Qt "is a cross-platform application framework that is widely used for developing application software with graphical user interface (GUI) (in which case Qt is referred to as a widget toolkit when used as such), and also used for developing non-GUI programs such as command-line tools and consoles for servers"

    --
    This is the NSA, we're gonna geet U h@x0r5! Also, what is a h@x0r5?
  3. Re:Function re-ordering inside the image? wow by Chrutil · · Score: 5, Informative

    That's actually common practice in profile guided optimization, put commonly used code close together in the image to minimize the number of pages loaded.

  4. Re:Function re-ordering inside the image? wow by noidentity · · Score: 5, Informative
    Really? I thought this was standard stuff for profile-guided-optimization. It's common knowledge that when a system initializes, it jumps all over the image, which is bad if it's paged. Seems a big "duh" to reorder functions so that all the init code is together.

    Another optimization that was common old Mac compilers was "dead-stripping", where they avoided linking in any functions that were never called. Apparently this isn't commonly done and instead if a single function in a file is called, then ALL are linked in, at least when I looked into it for Linux a while back.