Thanks for sharing these important KDE information!
As a long time KDE user (not developer though :( ), I have been hoping we
can see places of KDE on embedded device and I even talked with KDE guys
about it when KDE 4.0 was just released. Although KDE team was busy shaping
up KDE 4.X at that time
> I don't doubt that there's a market for it, but the question at hand is
> whether it's market we want to address. As Arjan said in his reply, it's
> not.
>
I am not the marketing guy for MeeGo, nor in my own work so that I have
little idea about marketing. My view of, at least, IV device or TV,
>
> It's turning into the fundaments of the UI. There are many reasons for
> that,
> including the fact that animations are becoming intrinsic parts of the UI.
> Also, supporting "eye candy mode" and "non-eye candy mode" means more code,
> meaning more tests. It's easier to test less code (think of
Thanks!
That is interesting since image isn't supposed to run on my AMD PC because
of these flags OR I haven't run into the code which can be optimized by
these?
BTW, I'd suggest we put such information in some documents in case people
didn't follow these emails.
JD Zheng
On Tue, Apr 6, 2010 at
, pni is sse3.[2]
>
>
>
> [1] http://xtreview.com/images/25481.pdf
>
> [2] http://en.wikipedia.org/wiki/SSE3
>
>
>
> *From:* ezjd [mailto:entropy@gmail.com]
> *Sent:* Wednesday, April 07, 2010 3:36 AM
> *To:* Zhang, Austin
> *Cc:* Skyles, Greg S; meego-
CosmoHill should get the credit :-)
On Tue, Apr 6, 2010 at 12:59 PM, ezjd wrote:
> CosmoHil should get th
>
>
> On Tue, Apr 6, 2010 at 12:42 PM, Jean-Christian de Rivaz wrote:
>
>> ezjd a écrit :
>>
>> You need make sure your PC CPU is supported (with SSE3 at l
CosmoHil should get th
On Tue, Apr 6, 2010 at 12:42 PM, Jean-Christian de Rivaz wrote:
> ezjd a écrit :
>
> 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
>> abov
meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] *On
> Behalf Of *ezjd
> *Sent:* Tuesday, April 06, 2010 11:22 PM
> *To:* Skyles, Greg S
> *Cc:* meego-dev@meego.com
> *Subject:* Re: [MeeGo-dev] CPU Architectures (was Re: Build for a standard
> PC)
>
>
>
>
> One of the biggest reason not to go down the path of eglibc and/or others,
is that we can build the exact same software stack for all the hardware
(netbooks, nettops, even laptops and desktop PCs) quicker and easier on
glibc. This creates a development atmosphere where everything just works, we
o
ibc is doing better ...(for
examplehttp://blog.aurel32.net/?p=47). Anyway, question answered already :-)
On Tue, Apr 6, 2010 at 9:17 AM, Greg KH wrote:
> On Tue, Apr 06, 2010 at 08:28:48AM -0700, ezjd wrote:
> > I am wondering why we stay with glibc for MeeGo.
>
> Becaus
I am wondering why we stay with glibc for MeeGo.
Debian/Ubuntu has moved to eglibc and even WindRiver Linux (now part of
Intel) uses eglibc too. The major reason is that eglibc makes life easier
for architecture other than x86 like ARM.
On Mon, Apr 5, 2010 at 10:58 PM, An Yang wrote:
> Hi, Arj
> Note that it's S^3E3 you are looking for, not S^2E3. Perhaps not the most
brilliant naming scheme Intel has come up with...
I am not a CPU expert but I think it is SSE3 made the difference in my case:
image worked in Athlon64X2 while it didn't in Pentium-M.
According to http://en.wikipedia.org
Wayland won't necessarily replace X11, instead most likely xserver will be
running on top of it for backward compatibility. But it is still in very
early stage and things can be changed.
JD Zheng
On Mon, Apr 5, 2010 at 7:52 PM, Dirk Hohndel wrote:
> On Mon, 5 Apr 2010 20:16:09 -0600, "Zhang, Xi
port/test multiple binary
repository because we have a community behind MeeGo :-)
Thanks.
JD Zheng
On Sun, Apr 4, 2010 at 9:52 AM, 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
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 but I didn't
Sorry for many of you may already see this already.
I just realized that the simple reply was sent to meego-community only,
while I think it is a more proper topic for meego-dev.
Thanks.
JD Zheng
-- Forwarded message --
From: ezjd
Date: Thu, Apr 1, 2010 at 11:46 AM
Subject
It is almost impossible to find good time in Europe, America and Asia.
So rotation of meeting time is always fair to everyone. (every a couple of
months?)
JD
On Thu, Mar 18, 2010 at 4:51 AM, Randall Arnold wrote:
>
> - Original message -
> > On 18/03/10 12:46 +0100, Kojo Tero (Nokia-D/
* What are you waiting for to happen in the MeeGo project?
--Day one. Between day zero and day one, there are very few technical
information available and basically I just guess and try to conclude from
guessing. As an open source project, it should be technology oriented,
shouldn't it?
* Do you k
Qt Jambi (Qt java binding) is basically stopped by Nokia. And Qt guys are
heading to QML.
Although Android Java UI part is "thin", I am not sure if it is worth the
effort to port it to use Qt. Another important thing is Android just employs
JAVA programming language NOT java runtime, i.e., it has
19 matches
Mail list logo
