Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Communications Handhelds Software Hardware Linux

Mobile Linux Challenges Windows Mobile 23

An anonymous reader writes "Taking a page from Microsoft's playbook, MontaVista today announced an embedded Linux platform aimed specifically at mobile phones. 'Mobilinux' is based on a 2.6 kernel with real-time and power-management enhancements, and targets 'feature-phones' as well as the higher-end devices targeted by Microsoft with its Windows Mobile for Smartphones offering."
This discussion has been archived. No new comments can be posted.

Mobile Linux Challenges Windows Mobile

Comments Filter:
  • by Dark Coder ( 66759 ) on Monday April 25, 2005 @03:51PM (#12340580)
    I would be wary of going into 2.6 over 2.4 kernel for low-power application such as a cell phone.

    Check out the Linux v2.4 vs. Linux v2.6 [www.denx.de]
  • by mr. mulder ( 204001 ) on Monday April 25, 2005 @03:54PM (#12340613)
    The primary users of mobile phones with Windows Mobile are business users - and business users use the phones becaus ehtey nicely integrate into their Windows environment (Exchange, Blackberry, Word, Excel, contacts, emails, etc.)

    If they can develop a Linux mobile device that syncs with Exchange or Blackberry (wirelessly like ActiveSync), it would be money.

    • Infineon, Trolltech and Samsung introduced a reference design [geekzone.co.nz] back in February.

      Motorola not only is already selling Linux-based Smartphones [geekzone.co.nz] since September 2004, but in addition to that they also licence Microsoft Exchange ActiveSync [geekzone.co.nz] to synchronise with Exchange Servers.
      • Thinking this through further, what business users need is an inexpensive open-source solution architecture that provides a HTTP-based syncronization mechinism for transferring mail between handhelds and corporate servers.

        Blackberry has done the ultimate-super-expensive version of this where it is completely closed-source. They've even brought it to the level of selling their own hardware.

        A successful open-sourced project surrounding this topic would do the following:

        1. define an xml/soap based protocol
        • Hmmm. There's an open standard: SyncML. There are SyncML clients for different mobile platforms and desktop/laptop OS. It's implemented and distributed on Symbian OS, it is part of Bluetooth OBEX, it's available as a tool for Windows Mobile.
        • I use IMAP with my phone, works beautifully. I have configured the phone's client to first get the headers and only get the body if I ask it too.

          Can't really imagine it being simpler.

  • Notice how their "other" square is outside of the big grey square? Now that's innovative.

    Linux has the same arrangement of squares as Symbian, with a blue background. That's just a different skin. Symbian could do that too.

  • MontaVista seems to be using X11 for their user interface. That's a big step forward. Does anybody know more details about their UI? I couldn't find a lot on their web site.

    (I have several Qt/Embedded and Qtopia-based devices, and those truly suck: Qt/Embedded and Qtopia are slow, consume gobs of memory, waste screen real estate on useless UI elements, and restrict you to exactly one toolkit to program in. They feel like a bad clone of PocketPC.)
    • Pfft. You don't need X11.

      directfb+SDL+cairo(glitz)+SVG == pure portable GUI mannah.

      I'm lovin' it, personally ...
      • The advantage of X11 is that there is lots of software that uses it: toolkits, applications, etc.

        If you roll your own with SVG, there is nothing. SVG-based GUIs will probably a major role at some point, but by running them on top of X11, you give users a smooth transition.

        • yeah, in theory. in practice, it'll be shit to run any X11 app on your phone, where it wasn't designed for in the first place.

          and since this article is a developer-focus one (you won't get consumers all excited about this), whats the point? write code for your new GUI environment, yo!

          • yeah, in theory. in practice, it'll be shit to run any X11 app on your phone, where it wasn't designed for in the first place.

            That's bullshit. The fact that the XFree86 implementation, which is perhaps all you have ever seen, is obese and adapted to workstation usage doesn't mean X11 is. Furthermore, there are plenty of X11 applications for those kinds of environments.

            X11 was designed for hardware that was much less powerful than today's phones. I used to run X11 and a full SVR3 UNIX system for softwar
            • The fact that the XFree86 implementation, which is perhaps all you have ever seen ..

              errmm.. no. i'm running X.org on all my boxen.


              X11 was designed for hardware that was much less powerful than today's phones. I used to run X11 and a full SVR3 UNIX system for software development on a 20MHz 386 with 4Mbytes of RAM, and that was a powerful machine at the time. Some X11 implementations are among the most light-weight window systems around.


              Yes, I remember running X11 just fine on my MIPS Magnum pizzabox
              • errmm.. no. i'm running X.org on all my boxen.

                X.org is derived from XFree86. It's nice, but it's not designed for being lean.

                I don't disagree that X11 can run, just that its pointless for developers to use it if they're working on a new cell phone platform, where there are plenty of other better, smaller, lighter options ...

                People keep claiming that there are "better, smaller, lighter options". I'd like to know what they are, because I haven't found them. Qt/Embedded, WinCE, and Palm are all slower
  • ...they release windows connectivity for it.

    I know we hate to say it, but Windows and lookOut are pretty dominant. A modern phone will be limited to the fans unless it integrates with outlook (and preferably other PMSs too) *as well as* linux. And I didn't see that out of the box.

To be is to program.

Working...