I have to say I was misled by title WayLand: A new X server for Linux of a
Phoronix's article. I see Kristian's response now, it's a display server not a
X server.
From: ezjd [mailto:entropy@gmail.com]
Sent: Tuesday, April 06, 2010 11:54 AM
To: Hohndel, Dirk
Cc: Zhang, Xing Z;
Hi, Arjan,
Everybody could got the correct information from the meego's released
rpms.
rpm -qa | while read rpm; do rpm -q --changelog $rpm | grep redhat.com
/dev/null echo $rpm; done
or
rpm -qa | while read rpm; do rpm -q --changelog $rpm | grep redhat.com
/dev/null || echo $rpm; done
I
By your point, what is “correct information” exactly?
The below script and the number are really NOTHING.
Those ‘redhat.com’ are saying ‘MeeGo is derived from fedora’? You can also get
some ‘suse.de’ or likewise in some other pkgs. Like had said, we borrowed some
working from other good distro
Thanks Austin,
rpm -qa | while read rpm; do rpm -q --changelog $rpm | grep suse.de
/dev/null echo $rpm; done
I got 157:112:19 (fedora:intel:suse)
I do NOT think fedora's gcc and yum is good enough also, but provide
both yum and zypper is not a good choice.
在 2010-04-06二的 14:45 +0800，Zhang,
On 6 April 2010 10:33, Graham Cobb g+me...@cobb.uk.net wrote:
I am next going to try to see if I can find a bootable MeeGo image I can stick
on a memory card and boot my laptop with so I can try that on a 12 hour
flight I have coming up!
Graham
If you do find one, please let the rest of us
Reposting this message to the dev list (instead of community)
Original Message
Hi
I have just been having a play with the handy /mic-image-creator/ tool
(on openSUSE 11.2). Since I have been hoping to get Meego running under
VirtualBox I was very pleased to see it had an
I must admit, I'll be really disappointed if amd64/x86_64 isn't
supported
Well, at some stage AMD included SSE3 support: just
$ cat /proc/cpuinfo | grep flags.*pni
SSE3 is called Prescott New Instructions (pni) in the kernel flags, you
can read the list of CPUs supporting that in
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
On Tue, Apr 06, 2010 at 04:44:29PM +0200, Belisko Marek wrote:
Hi,
I build my own image for meego and try to run it in qemu.
Always get following error:
./qemu-system-arm -M n900 -mtdblock
/home/open-nandra/Download/image_meego/meego-1.0-arm-n900-201004061454.img
-serial stdio -clock
On Tue, Apr 06, 2010 at 08:28:48AM -0700, ezjd wrote:
I am wondering why we stay with glibc for MeeGo.
Because it works and is supported.
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
On 04/06/10 11:06, ezjd wrote:
Because it works and is supported.
OK. It is good reason to me.
Are you sure that eglibc is really needed for arm? Look at the released
glibc package to see if something you require is missing for arm and if
so, please file a bug.
I agree that glibc works for
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
meego-dev-boun...@meego.com wrote:
On Tue, Apr 06, 2010 at 08:28:48AM -0700, ezjd wrote:
I am wondering why we stay with glibc for MeeGo.
Because it works and is supported.
Debian/Ubuntu has moved to eglibc and even WindRiver Linux (now part of
Intel) uses eglibc too. The major reason is
Arjan van de Ven a écrit :
My current thinking is to try a x86-64 kernel, with 32 bit userspace,
for the release after the upcoming one.
We know there is a clear advantage in that (for the graphics driver
to be specific), and it has very limited
impact on everything else in the system.
As
On Tue, Apr 6, 2010 at 5:28 PM, Toni Nikkanen t...@tuug.fi wrote:
On Tue, Apr 06, 2010 at 04:44:29PM +0200, Belisko Marek wrote:
Hi,
I build my own image for meego and try to run it in qemu.
Always get following error:
./qemu-system-arm -M n900 -mtdblock
On Tue, Apr 06, 2010 at 10:23:06PM +0200, Belisko Marek wrote:
Chcek the size of your image: Is it exactly 276824064 bytes long?
I build image for meego by myself. Image has 4G. Just follow
instructions from wiki.
Do you use original image from Nokia? I try to download by don't have
IMEI nr
H. Peter Anvin a écrit :
On 04/06/2010 12:38 PM, Jean-Christian de Rivaz wrote:
If you did it correctly you can easily boot it up with qemu eg.:
$ qemu -m 512 -hda meego-preview-netbook-core-20100330-001.usbimg
Thanks Markus,
Unfortunately when I use this command:
qemu -m 512 -hda
I am trying to work out how to have a working MeeGo development environment on
my Debian Squeeze desktop. I have found a few problems, reported a few bugs
and documented some issues and workrounds (see
http://wiki.meego.com/MIC_on_Debian). But I am a bit stumped by the latest
problem...
I
Hi, JD,
See link [1], page 5:
* CPUID Fn_0001_ECX[SSE41]: Added.
* CPUID Fn_0001_ECX[SSSE3]: Added.
And in your below output, as someone had mentioned, pni is sse3.[2]
[1] http://xtreview.com/images/25481.pdf
[2] http://en.wikipedia.org/wiki/SSE3
From: ezjd
hi all, my name's hendra from indonesia..i'm using moblin2.1 now, i want to
ask how to burn meego usbimg into usb stick, i've download the file
meego-preview-netbook-core-20100330-001_2.usbimg from the website..but i
can't burn it to usb..can anyone help me please, thank you..
best regards
sudo mic write meego-preview-netbook-core-20100330-001_2.usbimg
or
dd if= meego-preview-netbook-core-20100330-001_2.usbimg of=/dev/sdx
/dev/sdx is your USB disk device name
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On
Behalf Of hendra cakep
Sent: Wednesday, April
And in your below output, as someone had mentioned, pni is sse3.[2]
Yes, it makes sense. Thanks!
• CPUID Fn_0001_ECX[SSE41]: Added.
• CPUID Fn_0001_ECX[SSSE3]: Added.
My understanding is that having bits defined in CPUID and building a CPU
with that feature is different story, maybe
On Wed, Apr 7, 2010 at 1:50 PM, Justin Kwon ohkyoung.k...@samsung.com wrote:
Is it right?
Yes.
From the wiki:
Disclaimer: Please keep in mind that this is an early developer
version of the MeeGo code, and after installation, you will have a
terminal window, but no GUI. Only people actively
On 2010/4/7 11:50, Justin Kwon wrote:
Hi all,
Is it right?
Some X11 applications already exist in N900's yum repositories。e.g. pidgin
You could download rpms at
here:http://repo.meego.com/MeeGo/devel/trunk/repo/arm/os
smime.p7s
Description: S/MIME Cryptographic Signature
24 matches
Mail list logo
