On 05/04/10 04:04, Arjan van de Ven wrote:
On 4/4/2010 9:52, Nick Thomas wrote:
On 04/04/10 16:41, ezjd wrote:
You need make sure your PC CPU is supported (with SSE3 at least), for
example, pentium-m isn't as I saw pretty much same thing as yours but
c2d or above is OK and Atom of course.
VirtaulBox way worked in my AMD Athlon64X2 PC w/ this one
http://cross-lfs.org/~cosmo/meego/meego-iso.vdi
<http://cross-lfs.org/%7Ecosmo/meego/meego-iso.vdi> but I didn't try
qemu.
JD Zheng
So far, it's seemed to be a fairly weird collection of architectures.
I kind of expected N900-specific and LPIA builds, potentially + a
generic-as-possible ARM, a highish-power x86, and an amd64 image.
Can anyone comment on the list of architectures meego is planned to
support? Obviously, "ARM and x86" is the general idea, but there's
plenty of potential subdivision within that.
Old ARM, new ARM, lpia, old x86, new x86, amd64 would be my preferred
list ;) - for a weedy netbook or phone, CPU optimisations could make a
noticeable difference to performance.
Presumably, OBS makes building for additional architectures not too big
of a deal - although I realize it increases kernel and testing somewhat.
the big deal is in the amount of build capacity needed and the
maintenance and work
it is to keep track of all this.
on the x86 side, I kinda disagree with your choices.
Every linux distribution to date picks one "start point" in the x86
evolution,
and supports everything after that. Right now, MeeGo uses "Core2Duo"
as that starting point
(which is now 4 years old or so), which includes Atom as well.....
That captures a very large amount of machines out there, while still
working optimally on Atom...
(the SSSE3 choice comes from using SSE not x87 for floating point
math, which helps atom a *ton*, but is
also very good for core2 and later... frankly, x87 is nasty for the
compiler which means the generated
code isn't always so nice)
Obviously, extra architectures aren't free - and you're probably right
when it comes to the x86 side of things. For phones, 'lowest common
denominator' is unlikely to help much, I fear.
I must admit, I'll be really disappointed if amd64/x86_64 isn't
supported - even Slackware has one of those now ;), and my 'connected
tv' is currently amd64. Of course, not supporting amd64 means several
whole classes of bugs will never be exposed - so it does lower the
maintenance burden.
If the ability is there for the community to initiate and build ports of
everything to other architectures, that'd potentially be a decent middle
ground - if a port was successful and gained users, /and/ worked
measurably better on a particular class of hardware, perhaps a
road-to-officialdom could be arranged?
Additional: kind of related to this, and kind of to your other email to
Jean - one space I've not seen MeeGo make any overtures to yet (and
possibly rightly, I don't know) is the router space. At least in the UK,
there's a (slow but steady) drive to oust ADSL and give everyone a fibre
termination to their home. Kind-of coupled to that is a tendency for
home routers to gain more and more in the way of functionality - Home
Hub, Be Box, what have you. VoIP and online-TV is starting to get
built-in and bundled with the BB. Generally MIPS boxes, they act as
gateway devices and tend to be stuffed-up linux builds with no future.
Does MeeGo have a (distant, perhaps dimly-realised) future integrating
that kind of device, or is it something there's no interest in?
Obviously, neither nokia or intel care a jot about MIPS - so I'm not
necessarily suggesting that there should be a mips port - but I do hate
the necessity of having several different boxes to do similar functions.
Right now, my 'router' is actually a
router-fileserver-soon-to-be-the-connected-tv-and-phone-too ('just' need
to add TV tuner support and wire the phone into it). Of course, it's
Debian at the moment...
/Nick
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
