On 10/13/10 11:29, Attila Csipa wrote:
On Wed, Oct 13, 2010 at 8:15 PM, Auke
Kok<[email protected]<mailto:[email protected]>> wrote:
I also don't think there's an official stance on the amount of memory required to ""run
MeeGo"". In general, with 512mb most devices see a lot better performance than with
128mb, so you can draw your conclusions on whether it's 'good enough' for everyone or just 'good
enough' for *you*.
It has been previously stated[0] that the MeeGo compliance specs will contain
exactly that - strictly defined minimum hardware req for particular profiles in
order to call them compliant ('real', if you wish). Even the OP formulated the
question like that by saying 'minimum RAM required'. With enough hackery, you
certainly could get MeeGo (and Linux in general) to run on very modest hardware
or benefit from extra memory, but the question is what the official number for
a particular device profile is (it's a different story that we don't have those
numbers officially yet, just saying that 'how high/low can you hack/endure it'
was not really how I understood the question).
[0] http://lists.meego.com/pipermail/meego-dev/2010-September/005963.html
I fail to see what the motivation of your post is...
Would you like me to program MeeGo so that it tests the memory size and
stops the boot process if the memory size doesn't adhere to the
compliance spec?
The original question came from a person with a very specific device
asking whether MeeGo would run on this. I doubt he's interested in being
MeeGo compliance, but perhaps he can clarify?
Auke
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
