Announcement

Collapse
No announcement yet.

Meego in-vehicle images

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

  • Meego in-vehicle images

    Looks like they released the in-vehicle image for Atom processors this morning.

    The downloadable images available at http://meego.com/downloads now include an image for the Intel Atom-based in-vehicle platforms.
    This image is based on MeeGo 1.0 core and includes IVI specific packages for the Intel platforms, including the Moblin 2.1 IVI packages that formed the basis of the GenIVI 1.0 Reference implementation. A MeeGo User Experience for the in-vehicle usage model is not included in this MeeGo in-vehicle image. This image will boot to XFCE utilizing the Linux VESA graphics driver and has been tested on Intel eMenlow (US15W) and Tunnel Creek platforms. A Beta release of the Intel EMGD 3D graphics driver for MeeGo on these platforms is expected in June 2010.
    website

  • #2
    w00t! Hopefully the UX for ivi will be released soon.
    Former author of LinuxICE, nghost, nobdy.
    Current author of Automotive Message Broker (AMB).
    Works on Tizen IVI. Does not represent anyone or anything but himself.

    Comment


    • #3
      Hey Kev does this effect your work?

      Comment


      • #4
        A bit disappointed, mic2 built and installed an image to my thumb-drive but it won't boot.
        website

        Comment


        • #5
          A little isolinux trickery got me into the GUI. Unfortunately, I have no mouse/keyboard control and it hangs at the "Tips and Tricks" screen...
          After a 2 year break, I'm back! There are so many new and familiar faces here!
          New vehicle, new ideas!

          Chryssi - The Changeling CarPC Project

          Comment


          • #6
            There still aren't screenshots anywhere :-(

            I realise that part of meego is "it's a toolkit, you can make it look like anything you want", but the same is true of qt, wx, fltk, and others - and those all have screenshots [linked].

            I have to say, I still don't "get" meego; what does it offer that I can't do with debian, knoppix, or arch [just for want of some examples]?

            Gary (-;
            OBDGPSLogger, for logging OBDII and/or GPS data
            OBDSim, an OBDII/ELM327 software simulator
            mp3car forums: obdgpslogger, obdsim

            Comment


            • #7
              Originally posted by SapporoGuy View Post
              Hey Kev does this effect your work?
              No effect. IMHO, LinuxICE2 is still a more complete solution for now. However, when MeeGo IVI (and handsets for that matter) does progress, it only helps our cause and will hopefully fill some of our current gaps (navigation, bluetooth, telephony/handsfree to name a few). Because MeeGo uses standard Linux components and is completely open (unlike that bastard-child android), we get to use anything from it we want any way we want.

              There still aren't screenshots anywhere :-(

              I realise that part of meego is "it's a toolkit, you can make it look like anything you want", but the same is true of qt, wx, fltk, and others - and those all have screenshots [linked].

              I have to say, I still don't "get" meego; what does it offer that I can't do with debian, knoppix, or arch [just for want of some examples]?

              Gary (-;
              We had a conversation in IRC about this, but I'll echo it here. MeeGo is a reference OS for various devices such as IVI systems, netbooks, handsets and a few other devices. It consists of an optimized Linux distro with a specific graphical user layer on top which varies depending on the device. For handsets the graphical layer is done using a Qt-based toolkit/framework called MeeGoTouchFramework (MTF).

              What does meego offer that you can't do with debian/etc? Well, in short nothing. MeeGo has an "upstream first" approach to development. This means that any enhancements get pushed upstream first. That means that Debian and the others who pull from upstream also benefit. This contrasts greatly with Google approach in android to fork and fsck every upstream project that it can. To add, you can install MTF on any Linux distro of your choosing (I also hear that it runs native on windows/mac but I've never seen it so idk) like in the case where I have LinuxICE3 images with some MTF stuff installed based on Ubuntu. The core value of MeeGo is you get everything set up how it should be by default.

              MTF differs from Qt/Wx/GTK+ in the scope that it's really designed with touchiness in mind. GTK+ is a desktop oriented toolkit. It's made with captive attention and a mouse+keyboard in mind. MTF is designed with only your fingers in mind. So interaction is with gestures, swiping, pinching, tapping, etc. Widgets are designed to be big enough to be touchable by default. Sure, you can bend GTK+ to do that, but it's a lot of work. With MTF you get all that for free and it'll be consistent for every developer who develops with it (which can't be said about a app-specific custom GTK+ UI done up in glade).

              Hope that clears things up.

              Screenshots will come when the User interface layer is released.
              Former author of LinuxICE, nghost, nobdy.
              Current author of Automotive Message Broker (AMB).
              Works on Tizen IVI. Does not represent anyone or anything but himself.

              Comment


              • #8
                Looks like the in-vehicle release won't be until October. 1.0 for netbooks was released today however
                GMC Worklog

                Comment

                Working...
                X