Re: [MeeGo-dev] Meego 1.0 SDK issues

2010-05-28 Thread Feng, Haitao 
Could you try it on your host Linux instead of virtual box? I am not sure 
virtual box has enough support on DRI2.

Thanks
-Haitao

From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of Arun Ravindran
Sent: 2010年5月28日 15:50
To: Wu, Jackie
Cc: meego-dev@meego.com
Subject: Re: [MeeGo-dev] Meego 1.0 SDK issues

Hi,

I am running from virtual box. my host has an Mobile Intel(R) 4 series chipset.

[r...@er00595p arun]# lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox 
Graphics Adapter
00:03.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 
LANCE] (rev 40)
00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service
00:05.0 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio 
Controller (rev 01)
00:06.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
00:0b.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB2 EHCI Controller
[r...@er00595p arun]#


Regards
Arun

2010/5/28 Wu, Jackie mailto:jackie...@intel.com>>
Hi:

Are you using a host machine with an Intel integrated graphics card? So far, 
it's the only graphics device to support the simulator with 3D acceleration.

Thanks
- Jackie


From: meego-dev-boun...@meego.com 
[mailto:meego-dev-boun...@meego.com] On 
Behalf Of Arun Ravindran
Sent: 2010年5月28日 14:38
To: meego-dev@meego.com
Subject: [MeeGo-dev] Meego 1.0 SDK issues

Hi All,

I am following the SDK getting started 
(http://wiki.meego.com/Getting_started_with_the_MeeGo_SDK_for_Linux ) to try 
the latest meego SDK.

While running startmeego from chroot, i can see the the xephyr starting but the 
netbook UX is not appearing.

Here is the startmeego-debug output but and am unable to decipher anything. 
Could any one help me?

--

r...@meego-netbook-sdk:/# startmeego-debug
Cannot get current online state: The name org.moblin.connman was not provided 
by any .service filesfailed to create drawable
Window manager error: Unable to initialize Clutter.

(mutter:26330): mutter-CRITICAL **: Unable to initialize Clutter.

r...@meego-netbook-sdk:/# ** (bluetooth-panel:26344): DEBUG: Unable to create 
proxy for /org/moblin/UX/Shell/Toolbar: Could not get owner of name 
'org.moblin.UX.Shell.Toolbar': no such name
** (carrick-connection-panel:26350): DEBUG: Unable to create proxy for 
/org/moblin/UX/Shell/Toolbar: Could not get owner of name 
'org.moblin.UX.Shell.Toolbar': no such name
** (carrick-connection-panel:26350): DEBUG: Error: Couldn't end get properties 
call - The name org.moblin.connman was not provided by any .service files
** (carrick-connection-panel:26350): DEBUG: Error when ending GetProperties 
call: The name org.moblin.connman was not provided by any .service files
** (carrick-connection-panel:26350): DEBUG: Error when ending GetProperties 
call: The name org.moblin.connman was not provided by any .service files

** (matchbox-panel:26391): WARNING **: Missing argument for --geometry

(bluetooth-panel:26344): GLib-GObject-WARNING **: invalid (NULL) pointer 
instance

(bluetooth-panel:26344): GLib-GObject-CRITICAL **: g_signal_connect_data: 
assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(bluetooth-panel:26344): GLib-GObject-WARNING **: invalid (NULL) pointer 
instance

(bluetooth-panel:26344): GLib-GObject-CRITICAL **: g_signal_connect_data: 
assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(bluetooth-panel:26344): GLib-GObject-WARNING **: invalid (NULL) pointer 
instance

(bluetooth-panel:26344): GLib-GObject-CRITICAL **: g_signal_connect_data: 
assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
failed to create drawable

** ERROR **: Unable to initialize Clutter.

aborting...
failed to create drawable
** (moblin-power-icon:26403): DEBUG: Unable to create proxy for 
/org/moblin/UX/Shell/Toolbar: Could not get owner of name 
'org.moblin.UX.Shell.Toolbar': no such name
Loading simple Config module ...
** (moblin-power-icon:26403): DEBUG: No outputs have backlight property
Creating backend ...
** (moblin-power-icon:26403): DEBUG: no XRANDR extension, so aborting init

(moblin-power-icon:26403): Clutter-WARNING **: Called clutter_main() but 
Clutter wasn't initialised.  You must call clutter_init() first.
W: main.c: This program is not intended to be run as root (unless --system is 
specified).
Initializing tracker-miner-fs...
Track

Re: [MeeGo-dev] Show white window when run the simulator on MeeGo-SDK

2010-06-17 Thread Feng, Haitao 
Hi Xu,

Please submit a bug at bugs.meego.com for MeeGo SDK Simulator.

Thanks
-Haitao

On Thu, Jun 17, 2010 at 04:57:37PM +0800, Xu Cheng wrote:
> My laptop could running MeeGo 1.0 image fine. But your graphic chipset maybe
> without support list.
> Now, i could started MeeGo in simulator and show wallpaper without other
> widget.
> 
> 
>2010  6  17   4:16  cc д
> 
> I just meet the same problem. and after few days , I still have not sloved
> this problem.
> And even i changed my hardware that support SSS3 instruction.
> my harderware: 
>  CPU  core D E7500
>  MEM  2G
>  MOTHERBORD   G41
>  GraphicsCard:  NV7300GT
> 
> But i just tested Meego on different operating system.
> Ubuntu9.10  without Nvdia 7300 graphics card   run OK.
> Ubuntu9.10  with Nvdia 7300 graphics car   run D-Bus Error
> Fedora 10   without Nvdia 7300 graphics card  run D-Bus Error
> Fedora 10   with Nvdia 7300 graphics card  also run D-Bus Error
> 
> when i see your discussion.  i use " su -"
> export DBUS_SESSION_BUS_ADDRESS=""
> solved the DebusError  but  it still run white window . problem like blow
> shows
> /
> 
> ***
> /
>  Cannot get current online state: The name org.moblin.connman was not
> provided by any .service filesABRT
> ** (bluetooth-panel:30090): DEBUG: Unable to create proxy for /org/moblin/
> UX/Shell/Toolbar: Could not get owner of name
> 'org.moblin.UX.Shell.Toolbar': no such name
> 
> (bluetooth-panel:30090): GLib-GObject-WARNING **: invalid (NULL) pointer
> instance
> 
> (bluetooth-panel:30090): GLib-GObject-CRITICAL **: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> 
> (bluetooth-panel:30090): GLib-GObject-WARNING **: invalid (NULL) pointer
> instance
> 
> (bluetooth-panel:30090): GLib-GObject-CRITICAL **: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> 
> (bluetooth-panel:30090): GLib-GObject-WARNING **: invalid (NULL) pointer
> instance
> 
> (bluetooth-panel:30090): GLib-GObject-CRITICAL **: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> ** (carrick-connection-panel:30097): DEBUG: Unable to create proxy for 
> /org
> /moblin/UX/Shell/Toolbar: Could not get owner of name
> 'org.moblin.UX.Shell.Toolbar': no such name
> ** (carrick-connection-panel:30097): DEBUG: Error: Couldn't end get
> properties call - The name org.moblin.connman was not provided by any
> .service files
> ** (carrick-connection-panel:30097): DEBUG: Error when ending 
> GetProperties
> call: The name org.moblin.connman was not provided by any .service files
> ** (carrick-connection-panel:30097): DEBUG: Error when ending 
> GetProperties
> call: The name org.moblin.connman was not provided by any .service files
> 
> (gpk-update-icon:30133): devkit-power-gobject-WARNING **: Couldn't
> enumerate devices: The name org.freedesktop.DeviceKit.Power was not
> provided by any .service files
> 
> (gpk-update-icon:30133): devkit-power-gobject-WARNING **: Error invoking
> GetAll() to get properties: The name org.freedesktop.DeviceKit.Power was
> not provided by any .service files
> 
> ** (matchbox-panel:30138): WARNING **: ȱ   --geometry  IJ   
> failed to create drawable
> 
> ** ERROR **: Unable to initialize Clutter.
> 
> aborting...
> failed to create drawable
> W: main.c:   Ӧ  root   б򣨳   ָ   --system
> Loading simple Config module ...
> Creating backend ...
> Initializing tracker-miner-fs...
> Tracker-Message: Checking XDG_DATA_HOME is writable and exists
> Tracker-Message:   XDG_DATA_HOME is '(null)'
> ** (moblin-power-icon:30151): DEBUG: Unable to create proxy for 
> /org/moblin
> /UX/Shell/Toolbar: Could not get owner of name
> 'org.moblin.UX.Shell.Toolbar': no such name
> 
> (moblin-power-icon:30151): devkit-power-gobject-WARNING **: Couldn't
> enumerate devices: The name org.freedesktop.DeviceKit.Power was not
> provided by any .service files
> 
> (moblin-power-icon:30151): devkit-power-gobject-WARNING **: Couldn't
> enumerate devices: The name org.freedesktop.DeviceKit.Power was not
> provided by any .service files
> 
> (gnome-settings-daemon:30128): GVFS-RemoteVolumeMonitor-WARNING **:
> invoking IsSupported() failed for remote volume monitor with dbus name
> org.gtk.Private.GduVolumeMonitor:
> org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/libexec/
> gvfs-gdu-volume-monitor received signal 6
> ** (moblin-power-icon:30151): DEBUG: No outputs have backlight property
> ** (moblin-power-icon:30151): DEBUG: no XRANDR extension, so aborting init
> 
> (moblin-pow

Re: [MeeGo-dev] The meego sdk displays black in Xephyr

2010-06-30 Thread Feng, Haitao 
Hi Maokun,

Have you run "xhost +local:" before invoking "meego-sdk-chroot"?

Xephyr should work on OpenSuSE, as well as Ubuntu if you have Intel graphics
card.

Thanks
-Haitao

On Tue, Jun 29, 2010 at 11:53:49AM +0800, 韩茂琨 wrote:
> Hi,
> 
> I got the same problem with openSUSE11.2, I have installed Ubuntu10.04 on
> another exactly same laptop, the xephyr runs fine.anyone have same issue as
> mine?
> 
> br,Maokun
> 
> --- 10年6月29日，周二, theway  写道：
> 
> 
> 发件人: theway 
> 主题: Re: [MeeGo-dev] The meego sdk displays black in Xephyr
> 收件人: "Development for the MeeGo Project" 
> 日期: 2010年6月29日,周二,上午10:21
> 
> Hi :
> I guess maybe meego only supports integrated video card with an Intel
> chipset, does it?
> 
> >Hi yanming,
> >
> >
> I have same problem and I think that it is because the system requirement 
> is not met.
> 
> >
> >Please check your system information.
> >
> >My system info.
> >
> >1. Graphics controller is maybe OK.
> >lspci:
> >00:02.0 VGA compatible controller: Intel Corporation 82Q/963/
> Q965 Integrated Graphics Controller (rev 02)
> >
> >2.CPU doesn't correspond to SSSE3.
> >cat /proc/cpuinfo
> >processor : 0
> >vendor_id : GenuineIntel
> >cpu family : 15
> >model : 4
> >model name : Intel(R) Celeron(R) CPU 3.06GHz
> >stepping : 9
> >cpu MHz : 3056.653
> >cache size : 256 KB
> > fdiv_bug : no
> >hlt_bug : no
> >f00f_bug : no
> >coma_bug : no
> >fpu : yes
> >fpu_exception : yes
> >cpuid level : 5
> >wp : yes
> >flags
> : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 
> clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up pebs 
> bts pni dtes64 monitor ds_cpl tm2 cid cx16 xtpr lahf_lm 
> <- no SSSE3 flag
> >bogomips : 6113.30
> >clflush size : 64
> >cache_alignment : 128
> >address sizes : 36 bits physical, 48 bits virtual
> >power management:
> >
> >K.imoto
> >
> >yanming zhu wrote:
> >> De ar all,
> >> 
> >> I have download the
> >> meego-sdk-0524.tar.bz2 meego-sdk-0524.tar.bz2>,
> >> and install the SDK as "Getting_started_with_the_MeeGo_SDK_for_Linux"
> >> said, after startmeego-debug 
> &, the Xephyr start with a black window, can
> >> not see any MeeGo UI.
> >> 
> >> My system is: IBM X60 with Ubuntu 9.10;
> >> 
> >>
>  Error information as below, is any one had same problem, and do you know 
> how
> 
> >> to resolve it, thanks in advance.
> >> 
> >> Cannot get current online state: The  name org.mob lin.connman was not
> >>
>  provided by any .service filesABRT service is not running The message is 
> not
> 
> >> a signal. ignoring ** 
> (bluetooth-panel:4005): DEBUG: Unable to create proxy
> >> for /org/moblin/UX/Shell/Toolbar: Could not get owner of name
> >> 'org.moblin.UX.Shell.Toolbar': no such name ** (matchbox-panel:4049):
> >> WARNING **: Missing argument for --geometry **
> >> (carrick-connection-panel:4010): DEBUG: Unable to create proxy for
> >> /org/moblin/UX/Shell/Toolbar: Could not get owner of name
> >> 'org.moblin.UX.Shell.Toolbar': no such name **
> >> (car rick-connection-panel:4
> 010): DEBUG: Error: Couldn't end get properties
> >>
>  call - The name org.moblin.connman was not provided by any .service 
> files **
> 
> >> (carrick-connection-panel:4010): DEBUG: Error when ending GetProperties
> >>
>  call: The name org.moblin.connman was not provided by any .service files 
> **
> 
> >> (carrick-connection-panel:4010): DEBUG: Error when ending GetProperties
> >> call: The name org.moblin.connman was not provided by any .service 
> files
> >> Window manager warning: Failed to load theme "Moblin-Netbook": Failed 
> to
> >> find a valid file for theme Moblin-N etbook (mutter:399
> 6): mutter-WARNING **:
> >>
>  Failed to load theme "Moblin-Netbook": Failed to find a valid file for 
> theme
> 
> >>
>  Moblin-Netbook Window manager warning: Failed to load theme "Simple": 
> Failed
> 
> >> to find a valid file for theme Simple (mutter:3996): mutter-WARNING **:
> >>
>  Failed to load theme "Simple": Failed to find a valid file for theme 
> Simple
> 
> >> Window manager warning: Failed to load theme "Default": Failed to find 
> a
> >> valid file for theme Default (mutter:3996): mutter-WARNING **: Failed 
> to
> >> load theme "Default": Failed&nb sp;to find a& nbsp;
> valid file for theme Default W:
> >> main.c: This program is not intended to be run as root 
> (unless --system is
> >> specified). ** 
> (moblin-power-icon:4061): DEBUG: Unable to create proxy for
> >> /org/moblin/UX/Shell/Toolbar: Could not get owner of name
> >> 'org.moblin.UX.Shell.Toolbar': no such name (bluetooth-panel

Re: [MeeGo-dev] The meego sdk displays black in Xephyr

2010-07-02 Thread Feng, Haitao 
Hi Maokun,

Personally I use Ubuntu 9.10 as my developing machine now, and verify our SDK 
on OpenSuse and Fedora before release.

Thanks
-Haitao

-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of 韩茂琨
Sent: 2010年7月2日 10:40
To: Development for the MeeGo Project (discussion list)
Subject: Re: [MeeGo-dev] The meego sdk displays black in Xephyr

Hi, Haitao

yes I definitely have 'xhost +local:' run before invoke 'meego-sdk-chroot',

I am wondering what you guys are developing meego with? (opensuse? fedora? 
ubuntu?) first I work with ubuntu for convenience of maemo development, then I 
saw in meego.com that suse is coming in, then I am trying opensuse, now, 
yesterday I saw the meego image built is only available for 
fedora..."http://wiki.meego.com/ARM/Creating_ARM_image_using_MeeGo_Image_Creator";.

Haitao, would you suggest me a platform for development purpose?
Thank you in advance!

Best Regards,
Maokun

--- 10年7月1日，周四, Feng, Haitao  写道：

> 发件人: Feng, Haitao 
> 主题: Re: [MeeGo-dev] The meego sdk displays black in Xephyr
> 收件人: "Development for the MeeGo Project" 
> 日期: 2010年7月1日,周四,上午8:23
> Hi Maokun,
>
> Have you run "xhost +local:" before invoking
> "meego-sdk-chroot"?
>
> Xephyr should work on OpenSuSE, as well as Ubuntu if you
> have Intel graphics
> card.
>
> Thanks
> -Haitao
>
> On Tue, Jun 29, 2010 at 11:53:49AM +0800, 韩茂琨 wrote:
> > Hi,
> >
> > I got the same problem with openSUSE11.2, I have
> installed Ubuntu10.04 on
> > another exactly same laptop, the xephyr runs
> fine.anyone have same issue as
> > mine?
> >
> > br,Maokun
> >
> > --- 10年6月29日，周二, theway 
> 写道：
> >
> >
> > 发件人: theway 
> > 主题: Re: [MeeGo-dev] The
> meego sdk displays black in Xephyr
> > 收件人: "Development for
> the MeeGo Project" 
> > 日期:
> 2010年6月29日,周二,上午10:21
> >
> > Hi :
> > I guess maybe meego only
> supports integrated video card with an Intel
> > chipset, does it?
> >
> > >Hi yanming,
> > >
> > >
> > I have same problem and I
> think that it is because the system requirement is not met.
> >
> > >
> > >Please check your system
> information.
> > >
> > >My system info.
> > >
> > >1. Graphics controller is
> maybe OK.
> > >lspci:
> > >00:02.0 VGA compatible
> controller: Intel Corporation 82Q/963/
> > Q965 Integrated Graphics
> Controller (rev 02)
> > >
> > >2.CPU doesn't correspond
> to SSSE3.
> > >cat /proc/cpuinfo
> > >processor : 0
> > >vendor_id : GenuineIntel
> > >cpu family : 15
> > >model : 4
> > >model name : Intel(R)
> Celeron(R) CPU 3.06GHz
> > >stepping : 9
> > >cpu MHz : 3056.653
> > >cache size : 256 KB
> > > fdiv_bug : no
> > >hlt_bug : no
> > >f00f_bug : no
> > >coma_bug : no
> > >fpu : yes
> > >fpu_exception : yes
> > >cpuid level : 5
> > >wp : yes
> > >flags
> > : fpu vme de pse tsc msr pae
> mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts
> acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up
> pebs bts pni dtes64 monitor ds_cpl tm2 cid cx16 xtpr lahf_lm
>
> > <- no SSSE3 flag
> > >bogomips : 6113.30
> > >clflush size : 64
> > >cache_alignment : 128
> > >address sizes : 36 bits
> physical, 48 bits virtual
> > >power management:
> > >
> > >K.imoto
> > >
> > >yanming zhu wrote:
> > >> De ar all,
> > >>
> > >> I have download the
> > >>
> meego-sdk-0524.tar.bz2<http://download3.meego.com/
> > meego-sdk-0524.tar.bz2>,
> > >> and install the SDK
> as "Getting_started_with_the_MeeGo_SDK_for_Linux"
> > >> said, after
> startmeego-debug
> > &, the Xephyr start with a
> black window, can
> > >> not see any MeeGo
> UI.
> > >>
> > >> My system is: IBM X60
> with Ubuntu 9.10;
> > >>
> > >>
> >  Error information as below, is any
> one had same problem, and do you know how
> >
> > >> to resolve it, thanks
> in advance.
> > >>
> > >> Cannot get current
> online

Re: [MeeGo-dev] meego sdk issue with Fedora 13

2010-07-21 Thread Feng, Haitao 
Could you invoke the "startmeego-debug 2>log2" and send the log2 to me?

In Fedora system, because of selinux, OpenGL applications could not run inside 
chroot environment. Here is a walkaround "sudo setenforce 0" which temporally 
turns off selinux.

BTW: meego-...@meego.com is the mailing list for SDK topics. For future 
question and comments, could you post them to the MeeGo SDK mailing list?

Thanks
-Haitao

-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of Helio Chissini de Castro
Sent: 2010年7月21日 16:00
To: meego-dev@meego.com
Subject: [MeeGo-dev] meego sdk issue with Fedora 13

Hello all

On Fedora 13 with intel graphics, the meego SDK is failing to work with 
Xephyr.
The standar Xephyr + background root opens finally, but any application, 
despite in the process list and started, are not draw in the window, no 
mutter, no nothing. Even starting an xterm on the same DISPLAY, it shows that 
is open, no error is issued, but still only the root wallpaper screen.

Anyone is experimenting similar issue ?

[]'s

-- 
Helio Chissini de Castro
South America and Brazil Primary Contact
KDE Developer since 2002
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] how can I run meego compositor?

2010-07-28 Thread Feng, Haitao 
Hi,

We have enabled Xephyr with DRI2 extension, and if you have Intel graphics card,
you could get OpenGL acceleration. Basically Xephyr runs as fast as a real
netbook device.

Besides Xephyr, we have successfully enabled OpenGL acceleration in Qemu and
VirtualBox to launch the MeeGo netbook UX. The performance is not as fast as
Xephyr while both of them could be used for real development work practically. 
We
will release those work very soon.

Thanks
-Haitao

On Tue, Jul 27, 2010 at 09:15:24AM +0800, Navjot Sandhu wrote:
> the sdk won't work with certain graphic chipsets, and also SeLinux has to be
> disabled because it prevents the libGL.so files from being shared with other
> programs.
> 
>  
> 
> it boils down to a mutter and clutter problem!!  also the graphics chipset has
> to support SSE3
> 
>  
> 
> I got the Netbook image to boot up into a virtual environment but only
> successfully into the shell.  I'm going to try to see what I can do from there
> as far as loading drivers.
> 
>  
> 
> Incidently does anyone know the command to boot up the Netbook graphical
> interface from the command shell of the netbooks linux shell  (this is not the
> sdk chroot i'm talking about, where I know you have to run startmeego-debug or
> startmeego & after you set the display.
> 
>  
> 
> (startx starts up a barebones tinyx GUI)
> 
>  
> 
>  
> 
> From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On
> Behalf Of WuYongbo
> Sent: Monday, July 26, 2010 9:00 PM
> To: Development for the MeeGo Project (discussion list)
> Subject: Re: [MeeGo-dev] how can I run meego compositor?
> 
>  
> 
> yes, I did change the DISPLAY settings.
> 
> 2010/7/26 Jani Mikkonen 
> 
> > I tried to run compositor on meego sdk for netbook, it response with
> > "Compositing manager already running".
> > But I did not find any window-manager except for metacity for my host
> > PC.
> 
> Did you point DISPLAY variable to proper Xephyr display ? Metacity
> propably runs on :0 so, setup Xephyr on :1 or something else and do
> export DISPLAY=:1 before launching mcompositor.
> 
> 
> 
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
> 
> 
> 
> 
> --
> Good luck !
> 

> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] how can I run meego compositor?

2010-07-29 Thread Feng, Haitao 
We will release the Qemu for Netbook UX and Handset UX, and Xephyr for Netbook
UX and Handset UX at the same time.

Thanks
-Haitao

On Thu, Jul 29, 2010 at 11:45:17PM +0800, Jackson, Thomas (Tom) wrote:
> > Besides Xephyr, we have successfully enabled OpenGL acceleration in
> Qemu and VirtualBox to launch the MeeGo netbook UX. The performance is
> not as fast as Xephyr while both of them could be > used for real
> development work practically. We will release those work very soon.
> 
> > Thanks
> > -Haitao
> 
> That is great!   Since you mentioned successfully enabled OpenGL
> acceleration in Qemu for netbook UX, are there short term plans to do
> the same for the handset UX?  Seems to be  a recurring issue that much
> of the work is focused on netbook.  Sorry, had to ask.  
> 
> -Tom
> 
> 
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [MeeGo-SDK]package xorg-x11-server-Xephyr-1.9.0-16.1.i586.rpm is empty!!!

2010-09-09 Thread Feng, Haitao 
Hi,

I will update Xephyr as Xorg upgrades to 1.9.0. There should not be such a rpm
downloadable at this time. When I finish updating, we will publish the rpm.

I will submit my patch to Xorg dev mailing list, if you are a developer, I
welcome you to have a code review there.

At this time, you could use the old Xephyr downloadable from
meego.com/developers.

Thanks
-Haitao

On Thu, Sep 09, 2010 at 08:32:22PM +0800, Chengwei Wu wrote:
> Dear all:
> I downloaded the package xorg-x11-server-Xephyr-1.9.0-16.1.i586.rpm from
> http://download.meego.com/live/devel:/tools:/sdk/Trunk/i586/
> But it is empty. Ridiculous! what's wrong? who can tell me   Thanks in 
> advance!
> 
> PS: In http://repo.meego.com/MeeGo/builds/trunk/1.0.90.1.20100907.1/core/
> repos/ia32/packages/i586/, there is xorg-x11-server-1.9.0-1.32.i586.rpm
> But no corresponding package xorg-x11-server-Xephyr-1.9.0-1.32.i586.rpm where
> can I get it?
> 
> Your help will be appreciated!
> 
> Best Regards!
> Chengwei Wu
> 

> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [MeeGo-SDK]package xorg-x11-server-Xephyr-1.9.0-16.1.i586.rpm is empty!!!

2010-09-10 Thread Feng, Haitao 
Hi Chengwei,

Xephyr relies on the chroot Xlibs, I am now upgrading Xephyr and making it
working with Xorg 1.9.0.

Maybe you could use an older image (with Xorg 1.8.0) and then update the
libraries you need to the latest and do not update Xlibs.

Thanks
-Haitao

On Fri, Sep 10, 2010 at 09:59:12AM +0800, Chengwei Wu wrote:
> Hi Haitao:
> the old Xephyr you mean is http://download3.meego.com/
> xorg-x11-server-Xephyr-1.8.0-7.1.i586.rpm ???
> I tried to install this old Xephyr and
> meego-simulator-launcher-handset-1.0.1-1.1.i586.rpm into the latest image
> http://repo.meego.com/MeeGo/builds/trunk/1.0.90.1.20100907.1/handset/images/
> meego-handset-ia32-mtf-devel/
> 
> then I tried to run startmeego, Xephyr window did appear, but it was alwary
> balck screen.
> Could you please give some suggestions?
> Thanks a lot!
> 
>  
> 
> 
> 
> 
> 2010/9/10 Feng, Haitao 
> 
> Hi,
> 
> I will update Xephyr as Xorg upgrades to 1.9.0. There should not be such a
> rpm
> downloadable at this time. When I finish updating, we will publish the 
> rpm.
> 
> I will submit my patch to Xorg dev mailing list, if you are a developer, I
> welcome you to have a code review there.
> 
> At this time, you could use the old Xephyr downloadable from
> meego.com/developers.
> 
> Thanks
> -Haitao
> 
> On Thu, Sep 09, 2010 at 08:32:22PM +0800, Chengwei Wu wrote:
> > Dear all:
> > I downloaded the package xorg-x11-server-Xephyr-1.9.0-16.1.i586.rpm
> from
> > http://download.meego.com/live/devel:/tools:/sdk/Trunk/i586/
> > But it is empty. Ridiculous! what's wrong? who can tell me   Thanks in
> advance!
> >
> > PS: In http://repo.meego.com/MeeGo/builds/trunk/1.0.90.1.20100907.1/
> core/
> > repos/ia32/packages/i586/, there is xorg-x11-server-1.9.0-1.32.i586.rpm
> > But no corresponding package xorg-x11-server-Xephyr-1.9.0-1.32.i586.rpm
> where
> > can I get it?
> >
> > Your help will be appreciated!
> > 
> > Best Regards!
> > Chengwei Wu
> >
> 
> > ___
> > MeeGo-dev mailing list
> > MeeGo-dev@meego.com
> > http://lists.meego.com/listinfo/meego-dev
> 
> 
> 
> 
> 
> --
> 
> Best Regards!
> Chengwei Wu
> 
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] [PATCH 2/3] Enable off-screen rendering feature for Xephyr

2010-09-20 Thread Feng, Haitao 
Hi,

This patch will enable off-screen rendering feature for Xephyr.

Basically on Xephyr host side, I use XCompositeRedirect to do the off-screen
rendering after creating a host peer window. And when glSwapBuffer happens in
Xephyr clients, I will copy the host peer window contents into Xephyr and
register a damage to let the Xephyr clients redraw the content.

This feature could be disabled by -noosr.

Thanks
-Haitao 

Signed-off-by: Haitao Feng 
---
 configure.ac   |3 ++
 hw/kdrive/ephyr/dri2.h |   10 +--
 hw/kdrive/ephyr/dri2buffer.h   |   45 ++
 hw/kdrive/ephyr/ephyr.c|   45 ++
 hw/kdrive/ephyr/ephyrdri2.c|1 +
 hw/kdrive/ephyr/ephyrdri2.h|3 +-
 hw/kdrive/ephyr/ephyrdri2ext.c |   38 +++--
 hw/kdrive/ephyr/ephyrdri2ext.h |   10 ++
 hw/kdrive/ephyr/ephyrinit.c|8 +
 hw/kdrive/ephyr/hostx.c|   60 +++-
 hw/kdrive/ephyr/hostx.h|7 
 11 files changed, 216 insertions(+), 14 deletions(-)
 create mode 100644 hw/kdrive/ephyr/dri2buffer.h

diff --git a/configure.ac b/configure.ac
index 95f7a76..daea4e0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2069,6 +2069,9 @@ if test "$KDRIVE" = yes; then
 if test "x$DRI" = xyes && test "x$GLX" = xyes; then
 XEPHYR_REQUIRED_LIBS="$XEPHYR_REQUIRED_LIBS $LIBGL libdrm"
 fi
+if test "x$DRI2" = xyes && test "x$GLX" = xyes; then
+XEPHYR_REQUIRED_LIBS="$XEPHYR_REQUIRED_LIBS $LIBGL xcomposite"
+fi
 
 PKG_CHECK_MODULES(XEPHYR, $XEPHYR_REQUIRED_LIBS, [xephyr="yes"], 
[xephyr="no"])
 if test "x$XEPHYR" = xauto; then
diff --git a/hw/kdrive/ephyr/dri2.h b/hw/kdrive/ephyr/dri2.h
index 9db77f4..1d32cad 100644
--- a/hw/kdrive/ephyr/dri2.h
+++ b/hw/kdrive/ephyr/dri2.h
@@ -36,15 +36,7 @@
 #include 
 #include 
 #include 
-
-typedef struct
-{
-   unsigned int attachment;
-   unsigned int name;
-   unsigned int pitch;
-   unsigned int cpp;
-   unsigned int flags;
-} DRI2Buffer;
+#include "dri2buffer.h"
 
 extern Bool
 DRI2QueryExtension(Display * display, int *eventBase, int *errorBase);
diff --git a/hw/kdrive/ephyr/dri2buffer.h b/hw/kdrive/ephyr/dri2buffer.h
new file mode 100644
index 000..ab219c2
--- /dev/null
+++ b/hw/kdrive/ephyr/dri2buffer.h
@@ -0,0 +1,45 @@
+/*
+ * Copyright © 2007,2008 Red Hat, Inc.
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a
+ * copy of this software and associated documentation files (the "Soft-
+ * ware"), to deal in the Software without restriction, including without
+ * limitation the rights to use, copy, modify, merge, publish, distribute,
+ * and/or sell copies of the Software, and to permit persons to whom the
+ * Software is furnished to do so, provided that the above copyright
+ * notice(s) and this permission notice appear in all copies of the Soft-
+ * ware and that both the above copyright notice(s) and this permission
+ * notice appear in supporting documentation.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+ * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABIL-
+ * ITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY
+ * RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN
+ * THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSE-
+ * QUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
+ * DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+ * TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFOR-
+ * MANCE OF THIS SOFTWARE.
+ *
+ * Except as contained in this notice, the name of a copyright holder shall
+ * not be used in advertising or otherwise to promote the sale, use or
+ * other dealings in this Software without prior written authorization of
+ * the copyright holder.
+ *
+ * Authors:
+ *   Kristian Høgsberg (k...@redhat.com)
+ */
+
+#ifndef _DRI2BUFFER_H_
+#define _DRI2BUFFER_H_
+
+typedef struct
+{
+   unsigned int attachment;
+   unsigned int name;
+   unsigned int pitch;
+   unsigned int cpp;
+   unsigned int flags;
+} DRI2Buffer;
+
+#endif
diff --git a/hw/kdrive/ephyr/ephyr.c b/hw/kdrive/ephyr/ephyr.c
index e4252ee..47bd82d 100644
--- a/hw/kdrive/ephyr/ephyr.c
+++ b/hw/kdrive/ephyr/ephyr.c
@@ -55,6 +55,7 @@ KdPointerInfo *ephyrMouse;
 EphyrKeySyms ephyrKeySyms;
 Bool ephyrNoDRI=FALSE ;
 Bool ephyrNoDRI2=FALSE ;
+Bool ephyrNoOSR=FALSE ;
 Bool ephyrNoXV=FALSE ;
 
 static int mouseState = 0;
@@ -663,6 +664,7 @@ ephyrInitScreen (ScreenPtr pScreen)
   if (!ephyrNoDRI) {
 ephyrDRIExtensionInit (pScreen) ;
 ephyrHijackGLXExtension () ;
+ephyrNoOSR = TRUE ;
   }
 #endif
 
@@ -675,6 +677,9 @@ ephyrInitScreen (ScreenPtr pScreen)
   if (ephyrNoDRI && !ephyrNoDRI2) {
 ephyrDRI2ExtensionInit (pScreen) ;
 ephyrHijackGLXExtension () ;
+if (!ephyrNoOSR && !hostx_has_composite ()) {
+

[MeeGo-dev] [PATCH 3/3] Enable notfp feature for Xephyr

2010-09-20 Thread Feng, Haitao 
Hi,

This patch will enable a feature to disable GLX_texture_from_pixmap extension
for Xephyr.

Currently the glXPixmap is not supported in Xephyr. So I provide an option to
disable GLX_texture_from_pixmap extension in Xephyr.

The GLX_texture_from_pixmap could be disabled by -notfp option.

Thanks
-Haitao

Signed-off-by: Haitao Feng 
---
 hw/kdrive/ephyr/ephyr.c|1 +
 hw/kdrive/ephyr/ephyrhostglx.c |   27 +++
 hw/kdrive/ephyr/ephyrinit.c|8 
 3 files changed, 36 insertions(+), 0 deletions(-)

diff --git a/hw/kdrive/ephyr/ephyr.c b/hw/kdrive/ephyr/ephyr.c
index 47bd82d..c1faeca 100644
--- a/hw/kdrive/ephyr/ephyr.c
+++ b/hw/kdrive/ephyr/ephyr.c
@@ -56,6 +56,7 @@ EphyrKeySyms ephyrKeySyms;
 Bool ephyrNoDRI=FALSE ;
 Bool ephyrNoDRI2=FALSE ;
 Bool ephyrNoOSR=FALSE ;
+Bool ephyrNoTFP=FALSE ;
 Bool ephyrNoXV=FALSE ;
 
 static int mouseState = 0;
diff --git a/hw/kdrive/ephyr/ephyrhostglx.c b/hw/kdrive/ephyr/ephyrhostglx.c
index 728687b..2475c8a 100644
--- a/hw/kdrive/ephyr/ephyrhostglx.c
+++ b/hw/kdrive/ephyr/ephyrhostglx.c
@@ -153,6 +153,10 @@ typedef struct GLXGenericGetString {
 #define sz_xGLXGenericGetStringReq 12
 #define X_GLXGenericGetString 0
 
+#ifdef DRI2
+extern Bool   ephyrNoTFP;
+#endif
+
 Bool
 ephyrHostGLXGetStringFromServer (int a_screen_number,
  int a_string_name,
@@ -166,6 +170,13 @@ ephyrHostGLXGetStringFromServer (int a_screen_number,
 xGLXSingleReply reply;
 int length=0, numbytes=0, major_opcode=0, get_string_op=0;
 
+#ifdef DRI2
+const char *glx_texture_from_pixmap = "GLX_EXT_texture_from_pixmap ";
+char *start = NULL;
+char *end = NULL;
+int pos = 0, len = 0;
+#endif
+
 EPHYR_RETURN_VAL_IF_FAIL (dpy && a_string, FALSE) ;
 
 EPHYR_LOG ("enter\n") ;
@@ -232,6 +243,22 @@ ephyrHostGLXGetStringFromServer (int a_screen_number,
 EPHYR_LOG ("strname:%#x, strvalue:'%s', strlen:%d\n",
a_string_name, *a_string, numbytes) ;
 
+#ifdef DRI2
+if (ephyrNoTFP) {
+ start = strstr(*a_string, glx_texture_from_pixmap);
+ if (start){
+ EPHYR_LOG ("strname:%#x, strvalue:'%s', strlen:%d\n",
+a_string_name, *a_string, numbytes) ;
+ len = strlen(glx_texture_from_pixmap);
+ pos = start - *a_string;
+ end = start + strlen(glx_texture_from_pixmap);
+ memmove(start, end, numbytes + 1 - pos - len);
+ EPHYR_LOG ("strname:%#x, strvalue:'%s', strlen:%d\n",
+a_string_name, *a_string, numbytes) ;
+ }
+}
+#endif
+
 is_ok = TRUE ;
 out:
 EPHYR_LOG ("leave\n") ;
diff --git a/hw/kdrive/ephyr/ephyrinit.c b/hw/kdrive/ephyr/ephyrinit.c
index 07e6c65..5492e40 100644
--- a/hw/kdrive/ephyr/ephyrinit.c
+++ b/hw/kdrive/ephyr/ephyrinit.c
@@ -38,6 +38,7 @@ extern Bool   kdHasKbd;
 extern Bool   ephyrNoDRI;
 extern Bool   ephyrNoDRI2;
 extern Bool   ephyrNoOSR;
+extern Bool   ephyrNoTFP;
 extern Bool noGlxVisualInit;
 #endif
 extern Bool   ephyrNoXV;
@@ -124,6 +125,7 @@ ddxUseMsg (void)
   ErrorF("-nodri   do not use DRI\n");
   ErrorF("-nodri2  do not use DRI2\n");
   ErrorF("-noosr   do not use off-screen rendering\n");
+  ErrorF("-notfp   do not use texture from pixmap extension\n");
 #endif
   ErrorF("-noxvdo not use XV\n");
   ErrorF("-name [name] define the name in the WM_CLASS property\n");
@@ -265,6 +267,12 @@ ddxProcessArgument (int argc, char **argv, int i)
EPHYR_LOG ("no off-screen rendering enabled\n") ;
return 1 ;
}
+  else if (!strcmp (argv[i], "-notfp"))
+   {
+   ephyrNoTFP = TRUE ;
+   EPHYR_LOG ("no texture from pixmap enabled\n") ;
+   return 1 ;
+   }
 #endif
   else if (!strcmp (argv[i], "-noxv"))
{
-- 
1.6.1.3

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Why does the mcompositor's compositing functionality depend on the type of the topmost window?

2010-10-21 Thread Feng, Haitao 
Dear mcompositor developers,

Yongsheng and I have a question on mcompositor, why does the compositing
functionality depend on the type of the topmost window?

The function MCompositeManagerPrivate::possiblyUnredirectTopmostWindow() will
judge whether the topmost root window isAppWindow(true), if it is true, it will
not do the compositing. Otherwise it will do the compositing which means it will
get the texture of the topmost window, combine the decorator texture and draw
them into full screen on mcompositor's GL window.

Comparing the below two alternative coding logics:
1. If it is AppWindow, draw the AppWindow's texture on compositor's GL
window. This means mcompositor's GL window will be always mapped. 
2. If it is not AppWindow, combine it with decorator directly and do not 
touch
texture staff. This means mcompositor is only used for window animation.

Is there any special consideration on this design logic? 

Thanks
-Haitao
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Why does the mcompositor's compositing functionality depend on the type of the topmost window?

2010-10-21 Thread Feng, Haitao 
Hi Abdiel,

Thank you very much for your reply!

I get the mcompositor source code by "zypper si meegotouch-compositor" after
extracting the MeeGo 10-15 handset image and chrooting into it. The version is
0.5.8 and the mcompositemanager.cpp is attached. This is the code base I will be
working for. I am the developer to run MeeGo UX inside Xephyr or Qemu with GL
acceleration, as mcompositor sometimes crashes in Xephyr or Qemu, I am trying to
find out whether it is our code's bug or mcompositor's bug.

Because of your surprise, I checked out your git repo at
http://www.meego.gitorious.org/meegotouch/meegotouch-compositor. The git codes
are quite newer than 0.5.8. Mcompositemanagerextension,
mcompositewindowshadereffect and loadPlugin are all not in 0.5.8. But for
possiblyUnredirectTopmostWindow, our question still applied, it seems that "if
(w == stack[DESKTOP_LAYER])" has the same effect as "cw->isMapped() &&
cw->isAppWindow(true)".

I am interested with alternative 1, as you said, "Application windows do not
need to be composited all the time. Native meegotouch applications draw their
own window decorations and borders and do not need the decorator from the
compositor." Yes, the fullscreen application, such as video player or high-speed
games, do not need to be composited as the performance might not be good
enough. Are the meegotouch applications all belongs to this category?

Yongsheng is interested with alternative 2, as you said, "Decorator is for 3rd
party apps such as games that do not use the meegotouch framework." Our question
is that: Why draw their texture into compositor's GL window instead of draw them
directly and unmap the overlay as you did for meegotouch applications when
animation is finished? Robert has suggested that maybe for 3rd party apps, you
want to give them some window effect, such as fog, while meegotouch applications
do not need or already have the window effect. Is it the answer for
"mcompositor's compositing functionality depend on the type of the topmost
window"?

Thanks
-Haitao

On Thu, Oct 21, 2010 at 09:40:58PM +0800, Abdiel Janulgue wrote:
> > The difference here is whether the app window is MTF-based. If it's an app
> >  of non-MTF based, the composite overlay will be shown for animation and
> >  composite decorator and app window. But if it's a MTF-based window,
> >  composite overlay is only for animation from my understanding. I think
> >  it's because of performance concern. Could Anyone who knows about it tell
> >  us the root cause?
> 
> I don't completely get what you're trying to say here. The overlay is always 
> needed whenever composition use case is triggered - whether it is needed for 
> animating the windows or for using the decorator. For all other use case, 
> each 
> window should be rendering directly to the framebuffer.
> 
> -abdiel
> 
> > 
> > Cheers,
> > Yongsheng
> > 
> > > -Original Message-
> > > From: Ohly, Patrick
> > > Sent: Thursday, October 21, 2010 8:37 PM
> > > To: Feng, Haitao
> > > Cc: meego-dev@meego.com; Zhu, Yongsheng; MeeGo Touch
> > > Development
> > > Subject: Re: [MeeGo-dev] Why does the mcompositor's
> > > compositing functionality depend on the type of the topmost
> > > window?
> > >
> > > Hello Haitao!
> > >
> > > You might have a better chance getting an answer to the
> > > email below on
> > > the MTF mailing list. On CC and Reply-To set.
> > >
> > > On Do, 2010-10-21 at 11:29 +0100, Feng, Haitao wrote:
> > > > Dear mcompositor developers,
> > > >
> > > > Yongsheng and I have a question on mcompositor, why does
> > >
> > > the compositing
> > >
> > > > functionality depend on the type of the topmost window?
> > > >
> > > > The function
> > >
> > > MCompositeManagerPrivate::possiblyUnredirectTopmostWin
> > > dow() will
> > >
> > > > judge whether the topmost root window isAppWindow(true),
> > >
> > > if it is true, it will
> > >
> > > > not do the compositing. Otherwise it will do the compositing
> > >
> > > which means it will
> > >
> > > > get the texture of the topmost window, combine the
> > >
> > > decorator texture and draw
> > >
> > > > them into full screen on mcompositor's GL window.
> > > >
> > > > Comparing the below two alternative coding logics:
> > > > 1. If it is AppWindow, draw the AppWindow's texture
> > >
> > > on c

Re: [MeeGo-dev] libglx.so for virtualbox

2010-10-28 Thread Feng, Haitao 
Hi CSJ,

You need to modify and build the Xorg code to get libglx.so.

The modification is in:
xserver/glx/glxdriswrast.c:__glXDRIscreenProbe,
change from 
screen->base.GLXmajor = 1;
screen->base.GLXminor = 4;
to 
screen->base.GLXmajor = 1;
screen->base.GLXminor = 2;

This is only for MeeGo 05-24 image. Currently the issue has been fixed and
clutter could be started up by software rendering, so for latest MeeGo netbook
image, you do not need this step any more. However, you still need to set the
suid for guest Xorg.

Thanks
-Haitao 

On Thu, Oct 28, 2010 at 02:08:46PM +0800, CSJ wrote:
> Hi, all
> 
> In Meego wiki:
> http://wiki.meego.com/MeeGo_1.0_Netbook_VirtualBox
> 
> mentioned Download Libglx.so.gz
>   Replace libglx.so for an X issue, this libglx.so will put glx version to 
> 1.2,
> instead of 1.4.
> 
> is there any source code of this libglx.so?
> Or say, where does this libglx.so com from?
> 
> Thanks,
> CSJ
> 

> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] MeeGo app model in 2012: Rethinking the MeeGo app model to be more platform agnostic

2011-05-31 Thread Feng, Haitao 
I also think so.

Recently I have made llvmpipe working inside chroot+Xephyr, the graphics 
performance is very good.
Currently llvm is not in the MeeGo distro, what is the process to get it inside 
MeeGo?

Thanks
-Haitao

-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of Carsten Munk
Sent: Tuesday, May 31, 2011 5:25 PM
To: Zhang, Zheng
Cc: meego-dev
Subject: Re: [MeeGo-dev] MeeGo app model in 2012: Rethinking the MeeGo app 
model to be more platform agnostic

Yes, indeed - I've been fed the usual JVM and JIT knowledge through my
university education like many others, but this isn't the approach
taken in MeeGo currently as we have to write C++ for our native Qt
Quick extensions and we don't have a JVM on each device.

I feel that LLVM could give some good opportunities for MeeGo in this area.

BR
Carsten Munk

2011/5/31 Zhang, Zheng :
> Android has done most of such jobs via JVM.
>
> -Original Message-
> From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
> Behalf Of Carsten Munk
> Sent: Tuesday, May 31, 2011 2:11 PM
> To: meego-dev
> Subject: [MeeGo-dev] MeeGo app model in 2012: Rethinking the MeeGo app model 
> to be more platform agnostic
>
> Hi,
>
> One of the disadvantages of MeeGo is that unlike Android and other OS'es, we 
> don't provide a way for developers to provide one MeeGo compliant RPM for 
> typical MeeGo applications+extensions that will run on all MeeGo devices, no 
> matter if it is IA, ARM, MIPS. I'd like to spark a technical (+ compliance) 
> discussion on if we can somehow make this reality.
>
> I'd like a world where it matters less what architecture a MeeGo device runs, 
> or even specific optimization flags/architectures not in line with what 
> meego.com builds when it comes to compliance, allowing more flexibility in 
> hardware choice and hardware directions over the long term.
>
> Opinions that this isn't feasible is more than welcome :) Since we're all 
> about fast innovation now, here's one idea to think about.
>
> With the news of Qt5 the new future application model[1] is clear. It 
> motivates that 'While offering all of the power of native Qt using
> C++, the focus should shift to a model, where C++ is mainly used to
> implement modular backend functionality for Qt Quick.'. This will cause a 
> development model for MeeGo API apps along lines of:
>
> * QML applications, platform agnostic, distributed as 'noarch' RPM packages. 
> Contains QML/js files, resources, etc.
> * Qt Quick modules, platform agnostic, written in QML/js, distributed as 
> 'noarch' RPM packages (think widget sets, etc)
> * C++ Qt Quick modules, platform specific, distributed as 
> i586/armv7hl/mips/etc RPM packages. Contains compiled native code specific to 
> a target processor. Typically shared objects.
>
> As you can see, we're 2/3 there to where it essentially doesn't matter what 
> the underlying device runs, except that it provides certain APIs/runtimes for 
> the QML apps to use. Having a MeeGo Core that we can optimize towards 
> specific use cases and hence a wider market for MeeGo to be used in.
>
> I'd like to propose that we go to a model where we have one MeeGo API SDK 
> with one toolchain that targets the MeeGo platform, no matter the hardware 
> architecture. This means, take C++ Qt Quick modules and build them into a 
> platform agnostic format (intermediate language) that is then translated by 
> an application store or by device itself into native code, which is then run 
> on the device.
>
> Google has already been working on a similar approach for their Native Client 
> work, based on the LLVM intermediate format[2] and I think this is plausible 
> to do for MeeGo too in a similar fashion in a short timeframe. They have been 
> working on shared objects as well[3].
>
> Now, there are some issues to be discussed and I'll list some of them:
>
> 1) Performance loss - will there be any noticable loss in application 
> performance? Will it be mitigated by the fact the MeeGo platform + Qt stack 
> is optimized to the target as that's where the real work goes on usually?
> 2) Will ARM or IA/Atom specific optimizations be lost if LLVM is used?
> 3) Licensing issues (GPLv3/LLVM license/etc?)
> 4) Security implications/signing issues/etc
> 5) Obfuscation and reverse engineering implications of IL being used.
> 6) Compliance implications
> 7) Hardware specific extensions
>
> And last of all:
>
> Is it plausible to have a C++ extension in LLVM intermediate language 
> (targetted towards a fictional machine description) that links without issue 
> into the native Qt stack across architectures?
>
> Let me hear your thoughts - I think this could be a significant platform win.
>
> BR
> Carsten Munk
>
> [1] http://labs.qt.nokia.com/2011/05/09/thoughts-about-qt-5/
> [2] http://nativeclient.googlecode.com/svn/data/site/pnacl.pdf
> [3] http://www.chromium.org/nativeclient/pnacl
>