[MeeGo-dev] MeeGo core utiltities, coreutils or busybox?

[ezjd]

Let's try to see the whole picture outside of the view of a smartphone or
"handheld", say, in-vehicle device, media phone and connected TV as
mentioned in meego.com.

I doubt they will be as powerful as N900 and probably not even close in near
future. For example, ARM11 can easily meet the requirement for such devices
with less RAM and flash than N900. In device company's point of view, if
they can use ARM11 to do similar thing for less cost, they won't go to
Cortex-A8 no matter Cortex-A8 is faster. This is still commonly agreed in
embedded world.

Does someone see ARM ltd. will give up ARM11 even ARM9 totally soon? I
don't. As a result, there will be company doing ARM11 chips and devices. It
isn't like Intel/AMD stopped shipping Pentium III or Athlon, it would
disappear soon.

I am not saying we should support all low-end devices but should lower the
minimal HW requirement to a reasonable level.

Some data I got before: emdebian-grip with bare X windows takes ~90MB rootfs
and ~20MB RAM (runtime). Stripping out some fonts and locale files, it might
be fit into 60MB or probably <40MB jffs2. Note that grip is basically debian
w/o documents. Qtopia 4.X took ~30MB storage (less in jffs2) so that maybe
altogether it could fit into 64MB flash. btw, Qtopia + X isn't a valid
solution though.

The data is for reference only. Let's wait for first round of public MeeGo
document and code to see what Intel/Nokia expect.

Thanks.
JD

2010/2/26 Hans Bakker <hansmbakker at gmail.com>

> You could say "The specs of Nokia's N900, or better". It is quite a
> high-end device now, but phones are getting better very quickly and at first
> Meego will be deployed on the high-end devices I think.
>
> Maybe you could lower this requirement a bit, but not too much.
>
> Kind regards,
>
> Hans Bakker
>
> 2010/2/26 ezjd <entropy.zjd at gmail.com>
>
> According to the wide range of devices MeeGo tries to support, such limited
>> target might be needed. However, for different category, it can have higher
>> HW requirement and more functionalites as well.
>>
>> Thanks.
>> JD
>> 2010/2/26 Marcin Juszkiewicz <marcin at juszkiewicz.com.pl>
>>
>>> Dnia czwartek, 25 lutego 2010 o 20:33:38 ezjd napisał(a):
>>>
>>> > The minimal HW requirement like 64MiB flash, 64 MiB RAM with 300MHz CPU
>>> > sounds reasonable to me. The question will be if we can fit MeeGo into
>>> > that, esp. GUI part.
>>>
>>> I doubt it. I know that Moblin team has people which worked on such
>>> systems
>>> (hi ex-OH guys) but I do not think that MeeGo should support such ones.
>>> Better
>>> concentrate on more advanced devices and leave such small ones for
>>> embedded
>>> projects.
>>>
>>> Regards,
>>> --
>>> JID:      hrw at jabber.org
>>> Website:  http://marcin.juszkiewicz.com.pl/
>>> LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
>>>
>>>
>>> _______________________________________________
>>> MeeGo-dev mailing list
>>> MeeGo-dev at meego.com
>>> http://lists.meego.com/listinfo/meego-dev
>>>
>>
>>
>> _______________________________________________
>> MeeGo-dev mailing list
>> MeeGo-dev at meego.com
>> http://lists.meego.com/listinfo/meego-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meego.com/pipermail/meego-dev/attachments/20100226/908a4203/attachment.html>