Re: [MeeGo-dev] conflicting screen dimensions on netbook

On 2/21/2011 10:22 PM, saurabh chakrabarty wrote: Hi all, On MeeGo 'xdpyinfo | grep dim' gives as output 1024x600 pixels and 214 mm x 127 mm. On Ubuntu we get 1024x600 pixels and 270 mm x 158 mm. have you tried using a ruler and measuring the actual screen dimension? If so, what is it?

Re: [MeeGo-dev] Fail to run the Phoronix "qgears2" test suit for 3D benchmark.

On 2/21/2011 6:05 PM, jms yang wrote: hi There Just verified that the Phoronix test suit "qgears" with OpenGL rendering is capable to test on Acer AspireOne with pinetrail image(e.g. MeeGo release 1.1.90 (MeeGo) BUILD: meego-tablet-ia32-pinetrail-1.1.90.2.20110207.22) smoothly. Is there any

Re: [MeeGo-dev] kernel_panic on on mrst-mtf image

On 2/21/2011 5:05 AM, praveen pandey wrote: Hi, I am using http://repo.meego.com/MeeGo/builds/1.1.90/1.1.90.2.20110208.4/handset/images/meego-handset-ia32-mrst-mtf/ image on moorsetown Hardware but I am not able to boot. I have attached the logs here. somewhere in the call trace it points

Re: [MeeGo-dev] Upstart in MeeGo 1.2

On 2/17/2011 2:46 PM, John Veness wrote: On 17/02/11 09:03, Tapio Rantala wrote: pe, 2011-01-07 kello 16:11 +0200, ext Tapio Rantala kirjoitti: Hi all! We are preparing upstart so that it would be integrated in meego 1.2 and therefore replace sysvinit as init provider. Hi Due to recent ev

Re: [MeeGo-dev] Upstart in MeeGo 1.2

On 2/17/2011 1:08 AM, Carsten Munk wrote: 2011/2/17 Tapio Rantala: pe, 2011-01-07 kello 16:11 +0200, ext Tapio Rantala kirjoitti: Hi all! We are preparing upstart so that it would be integrated in meego 1.2 and therefore replace sysvinit as init provider. Hi Due to recent events work on this

Re: [MeeGo-dev] Xorg restart issue in meego 1.1.80.6 release

On 2/16/2011 5:00 AM, dhaval bc wrote: hi all, I am working on meego-1.1.80.6 handset-mtf image on moorestown platform, i have noticed that once Xorg crashes it fails to restart, but the same works fine on meego 1.1-handset-mtf image. Do i have to edit any configuration file to auto restart Xo

Re: [MeeGo-dev] glibc vs. eglibc

On 2/15/2011 10:11 AM, Syed Faisal Akber wrote: Jeremiah, There are a number of libc alternatives out there for embedded systems. They include: uC-libc - http://www.uClinux.org/ uClibc - http://www.uclibc.org/ newlib - http://www.sourceware.org/newlib/ There are more that I'm not including her

Re: [MeeGo-dev] glibc vs. eglibc

On 2/15/2011 8:57 AM, Jeremiah Foster wrote: None of the replies answers the question, which I'll repeat; is there a reason why MeeGo uses one and not the other? yes. we use the "real" glibc that most folks are using the eglibc team is relative new with little track record (this is nothin

[MeeGo-dev] Evicting someone from the meego mailing lists (was Re: Buyout of Nokia)

On 2/13/2011 1:12 PM, Randolph Dohm didn't we warn you several times before that what you are doing is offtopic and rude for meego-dev ? Your post, again and as usual, has nothing to do with anything technical or development related. Administrators, please consider banning this "Randolph Dohm

Re: [MeeGo-dev] BME (Battery Management Entity) on MeeGo

On 2/9/2011 3:30 AM, Rémi Denis-Courmont wrote: On Saturday 29 January 2011 10:42:28 ext Carsten Munk, you wrote: 2011/1/29 Lego Ming: Hi all, We want to study the Battery Management Mechanism on MeeGo Handset. The battery management mechanism on MeeGo handset is up to the individual hardware

Re: [MeeGo-dev] updated MeeGo compliance spec available for review

On 2/7/2011 10:0st "core') If you compile your app against libssl in Meego 1.1 it will link against libssl.so.8, when you go to Meego 1.1.90->1.2 your app won't load as libssl.so.10 is there. If you symlink it may work, but you can never know as that's why the version changed in the first pla

Re: [MeeGo-dev] updated MeeGo compliance spec available for review

On 2/7/2011 9:03 AM, Gabriel M. Beddingfield wrote: On Mon, 7 Feb 2011, Sergio Schvezov wrote: Suppose that your app needs 3rd party libs and you install them in the folder /opt/foo/lib. Before you start your app, you can manipulate the LD_LIBRARY_PATH to pull in your lib folder. [snip] S

Re: [MeeGo-dev] updated MeeGo compliance spec available for review

On 2/7/2011 4:41 AM, Antti Kaijanmäki wrote: On Fri, 2011-02-04 at 08:43 -0700, Wichmann, Mats D wrote: Hoping some of you have time to take a look and supply comments... http://wiki.meego.com/Quality/Compliance, as usual. current version is the .7 revision. "Section 3: Application Compatibil

Re: [MeeGo-dev] updated MeeGo compliance spec available for review

On 2/4/2011 12:10 PM, Antti Kaijanmäki wrote: On Fri, 2011-02-04 at 14:32 -0500, Bernd Stramm wrote: On Fri, 04 Feb 2011 21:21:04 +0200 Kernels have supported IPv6 for years, unless they are specifically configured not to. Yes, but sadly there are products where kernels are specifically configu

Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

On 2/2/2011 6:43 AM, Glen Gray wrote: or we all spend time making the opensource BCM driver work on 2.6.37 this sounds like a really good idea regardless of anything else. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo

Re: [MeeGo-dev] gstreamer vaapi support on meego

On 2/2/2011 4:07 AM, navin karnam wrote: Hi All, Whether Meego 1.1 official release supports video playback using the vaapi elements of the gstreamer (vaapidecode or vaapisink) on Intel moorestown platform? Do we need to upgrade the libva or patch graphics drivers to get for the vaapi elemen

Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

On 2/1/2011 12:57 PM, Rudolf Streif wrote: Thank you. Yes, I did download the latest source from http://www.broadcom.com/support/802.11/linux_sta.php. The version number is 5.100.82.38 which is the version of the spec file. It's the one I am having issues with. not to be an ass about it, but

Re: [MeeGo-dev] Libva support on meego 1.1

On 2/1/2011 6:03 AM, john pratss wrote: Hi, I have tried a gstreamer pipeline to play a video, pipeline freezes while libva is trying to open the pvr graphics driver, so could not able play the video. The pipeline is run on the mego 1.1 official release on a Intel moorestown platform. yikes

Re: [MeeGo-dev] Nokia alert: android rised from 17 % marketshare to 32 % and is bigger than symbian.

On 1/31/2011 12:35 PM, Randolph Dohm wrote: 2011/1/31 Arjan van de Ven: On 1/31/2011 12:32 PM, Randolph Dohm wrote: http://www.heise.de/newsticker/meldung/Smartphones-Android-ueberholt-Symbian-Apple-verliert-Marktanteile-1180547.html?view=zoom;zoom=1 http://www.canalys.com/pr/2011/r2011013

Re: [MeeGo-dev] Nokia alert: android rised from 17 % marketshare to 32 % and is bigger than symbian.

On 1/31/2011 12:32 PM, Randolph Dohm wrote: http://www.heise.de/newsticker/meldung/Smartphones-Android-ueberholt-Symbian-Apple-verliert-Marktanteile-1180547.html?view=zoom;zoom=1 http://www.canalys.com/pr/2011/r2011013.html ___ please tell me why thi

Re: [MeeGo-dev] BME (Battery Management Entity) on MeeGo

On 1/28/2011 5:54 PM, Lego Ming wrote: Hi all, We want to study the Battery Management Mechanism on MeeGo Handset. Like: The voltage threshold corresponding to different battery level. (for example, display 2 level if current voltage is 3.85v) The low battery management - Low battery to dis

Re: [MeeGo-dev] Ext3 on handset images instead of Btrfs

On 1/28/2011 6:32 AM, Carsten Munk wrote: 2011/1/28 Arjan van de Ven: On 1/28/2011 4:04 AM, Carsten Munk wrote: Hi, We just noticed we (N900 images) seem to be the only ones using btrfs on Handset images[1] [2]. When was this change made and is it an error? If not, why? Do we have a new

Re: [MeeGo-dev] Ext3 on handset images instead of Btrfs

On 1/28/2011 4:04 AM, Carsten Munk wrote: Hi, We just noticed we (N900 images) seem to be the only ones using btrfs on Handset images[1] [2]. When was this change made and is it an error? If not, why? Do we have a new default filesystem for the default configuration? MeeGo's default filesyste

Re: [MeeGo-dev] flash filesystem support on meego

On 1/27/2011 9:34 PM, dhaval bc wrote: Hi all, Is meego planning to support any of the nand flash filesystems like yaffs2 or jffs2 ??? Currently meego supports ext3 and btrfs, ext3 is not much of a nand flash filesystem and filesystem corruption issues that exists on ext3 since it does not sup

Re: [MeeGo-dev] I2C device in MeeGo 1.1

On 1/27/2011 5:07 AM, Roman Gezikov wrote: Hello, Could anyone help me to understand what needs to be done to get I2C device seen in file system? We use MeeGo 1.1 Netbook on IA board (Advantech AIMB-212). i2c devices/busses aren't self-enumerating (as general rule) so to get an i2c devic

Re: [MeeGo-dev] ospmd on aava

kage is NOT useful in MeeGo. Don't use it. It doesn't do anything. thanks again, Raghavendra On Thu, Jan 20, 2011 at 1:43 AM, Arjan van de Ven mailto:ar...@linux.intel.com>> wrote: On 1/19/2011 8:36 PM, raghu wrote: Hi, I saw upowerd daemon running on

Re: [MeeGo-dev] build.meego.com Down

On 1/25/2011 6:33 AM, Ryan Ware wrote: Server is back up. almost Transmitting file data .Server returned an error: HTTP Error 400: Bad Request ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Dconf

On 1/24/2011 11:38 PM, Dave Neary wrote: Arjan van de Ven wrote: Heck, app writers wouldn't even notice the difference if you use the proper abstraction API. ... which is, presumably, GSettings? since MeeGo API's are Qt based... it'll

Re: [MeeGo-dev] Dconf

On 1/24/2011 10:29 PM, Laurent Pinchart wrote: I agree with Aaron that just embracing what Ubuntu does and create Ubuntu- specific versions of Qt applications is a bad idea. If dconf is the way to go, it needs to be properly integrated into Qt instead of coming as Ubuntu- specific bindings. Then

Re: [MeeGo-dev] ospmd on aava

On 1/19/2011 8:36 PM, raghu wrote: Hi, I saw upowerd daemon running on MeeGo 1.1, and wanted to remove it and test ospmd on aava device. May I know the dependencies involved, either from kernel or other modules. and please let me know how to proceed in resolving those dependencies. I know tha

Re: [MeeGo-dev] Dconf

On 1/19/2011 2:49 PM, Rob Taylor wrote: On 19 Jan 2011, at 00:28, Arjan van de Ven wrote: On 1/19/2011 6:11 AM, Ville M. Vainio wrote: Now that the internet is telling me Ubuntu is warming up to Qt and making Qt wrappers for dconf... Perhaps this is a bandwagon meego should jump to? It&#

Re: [MeeGo-dev] Dconf

On 1/19/2011 6:11 AM, Ville M. Vainio wrote: Now that the internet is telling me Ubuntu is warming up to Qt and making Qt wrappers for dconf... Perhaps this is a bandwagon meego should jump to? It's not like we have anything better lined up in that area. -- this has come up several times

Re: [MeeGo-dev] NFC

On 1/18/2011 11:29 AM, Tom Chen wrote: Hi, Michael thanks for your information, i could found open nfc sdk for Andorid in sourceforge. but i could not find any place to download the source code of that, is it really open source already? the www.open-nfc.org said

Re: [MeeGo-dev] Audio stack question

On 1/18/2011 9:10 AM, Darren Mohle wrote: Does Meego use the standard Linux audio stack? Is it roughly (as I currently understand it): ([A] applications) --> ([B] optional higher level libs [gstreamer/qtmobility/etc]) --> ([C] optional lower level libs [alsa_userlib/oss]) --> ([D] pulseaudio) -

Re: [MeeGo-dev] Power Management on Meego 1.2

On 1/14/2011 5:32 AM, raghu wrote: Hi, I would like to know the plans about/Power Management/ and /Thermal Management/ for /Moorestown/ on Meego 1.2. well if you are familiar with Linux Power Management. you already know the answer to the power management part of your question... MeeGo

Re: [MeeGo-dev] ARM RunFast by default in glibc

On 1/12/2011 1:06 AM, Carsten Munk wrote: Hi (ARM toolchain group mostly) Do we have a patch for glibc-2.11-12-g24c0bf7 and/or glibc-2.12.1 that enables ARM RunFast[1] mode by default anywhere? Would be good to push it along with hardfp while we're at it and getting things tested through. can

Re: [MeeGo-dev] Spectra driver - Moorestown Platform

On 1/11/2011 8:42 PM, Jesslyn Abdul Salam wrote: HI , Due to certain hard constraints on our platform, we are mandated to use ext3 and NAND FTL (and not MTD). It would be very difficult to consider UBIFS inspite of the obvious benefits there. are you using the current driver (from the 2.6.37

Re: [MeeGo-dev] [Meego-kernel] Can't run Meego at Intel New platform oak trail !!

On 1/10/2011 9:00 AM, Jechlitschek, Christoph wrote: Hi Arjan, I believe I have the same issue. Is there any public image available that boots with UX on OakTrail? It may be a stupid question, but what's wrong with the netbook image? I added the pvr-bin and psb-video to the netbook image and I

Re: [MeeGo-dev] [Meego-kernel] Can't run Meego at Intel New platform oak trail !!

On 1/10/2011 12:19 AM, tang.xin...@byd.com wrote: hi meego guys: I have Intel OAK TRAIL mainboard, but can't run Meego.At meego.com not to supply,have not GMA600 driver. so I make new Meego ISO that use MIC that use http://repo.meego.com/MeeGo/builds/trunk/daily/core/repos/sou

Re: [MeeGo-dev] Upstart in MeeGo 1.2

On 1/10/2011 5:09 AM, Pertti Kellomäki wrote: On 01/07/2011 04:11 PM, ext Tapio Rantala wrote: We are preparing upstart so that it would be integrated in meego 1.2 and therefore replace sysvinit as init provider. For average meego package, this does not change much. Upstart supports sysvinit st

Re: [MeeGo-dev] Upstart in MeeGo 1.2

On 1/8/2011 2:49 PM, Leonid Batizhevsky wrote: PS: initV support parallel start and depends (see in debian) the point of upstart isn't parallel start; that's almost the worst feature of upstart to be honest (but obviously I expect this to be done correctly and properly as part of the ups

Re: [MeeGo-dev] Upstart in MeeGo 1.2

On 1/7/2011 6:46 AM, Dave Neary wrote: Hi, Glen Gray wrote: For average meego package, this does not change much. Upstart supports sysvinit style init scripts so they will continue to work as usual. This raises then the obvious question of Why ? What tangible benefits does moving to Upstart of

Re: [MeeGo-dev] Do someone knows how to Fixed highest frequency in MeeGo?

On 1/7/2011 12:39 AM, Zhu, Junmin wrote: I want toavoid the uncertain impact of dynamically adjusted frequencies, so try to set fixed highest frequency for intel CPU in MeeGo. as a general rule, applications and such do not get to do that. if you are making your own device/product, you can

Re: [MeeGo-dev] Upstart in MeeGo 1.2

On 1/7/2011 7:10 AM, Glen Gray wrote: On 7 Jan 2011, at 14:46, Dave Neary wrote: This raises then the obvious question of Why ? What tangible benefits does moving to Upstart offer. I can answer this... Upstart supports old init style scripts, but that's not all it supports. You can do things

Re: [MeeGo-dev] Upstart in MeeGo 1.2

On 1/7/2011 6:11 AM, Tapio Rantala wrote: Hi all! There has been a lot of discussions about this subject, but unfortunately behind closed doors. Now that I am expected to take action, I'll bring this message forth. We are preparing upstart so that it would be integrated in meego 1.2 and therefo

Re: [MeeGo-dev] Broadcom WiFi guide updated

On 1/5/2011 6:40 AM, Glen Gray wrote: Hey Folks, Just a heads up that the Broadcom drivers have gone through a revision over christmas. I've updated my guide and source rpm to pull down the latest driver. See http://slaine.org/_slaine/Meego_1.1_Wifi.html -- for all of this discussion n

Re: [MeeGo-dev] mono

On 1/4/2011 2:56 PM, Mark S. Townsley wrote: Hi: I am seeing mono as part of Meego distribution. Is that part of Meego core? nope, Mono is not part of the MeeGo core. Mono is being pulled in by some of the reference applications for the Netbook build. you're not required to have Mono, nor

Re: [MeeGo-dev] MeeGo 1.2 Roadmap?

On 1/3/2011 10:10 AM, Dave Neary wrote: just as a side note... since we're about two or so weeks away from feature freeze for 1.2 it should be assumed that all feature requests that get filed are for 1.3 ( in fact, that should have been the case from the day that 1.2 development started, b

Re: [MeeGo-dev] MeeGo 1.2 Roadmap?

On 1/3/2011 2:47 AM, quim@nokia.com wrote: Hi there, Carsten wrote: > So, we're in 2011, we have a release 1.2 in about 4-5 months - and I > wondered, what do we intend on delivering? See, comment, vote: Bug 9908 - Open roadmapping process defined but no implemented http://bugs.meego.com/

Re: [MeeGo-dev] The screen backlight control interface in HW adaptation

On 12/29/2010 10:46 PM, Peter Feng wrote: Dear Sir: I would like to know the screen backlight control interface in Hardware Adaption Layer. Meego's man said that Qmsystem will provide some new APIs for meego, include display backlight control. I think the API have to connect/communication to

Re: [MeeGo-dev] ospm

On 12/29/2010 10:27 PM, raghu wrote: Hi All, I came to know that ospm package in meego will soon be replaced by new package based on power thermal management(PTM). the ospm package in MeeGo needs to be deleted entirely, it serves no useful purpose. if so I am eager to know how soon can

Re: [MeeGo-dev] Accelerometer sensor driver with sysfs interface

On 12/29/2010 7:21 PM, Jia-Chi Lai wrote: Dear Arjan. I'm confused about the different of input event and sysfs. If we use sysfs to replace the input event, are there any information would be lose?? Did you mean that the driver use the sysfs, then the sensorfw would need a sysfs adapotr? And th

Re: [MeeGo-dev] Accelerometer sensor driver with sysfs interface

On 12/28/2010 7:23 PM, Zhao, Forrest wrote: Hi Timo, The default adaptor of accelerometer used input event. If we use sysfs to replace input event, are there any effect of this? Does any information will be lose because of replacing input event to sysfs? I assume no side effect by replacing

Re: [MeeGo-dev] Install MeeGo on Atom CE4100 Videon platform

On 12/27/2010 11:54 AM, Mueller, Robert wrote: Customer question: "I am using the CE4100 development board from Videon. Am I asking in the wrong place? If not... is there any guide for installing MeeGo on it?" This public *development* list is absolutely not the right place to ask customer s

Re: [MeeGo-dev] Is MeeGo a Google product?

On 12/25/2010 8:34 PM, Gaveen Prabhasara wrote: On Sat, Dec 25, 2010 at 5:18 PM, Thiago Macieira wrote: On Saturday, 25 de December de 2010 07:10:59 sajeev.manikk...@nokia.com wrote: Hi, Can't Google Chrome be out of MeeGo distribution? I mean make it available as a seperate downloadable on t

Re: [MeeGo-dev] Meego 1.1 Netbook doesn't support touching?

On 12/20/2010 7:33 PM, He, Yunlong wrote: Hi, Experts, I just installed meego 1.1 netbook to my netbook, but touching pad can’t be used, it seems only “move” events can be detected, but click event can’t be detected, same issue on another tablet. Who knows why? in addition to hardware sup

Re: [MeeGo-dev] Driver module and firmware loading on boot

On 12/19/2010 9:15 PM, Tomasz Sterna wrote: Hi. I would like to insert a wifi driver module and load the firmware for the device on boot. I have few problems though. 1. The driver module is not autoloaded on the device boot. no PCI or firmware enumeration? That sounds like a bug in the platfo

Re: [MeeGo-dev] Error while compiling xulrunner

On 12/19/2010 12:43 PM, Jeremias Bosch wrote: Hello, i try to compile xulrunner (from hg.meego.com ) on meego netbook SDK 1.1 but I end within a compile error: /build-tree/obj-qt- buildxulrunner/xulrunner/nss/shlibsign: symbol lookup error: /usr/lib/libQtCore.so.4: undef

Re: [MeeGo-dev] Xinerama in MeeGo Xorg?

On 12/18/2010 6:42 AM, Carsten Munk wrote: Hi, Out of curiosity, what's the technical reasoning for having Xinerama disabled in MeeGo X.org?\ it's completely obsoleted by the xrandr stuff. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://l

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: Yes, we've seen this happen with previous hardware where we are stuck with 2.6.22 and a kernel config that clashes with newer udev. That's the moment where we either find a way to patch in the needed feature or say 'tough luck, no cookie for us'. I

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

On 12/15/2010 11:28 AM, Carsten Munk wrote: 2010/12/15 Thomas B. Ruecker <mailto:dm8...@openaos.org>> On Wed, Dec 15, 2010 at 09:47:33AM -0800, Arjan van de Ven wrote: > On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: >> Now at least Nokia for the N900 provides a

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: Now at least Nokia for the N900 provides a much newer kernel for MeeGo, so those of us who own N900's are in good shape, but the conflict I'm trying to point out is real... and there will be a point where, even if you ignore the hard compliance top

Re: [MeeGo-dev] Comments on proposed kernel policy

On 12/14/2010 10:53 PM, Thomas B. Ruecker wrote: I don't see the difference between a vendor maintaining a kernel package and a community of people maintaining a kernel package Being involved in a relatively small OSS community around Archos portable media players I can tell you that it ma

Re: [MeeGo-dev] Comments on proposed kernel policy

On 12/14/2010 3:34 PM, Nishanth Menon wrote: a relatively current release will be chosen yes. Now "last formal" is a hard term; since 2.6.38 likely will be out before 1.2 ships, 2.6.37 is clearly not the last formal release at the time of ship. (but 2.6.38 will be out very shortly before 1.2 sh

Re: [MeeGo-dev] Comments on proposed kernel policy

On 12/14/2010 3:10 PM, Nishanth Menon wrote: Arjan van de Ven had written, on 12/14/2010 04:55 PM, the following: [...] 1. MeeGo will ship with one 'reference kernel', that will have one shared codebase between all the devices it supports (with different configuration files). This k

Re: [MeeGo-dev] Comments on proposed kernel policy

On 12/14/2010 2:38 PM, Nishanth Menon wrote: Carsten Munk had written, on 12/14/2010 03:45 PM, the following: btw, I think this discussion is better on meego-kernel ML. Just noticed that http://wiki.meego.com/Core_OS_Program/Kernel_policy Overall, meaning of upstream is confusing to me at le

Re: [MeeGo-dev] Comments on proposed kernel policy

On 12/14/2010 1:45 PM, Carsten Munk wrote: Hi, Just noticed that http://wiki.meego.com/Core_OS_Program/Kernel_policy came up and is on the agenda for TSG meeting tomorrow, so given that we have 24 hours to comment and I haven't seen it discussed in public, here's a couple of questions/comments f

Re: [MeeGo-dev] Using "meego" or similar in packages and distro names

On 12/14/2010 8:47 AM, Julian Andres Klode wrote: On Di, 2010-12-14 at 08:35 -0800, Arjan van de Ven wrote: On 12/14/2010 7:57 AM, quim@nokia.com wrote: Hi, let's see if we can move into specific details to find and fix whatever is problematic in this discussion about using anything

Re: [MeeGo-dev] Using "meego" or similar in packages and distro names

On 12/14/2010 7:57 AM, quim@nokia.com wrote: Hi, let's see if we can move into specific details to find and fix whatever is problematic in this discussion about using anything close to "meego" in packages and distro names. Can that discussion *PLEASE* move away from the development list

Re: [MeeGo-dev] [Pkg-meego-maintainers] Packaging the MeeGo stack on Debian - Use the name ?

On 12/10/2010 4:38 AM, Julian Andres Klode wrote: On Fr, 2010-12-10 at 11:24 +, MJ Ray wrote: Ibrahim Haddad wrote: We would ask you to move away from using {M,m}-e-e-{G,g}-o or any subset of those letters or sounds in that order, alone or in combination with other letters, words or marks t

Re: [MeeGo-dev] where can i get gles 1.0?

On 12/9/2010 6:35 PM, yunwuyu wrote: Hi, I'm working on meego and now i need the source code of gles, but i can only find gles 2.0 libs, would you please tell me where i can get gles 1.0's source code? Or, how can i get that? Anybody knows that? Thanks. meego needs gles 2.0... not 1.0

Re: [MeeGo-dev] about PPI / resolution settings

On 12/9/2010 6:40 AM, praveen pandey wrote: Hi, I am using a moorstown HW and picked up the handset mtf 1.1 image. Since my device's physical size and resolution is different(than the default handset image's), I have edited /etc/meegotouch/devices.conf for the resolution and PPI values. thi

Re: [MeeGo-dev] Qt uses OpenSSL, and fails?

On 12/8/2010 3:00 AM, fathi.bou...@nokia.com wrote: Hi, The fix is in MeeGo 1.1 but still not in Trunk. how on earth did that happen??? things are not allowed to go into 1.1 updates until the fix is in Trunk! ___ MeeGo-dev mailing list MeeGo-dev@m

Re: [MeeGo-dev] Qt uses OpenSSL, and fails?

On 12/8/2010 8:44 AM, Rémi Denis-Courmont wrote: - use GnuTLS or NSS instead of OpenSSL, we should be using NSS anyway wherever possible, not just for the licensing side, but also because openssl has a history of ABI mess. ___ MeeGo-dev mailing li

Re: [MeeGo-dev] Which component in MeeGo control the display brightness?

On 11/29/2010 11:44 PM, Zhao, Forrest wrote: Hi, Could you please give some light on which component in MeeGo control the display brightness? I'd like extend this component to respond to the proximity sensor event to adjust the display brightness accordingly. For example the display brightne

Re: [MeeGo-dev] Linking of X libraries in meego

Hi, I am facing some issues with linking of X libraries in meego. I have a test application in meegoouch-applauncherd that uses X libraries. The Linker flags -lX11 -lXtst -lXi have been added in the Cmake file. The build dependency for the package is also mentioned in the .yaml file. Pkg

Re: [MeeGo-dev] Error: failed to create image : Failed to find package 'syslinux' : No package(s) available to install

Hi Harsha, You need the right version of syslinux on your system. The best way to update your system is to download the package from http://repo.meego.com/MeeGo/tools/repos/ and build it. Choose your distribution accordingly e.g. for Ubuntu 10.04: http://repo.meego.com/MeeGo/tools/repos/ubunt

Re: [MeeGo-dev] Image creation failed: "Error: failed to create image : Failed mount disks : Fail to support file system btrfs"

On 11/22/2010 6:17 PM, nanjundiah.har...@elektrobit.com wrote: Intention is to build a custom image and boot the image on SD card. Am I on the right track? no since you're using the image format for one device, on the architecture of another that's clearly not going to work. __

Re: [MeeGo-dev] Image creation failed: "Error: failed to create image : Failed mount disks : Fail to support file system btrfs"

On 11/22/2010 5:52 PM, nanjundiah.har...@elektrobit.com wrote: sudo mic-image-creator --arch=armv7l --config=/home/harsha/workspace/image-creator-stable/image-creator/meego-handset-armv7l-n900-1.1.80.6.20101112.1.ks --format=mrstnand *Error: failed to create image : Failed mount disks : Fail

Re: [MeeGo-dev] Is this a bug or a feature?

On 11/13/2010 3:03 PM, Nasa wrote: Hi, As a end-user/hobbyst I was wondering where do items that don't fit "tested platforms" but meet the requirements for using Meego (say a home built machine using an intel platform) are suppose to be recorded? For example, a system using a standard monitor

Re: [MeeGo-dev] Handset UX rotation -- how is it implemented?

On 11/13/2010 11:59 AM, dhaval bc wrote: can it be done at kernel level itself... i mean to rotate the framebuffer itself and then calibrating the touch accordingly... is there any such option which we can specify in kernel commandline itelf (Intel based architecture)?? I remember one such opt

Re: [MeeGo-dev] Handset UX rotation -- how is it implemented?

On 11/13/2010 11:37 AM, Carsten Munk wrote: 2010/11/13 Arjan van de Ven: On 11/13/2010 11:29 AM, Javier wrote: I'm trying the Handset 1.1 final-demo images on my N900, and I've found that in both landscape and portrait modes, the X11 root window is 800x480 (that is, always portrait)

Re: [MeeGo-dev] Handset UX rotation -- how is it implemented?

On 11/13/2010 11:29 AM, Javier wrote: I'm trying the Handset 1.1 final-demo images on my N900, and I've found that in both landscape and portrait modes, the X11 root window is 800x480 (that is, always portrait). However, Qt applications (for example duicontrolpanel) render just fine in portrait.

Re: [MeeGo-dev] QWidget::showEvent might be helpful for apps wanting to know if they should keep drawing.

On 11/12/2010 4:42 PM, Yung, Winson W wrote: If there's any way that the WM knows this, let's make sure it sends an event. Let's even extend EWMH with this event. Then Qt and any other toolkit can send the appropriate event. Forget Symbian at this point. People here in MeeGo don't have to worry

Re: [MeeGo-dev] QWidget::showEvent might be helpful for apps wanting to know if they should keep drawing.

On 11/12/2010 11:05 AM, Thiago Macieira wrote: t it. QEvent::WindowActivate is used on X11, however. It's sent in response to an XFocusIn or EnterNotify events. Its counterpart (QEvent::WindowDeactivate) is sent to windows when XFocusOut and LeaveNotify are received as well as when XFocusIn and E

Re: [MeeGo-dev] audio and video codecs

On 11/10/2010 3:26 PM, Mark S. Townsley wrote: Hi: Is there a default list of audio and video codecs that come with MeeGo core? we pretty much ship all of those that do not require licensing contracts/deals... ___ MeeGo-dev mailing list MeeGo-de

Re: [MeeGo-dev] /proc/version

On 11/10/2010 8:19 AM, Mark S. Townsley wrote: Hi: I like a way to find out the meego version from within my code. When I look at /proc/version on my MeeGo 1.1 netbook installation, it says (MeeGo 4.5.0-1).How do I usually translate that number to the actual MeeGo version? Is there anot

Re: [MeeGo-dev] Coding guidelines doc

On 11/10/2010 2:13 AM, Thilaga wrote: Hi All, Is there any Meego Coding guidelines document. meego contains many open source projects in general we expect you to follow the guidelines for the projects you are working on, if such an existing project exists (for example, for the kernel we requi

Re: [MeeGo-dev] How application can get display off event?

On 11/9/2010 12:36 PM, Yung, Winson W wrote: Hey Arjan, I am not sure I can use the same event for detecting display off. Let's say I wrote an analog clock MeeGo application, and it is running in the foreground. When display is off, the analog clock should not attempt to update UI. correct.

Re: [MeeGo-dev] How application can get display off event?

On 11/9/2010 12:16 PM, Yung, Winson W wrote: Hi all, I posted the following question to MeeGo’s application developer forum , but didn’t get any response/suggestion. I am wondering folks here have any insight on this or not: In the case when disp

Re: [MeeGo-dev] wayland display server in MeeGo?

On 11/4/2010 9:58 PM, Nishanth Menon wrote: Arjan van de Ven wrote, on 11/04/2010 09:39 PM: On 11/4/2010 9:00 PM, Nishanth Menon wrote: Hi Folks, Wondering in what way we use Wayland in MeeGo - is this part of the plan of MeeGo 1.2? As per [1] we'd potentially be using this? Checking goog

Re: [MeeGo-dev] wayland display server in MeeGo?

On 11/4/2010 9:00 PM, Nishanth Menon wrote: Hi Folks, Wondering in what way we use Wayland in MeeGo - is this part of the plan of MeeGo 1.2? As per [1] we'd potentially be using this? Checking google, I came across [3] discussed some time back, but I guess "in development" does'nt mean we are

Re: [MeeGo-dev] MeeGo modules autoload?

On 10/31/2010 4:01 AM, Tomasz Sterna wrote: Is there a MeeGo way to autoload a set of modules on boot? udev will load all enumerated devices automatically. is that not working for you? is your kernel missing exposing the firmware enumeration to userspace properly? ___

Re: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo

On 10/28/2010 6:10 PM, Sivan Greenberg wrote: Re reading about MeeGo's architecture, is Geoclue the engine or the "backend" for Qt's Mobility location and positioning APIs? If not, what is the relationship ? geoclue is the reference back end. Geoclue however is not a manadatory component. I

Re: [MeeGo-dev] ARMv7 hardfp port of MeeGo discussion

On 10/26/2010 12:18 PM, Quim Gil wrote: On Mon, 2010-10-25 at 23:52 +0200, ext Thiago Macieira wrote: This is why I was wondering why we're not using hardfp *now* for 1.1.0. We shouldn't be breaking binary compatibility. We shouldn't be softp either. Just reminding the obvious, but as for tod

Re: [MeeGo-dev] ARMv7 hardfp port of MeeGo discussion (Was: Re: new draft of MeeGo compliance specification)

On 10/25/2010 2:33 PM, harri.hakuli...@nokia.com wrote: From: Arjan van de Ven [ar...@linux.intel.com] Sent: Monday, October 25, 2010 4:59 PM On 10/25/2010 4:06 AM, jarmo.k...@nokia.com wrote: Hi, We have discussed about hardfp (and other) support in

Re: [MeeGo-dev] kernel: CONFIG_X86_ACPI_CPUFREQ performance issues

On 10/25/2010 1:11 PM, Gabriel M. Beddingfield wrote: On Mon, 25 Oct 2010, Auke Kok wrote: IOW just provide a README that says that the application requires all the power savings features to be turned off, which is what you realistically want. There's no way to give you what you want witho

Re: [MeeGo-dev] kernel: CONFIG_X86_ACPI_CPUFREQ performance issues

On 10/25/2010 10:22 AM, Gabriel M. Beddingfield wrote: Anybody know how to configure the speed profile (swich from "on demand" to "performance"?) that's normally a bad idea. your bug report is rather vague can you be more detailed on which meego you are using, give us "powertop -d" outpu

Re: [MeeGo-dev] ARMv7 hardfp port of MeeGo discussion (Was: Re: new draft of MeeGo compliance specification)

On 10/25/2010 4:06 AM, jarmo.k...@nokia.com wrote: Hi, We have discussed about hardfp (and other) support in the toolchain team. Current assumption is that hardfp will be used in MeeGo 1.2. But there are still quite many other things to be agreed also - regarding different compiler options an

Re: [MeeGo-dev] kernel: CONFIG_X86_ACPI_CPUFREQ performance issues

On 10/24/2010 8:39 PM, Gabriel M. Beddingfield wrote: Hello, When doing processor intesive calculations (e.g. synthesizing audio) I've found that the kernel option CONFIG_X86_ACPI_CPUFREQ causes a big performance drop when it's enabled. Any ideas why this is? is your calculation running "nice

<    1   2   3   4   5   >