Re: [MeeGo-dev] Dose anyone run Meego of N900 image in QEMU successfully?
On (22:27 12/07/10), Tom Chen fun...@gmail.com put forth the proposition: Hi, Could some Nokia guys give some good docs for how to build and run N900 image with Qemu? it looks a little docs about N900. I'd also like some info on how to add some extra space so it's possible to install dev packages. I've tried all the ways I can think of but nothing seems to work. Br Tom Chen On Mon, Jul 12, 2010 at 9:51 AM, Andrew Savory me...@andrewsavory.comwrote: Hi, On 7 July 2010 09:23, Tom Chen fun...@gmail.com wrote: Hi, i agree with your point for - PLEASE READ THE WIKI CAREFULLY --, but i think the wiki is not so good for new guy, like me. actual, i had yum install SDL before, but the system said it's already existed. so, i don't know i need install other packages, like SDL-devel. i think your means yum install SDL-devel, not libsdl-dev in Fedora. maybe libsdl-dev used in Ubuntu. Yes, libsdl-dev on ubuntu. Since Fedora 12 seems to be the preferred dev platform, I've tweaked the name of the package on http://wiki.meego.com/ARM/Meego_on_Qemu to be SDL-devel. If anyone knows the correct name for all the packages on Ubuntu and Fedora, please go ahead and fix that page! Thanks Andrew. -- asav...@apache.org / cont...@andrewsavory.com http://www.andrewsavory.com/ ___ 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 -- Don't look back, the lemmings are gaining on you. pgpoY5smx2yTw.pgp Description: PGP signature ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Simulator events
On Wednesday 14. July 2010 06.42.24 Vincent Yau wrote: Dear All: Is there a way to simulate certain kinds of user events inside Meego Simulator that comes with the SDK? One example of events I want to simulate is the touch events on a touch-screen. Is there such a way to generate that kind of events inside the Simulator? A single-touch event is no different than a mouse event. So just click wherever you want the touch to happen. A touch with multiple fingers, however, is more complicated. I don't think there's any way to simulate that. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Beagleboard kernel config / sgx setup?
On Wed, 2010-07-14 at 09:54 +0300, Ameya Palande wrote: Hi Amit, On Wed, 2010-07-14 at 07:23 +0200, ext Amit Pundir wrote: On Wed, Jul 14, 2010 at 9:12 AM, vijay singh testmrs@gmail.com wrote: On Tue, 2010-07-13 at 18:35 +0530, Amit Pundir wrote: On Fri, Jul 9, 2010 at 11:50 PM, Till Harbaum / Lists li...@harbaum.org wrote: Hi, Am Donnerstag 08 Juli 2010 schrieb William Mills: This is an excellent page! Much better than the piece meal stuff we had before. Thanks. Hopefully somebody will make use of it. Hi, Today is my first day @Meego, so my questions may sound stupid.. though I have worked on Beagleboard/Openembedded before. I'm facing some issues while building Beagleboard rootfs image. I'm following the instructions on this page: http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch Am I suppose to set-up and run those instructions in a Scratchbox like environment? If answer is yes then that is the cause of my problem because I have not set-up any such environment. If answer is no then here is my set-up: I'm running Ubuntu-9.10 on my host machine. I have installed the necessary packages as mentioned here: http://wiki.meego.com/Image_Creation#Requirements and running the latest development version of mic-image-creator from here: http://wiki.meego.com/Image_Creation#From_Development_Git_Tree After all this set-up, I decided to give it a shot but I got the following error: -- $ sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=fs --arch=armv7l --config=../meego-handset-armv7l-beagle-1.0.80.8.20100630.ks [main] use_comps=1 default_ks=default.ks cachedir=/var/tmp/cache distro_name=MeeGo image_format=livecd tmpdir=/var/tmp outdir=. Run mode: legacy Geting repomd.xml from repo handset... Getting primary.sqlite from repo handset... Getting patterns repodata/77c704dfd2ab7342491f74496c6c92c7d4fa07f0e7caa3c217c7a2c559e63374-patterns.xml.gz from repo handset... Getting comps repodata/87659030459ca748c117946801759b1e912033be1478c6584633f1621a8f588f-comps.xml.gz from repo handset... Geting repomd.xml from repo MeeGo-Trunk... Getting primary.sqlite from repo MeeGo-Trunk... Getting patterns repodata/faeb6b4db83441a1a80a162a29198bc39594f5bc937f2436b4752adbe77e5ad3-patterns.xml.gz from repo MeeGo-Trunk... [u'armv7l'] MeeGo release 1.0.80 Target arch: armv7l Traceback (most recent call last): File /usr/bin/mic-image-creator, line 806, in module ret = main() File /usr/bin/mic-image-creator, line 753, in main creator.install() File /usr/lib/python2.6/dist-packages/mic/imgcreate/creator.py, line 746, in install ayum = LiveCDYum(self._recording_pkgs, target_arch = self.target_arch) File /usr/lib/python2.6/dist-packages/mic/imgcreate/yuminst.py, line 50, in __init__ self.arch.setup_arch(target_arch) AttributeError: 'LiveCDYum' object has no attribute 'arch' -- Kindly let me know what am I doing wrong here. Thanks for your concern. regards, Amit Pundir Till: You also seem to be running on 10.04. Do you see the following error after the mic-image-creator step: Yes, i have also been ignoring it. But now that you mention it i remember that i wanted to add this to the wiki page, so people following my instructions don't get irritated by this. Is the new beagleboard available in germany already? The 128MB RAM of the original one seem to be critical and i'd like to give the new one a test and see whether the gui loads faster. Till Did you install all the depedency (check at below page) : //http://wiki.meego.com/Image_Creation#Installation Yes I did and also confirmed it by running the following command as mentioned in the wiki page: -- $ sudo ./tools/mic-check-alldeps Checking autoconf... autoconf installed . Checking version of squashfs-tools...OK You are ready for running Image Creator!!! -- I followed the same page, and could create rootfs for beagle board successfully. My host OS is Ubuntu 10.04 x86-32 Cheers, Ameya. For me it also working. same configuration. Regards, Vij ___ 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] Beagleboard kernel config / sgx setup?
On Wed, Jul 14, 2010 at 1:14 PM, vijay singh testmrs@gmail.com wrote: On Wed, 2010-07-14 at 09:54 +0300, Ameya Palande wrote: Hi Amit, On Wed, 2010-07-14 at 07:23 +0200, ext Amit Pundir wrote: On Wed, Jul 14, 2010 at 9:12 AM, vijay singh testmrs@gmail.com wrote: On Tue, 2010-07-13 at 18:35 +0530, Amit Pundir wrote: On Fri, Jul 9, 2010 at 11:50 PM, Till Harbaum / Lists li...@harbaum.org wrote: Hi, Am Donnerstag 08 Juli 2010 schrieb William Mills: This is an excellent page! Much better than the piece meal stuff we had before. Thanks. Hopefully somebody will make use of it. Hi, Today is my first day @Meego, so my questions may sound stupid.. though I have worked on Beagleboard/Openembedded before. I'm facing some issues while building Beagleboard rootfs image. I'm following the instructions on this page: http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch Am I suppose to set-up and run those instructions in a Scratchbox like environment? If answer is yes then that is the cause of my problem because I have not set-up any such environment. If answer is no then here is my set-up: I'm running Ubuntu-9.10 on my host machine. I have installed the necessary packages as mentioned here: http://wiki.meego.com/Image_Creation#Requirements and running the latest development version of mic-image-creator from here: http://wiki.meego.com/Image_Creation#From_Development_Git_Tree After all this set-up, I decided to give it a shot but I got the following error: -- $ sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=fs --arch=armv7l --config=../meego-handset-armv7l-beagle-1.0.80.8.20100630.ks [main] use_comps=1 default_ks=default.ks cachedir=/var/tmp/cache distro_name=MeeGo image_format=livecd tmpdir=/var/tmp outdir=. Run mode: legacy Geting repomd.xml from repo handset... Getting primary.sqlite from repo handset... Getting patterns repodata/77c704dfd2ab7342491f74496c6c92c7d4fa07f0e7caa3c217c7a2c559e63374-patterns.xml.gz from repo handset... Getting comps repodata/87659030459ca748c117946801759b1e912033be1478c6584633f1621a8f588f-comps.xml.gz from repo handset... Geting repomd.xml from repo MeeGo-Trunk... Getting primary.sqlite from repo MeeGo-Trunk... Getting patterns repodata/faeb6b4db83441a1a80a162a29198bc39594f5bc937f2436b4752adbe77e5ad3-patterns.xml.gz from repo MeeGo-Trunk... [u'armv7l'] MeeGo release 1.0.80 Target arch: armv7l Traceback (most recent call last): File /usr/bin/mic-image-creator, line 806, in module ret = main() File /usr/bin/mic-image-creator, line 753, in main creator.install() File /usr/lib/python2.6/dist-packages/mic/imgcreate/creator.py, line 746, in install ayum = LiveCDYum(self._recording_pkgs, target_arch = self.target_arch) File /usr/lib/python2.6/dist-packages/mic/imgcreate/yuminst.py, line 50, in __init__ self.arch.setup_arch(target_arch) AttributeError: 'LiveCDYum' object has no attribute 'arch' -- Kindly let me know what am I doing wrong here. Thanks for your concern. regards, Amit Pundir Till: You also seem to be running on 10.04. Do you see the following error after the mic-image-creator step: Yes, i have also been ignoring it. But now that you mention it i remember that i wanted to add this to the wiki page, so people following my instructions don't get irritated by this. Is the new beagleboard available in germany already? The 128MB RAM of the original one seem to be critical and i'd like to give the new one a test and see whether the gui loads faster. Till Did you install all the depedency (check at below page) : //http://wiki.meego.com/Image_Creation#Installation Yes I did and also confirmed it by running the following command as mentioned in the wiki page: -- $ sudo ./tools/mic-check-alldeps Checking autoconf... autoconf installed . Checking version of squashfs-tools...OK You are ready for running Image Creator!!! -- I followed the same page, and could create rootfs for beagle board successfully. My host OS is Ubuntu 10.04 x86-32 Cheers, Ameya. For me it also working. same configuration. Regards, Vij Looks like I need to try it on Ubuntu-10.04. Will let you know the result. Thanks a lot for feedback. regards, Amit Pundir ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev
[MeeGo-dev] [Connman] [N900]: Very flaky connman behaviour regarding wifi, debug log linked
We are experiencing very flaky wifi on the N900 and wlan0 seems to work fine with standard wireless-tools and wpa_supplicant etc. But not with connman (0.54 from trunk + fix for BMC#3807, which made connman extremely flaky with SIGSEGVs.) I have implemented a testcase which runs at startup: * In rc.sysinit, rm -rf /var/lib/connman/default.profile to ensure a clean slate. Patch for BMC#3807 is included in connman binary. * In rc.sysinit, run connmand -n -d '*' /connman.debug * In rc.sysinit, disable ofonod, bluetoothd and Nokia N900 usb networking as to not interfere * After 60 seconds, run /usr/lib/connman/test/test-manager * Check output for /org/moblin/connman/technology/wifi which would indicate wifi technology being available, indicate date/time + PASS/FAIL in log * Dump /var/log/messages, /var/log/debug and /connman.debug into log * Reboot, try again. In one run, wifi only appeared 6 out of 16 times which is considered slightly flaky in my books. I haven't verified if the same issue happens on other hardware configurations, but it might. At http://stskeeps.subnetmask.net/meego/connman-14jul2010.log you can download my test log, there's a good number of FAIL cases and some PASS cases to look at. It would be great if you connman guys (or anyone else) could come with theories on why this is so flaky, it would be fantastic as this is keeping us from a usable image on N900. Best regards, Carsten Munk Acting N900 hardware adaptation maintainer (while Harri's on vacation) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [Connman] [N900]: Very flaky connman behaviour regarding wifi, debug log linked
Hi Carsten, We are experiencing very flaky wifi on the N900 and wlan0 seems to work fine with standard wireless-tools and wpa_supplicant etc. But not with connman (0.54 from trunk + fix for BMC#3807, which made connman extremely flaky with SIGSEGVs.) I have implemented a testcase which runs at startup: * In rc.sysinit, rm -rf /var/lib/connman/default.profile to ensure a clean slate. Patch for BMC#3807 is included in connman binary. * In rc.sysinit, run connmand -n -d '*' /connman.debug * In rc.sysinit, disable ofonod, bluetoothd and Nokia N900 usb networking as to not interfere * After 60 seconds, run /usr/lib/connman/test/test-manager * Check output for /org/moblin/connman/technology/wifi which would indicate wifi technology being available, indicate date/time + PASS/FAIL in log * Dump /var/log/messages, /var/log/debug and /connman.debug into log * Reboot, try again. In one run, wifi only appeared 6 out of 16 times which is considered slightly flaky in my books. I haven't verified if the same issue happens on other hardware configurations, but it might. At http://stskeeps.subnetmask.net/meego/connman-14jul2010.log you can download my test log, there's a good number of FAIL cases and some PASS cases to look at. It would be great if you connman guys (or anyone else) could come with theories on why this is so flaky, it would be fantastic as this is keeping us from a usable image on N900. my experience with TI WiFi hardware is actually limited, but one clear thing I see here is this one: connmand[519]: Failed to open RFKILL control device connmand[519]: Enabling udev based RFKILL processing I have no idea why the kernel is compiled without CONFIG_RFKILL support or why udev might be not creating /dev/rfkill properly. The udev based RFKILL processing is racy and we did actually remove it lately. And a 2.6.35-rc4 clearly has /dev/rfkill support. A MeeGo kernel should always have CONFIG_RFKILL enabled. Maybe that helps already. Regards Marcel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Beagleboard support HDMI or TV/Out?
On Jul 13, 2010, at 22:38, Cristopherson Torres Martinez wrote: Hi, I have been able to boot Meego on a Beagle C2 using either of the following instructions. Can you get your hands on a later version of the Beagle board? The C4 for example has DVI-D output which you can use with a DVI-D to HDMI cable for output on a TV. Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] QA guys: Wiki clutter?
Hi, Zhao, Fan wrote: Agree, and all handset test reports have been restructured like: http://wiki.meego.com/Quality/HandsetTestReport/UXWeekly20100706 Thanks! Would it bother you to avoid the extra subpage level and just use http://wiki.meego.com/Quality/UX weekly report 20100706 please? Also, if you wouldn't mind using Handset test report instead of HandsetTestReport, your page names will be consistent with the rest of the wiki. Thanks! Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] QA guys: Wiki clutter?
Hello Bill, Whoever admins the mediawiki install may want to have a look at: http://www.mediawiki.org/wiki/Subpages Subpages are enabled already. Elliot -- Elliot Smith Intel Open Source Technology Centre - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] mcompositor X11 requirements/limitations
On Wed, 2010-07-14 at 00:38 +0200, ext Robin Burchell wrote: Hi Eugene, Excerpts from Eugene Seah's message of Tue Jul 13 23:33:25 +0100 2010: Hi there, I'm trying to get the UX working on another ARM device that does not have the same SGX graphics chip that the N900/Beagleboard have. What's limiting the UX/mcompositor from working with non-hw accelerated X11? MCompositor requires a GLX/EGL backend to do rendering. I briefly (5 mins) looked into whether a software backend would be possible, as GLX/EGL backends are thankfully fairly seperated from everything else, but I didn't really reach a conclusion. It may be possible (if slow). That's right. You could write a new backend for mcompositor, using QGraphicsView or Mesa-like library for software rendering. MCompositor works this way as it composites thumbnails of running applications or something along these lines. I haven't worked out precisely what it does as I haven't had the time to sit down and actually get it running. ;) Hardware acceleration is needed for speed, of course. And we can also avoid making a copy of the application window contents for compositing with some server-side buffer magic. -Kimmo The rest of the UX is usable without GL, as libmeegotouch does not require it - with newest libmeegotouch from master (I'm not sure if it's updated in MeeGo yet), you have a patch by me which looks for the environment variable M_USE_SOFTWARE_RENDERING to use software rendering, or alternatively, you can run applications and pass -software as a parameter. Thanks. Hope this helps, -- Robin Burchell http://rburchell.com ___ 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] mcompositor X11 requirements/limitations
On Wed, 2010-07-14 at 02:55 +0200, ext Robin Burchell wrote: Hi, ... So, you may need to swap a new window manager in (or look at writing a s/w rendering backend), but apart from that, the rest of the stack should work OK if told to use software rendering mode. Applications don't rely on the compositor to render them. Normal applications don't but we have some custom things for Meegotouch applications, like synthetic VisibilityNotify sending from mcompositor. Also some additional window properties to handle the decorator logic (Meegotouch applications decorate themselves, and for others we have an external decorator [mdecorator] window). Iconified state is used for the task switcher but not in a traditional way (we use the main window instead of a icon window). -Kimmo Now, let's go semi-theoretical: I've not actually had a chance to play with a finished MeeGo handset stack yet as I don't have an SD card to flash to use on my n900 - this is all just from looking at meego.gitorious.org and what I know already.. To actually launch an application, let's say meego-handset-dialer, fire up X, and run meego-handset-dialer -software from a terminal, and it should work - hopefully. The same process *should* apply for homescreen given what I believe, but I've CC'd in Carsten Munk who has done some solid work at applying the above sort of stuff on the unofficial N8x0 adaptation. Carsten, have I missed anything here? -- Robin Burchell http://rburchell.com ___ 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
[MeeGo-dev] Suggestions to Meego site Administrators / Developers
1) Why Meego Project does not provide alternative downloads by Bittorrent protocol ? The way to download Meego now is *amazingly SLOW* and unreliable; using BitTorrent protocol would be better for data integrity and speed. 2) Please update the page for downloading Meego with Chrome browser ( http://goo.gl/9uAp ), it needs a MD5 sum: field like the page without Chrome browser( http://goo.gl/zNFg ) 3) Please add links to the md5sum at http://goo.gl/9IVZ , and write something there to make it easier for everybody to verify the integrity of the .img file. The location of that .md5sum file is IMO **obscure**. I searched for it more than 10 minutes after finally discovered the magic place http://goo.gl/F0GO (I later discovered it on the Meego for Netbooks page, i.e. the one without Chrome) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [Connman] [N900]: Very flaky connman behaviour regarding wifi, debug log linked
On Jul 14, 2010, at 2:16 AM, Changming Sun wrote: Sorry,where can I found some document for connman? It's rare. You can get more information, source code, recent release, etc. here: http://connman.net/ Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Simulator events
On Jul 13, 2010, at 9:42 PM, Vincent Yau wrote: Dear All: Is there a way to simulate certain kinds of user events inside Meego Simulator that comes with the SDK? One example of events I want to simulate is the touch events on a touch-screen. Just a quick reminder that questions about the SDK or application development should be posted to the meego-sdk mailing list, instead of meego-dev. http://lists.meego.com/listinfo/meego-sdk Regards, Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Zypper, Yum, and private repositories
Hi all, I'm adding a private RPM repository to a MeeGo install with our own apps. By looking at the system, there are Yum definitions in /etc/yum.repos.d/ and there are Zypper definitions in /etc/zypper/repos.d/ In order to integrate the repo definitions as smooth as possible and having the standard tools popup a notification when updates are available, where should I add the repo definitions? in Yum configuration? in Zypper configuration? both? Many thanks in advance. saludos daniel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] [PATCH 3/3] kernel-source: Remove duplicates from config-ivi
Signed-off-by: Ameya Palande ameya.pala...@nokia.com --- config-ivi |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/config-ivi b/config-ivi index 4d6f0d3..59981bb 100644 --- a/config-ivi +++ b/config-ivi @@ -142,8 +142,6 @@ CONFIG_SATA_SIL24=y CONFIG_MTD_CONCAT=y CONFIG_MTD_PARTITIONS=y # CONFIG_MTD_TESTS is not set -# CONFIG_MTD_BLOCK_RO is not set -# CONFIG_MTD_OOPS is not set # CONFIG_MTD_CFI is not set # CONFIG_MTD_JEDECPROBE is not set # CONFIG_MTD_RAM is not set -- 1.7.0.4 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] [PATCH 1/3] kernel-source: Remove duplicates from config-generic
Signed-off-by: Ameya Palande ameya.pala...@nokia.com --- config-generic | 13 - 1 files changed, 0 insertions(+), 13 deletions(-) diff --git a/config-generic b/config-generic index 92a1c69..3122828 100644 --- a/config-generic +++ b/config-generic @@ -1836,13 +1836,6 @@ CONFIG_VIDEO_OUTPUT_CONTROL=y CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB_TRIDENT_ACCEL is not set -# CONFIG_FB_ARK is not set -# CONFIG_FB_PM3 is not set -# CONFIG_FB_CARMINE is not set -# CONFIG_FB_GEODE is not set -# CONFIG_FB_VIRTUAL is not set -# CONFIG_FB_METRONOME is not set -# CONFIG_FB_MB862XX is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y @@ -2955,8 +2948,6 @@ CONFIG_CHECK_SIGNATURE=y # CONFIG_MSTWN_POWER_MGMT is not set # CONFIG_USB_NET_MBM is not set -# CONFIG_USB_GADGET_LANGWELL is not set -# CONFIG_USB_LANGWELL is not set # CONFIG_USB_MRSTN_GADGET is not set # CONFIG_INTEL_LNW_DMAC1 is not set @@ -3167,7 +3158,6 @@ CONFIG_USB_GSPCA_SN9C20X_EVDEV=y # CONFIG_RCU_FANOUT_EXACT is not set CONFIG_PERF_EVENTS=y # CONFIG_DEBUG_PERF_USE_VMALLOC is not set -# CONFIG_OPROFILE_EVENT_MULTIPLEX is not set CONFIG_KSM=y # CONFIG_MEMORY_FAILURE is not set CONFIG_PM_RUNTIME=y @@ -3319,7 +3309,6 @@ CONFIG_PM_ADVANCED_DEBUG=y # CONFIG_EEEPC_WMI is not set # CONFIG_VHOST_NET is not set # CONFIG_VIDEO_TLG2300 is not set -# CONFIG_VMWARE_BALLOON is not set CONFIG_USB_IPHETH=m CONFIG_USB_SIERRA_NET=m # CONFIG_HMC6352 is not set @@ -3410,7 +3399,6 @@ CONFIG_TOUCHSCREEN_TPS6507X=m CONFIG_INPUT_AD714X_I2C=m CONFIG_INPUT_AD714X_SPI=m CONFIG_GPIO_JANZ_TTL=m -# CONFIG_MFD_TC35892 is not set # CONFIG_VIDEO_MEM2MEM_TESTDEV is not set # CONFIG_FB_TMIO is not set # CONFIG_VIDEO_TM6000_ALSA is not set @@ -3485,7 +3473,6 @@ CONFIG_PVR_SUPPORT_CPU_CACHED_BUFFERS=y CONFIG_CROSS_COMPILE= # CONFIG_FB_XGI is not set -# CONFIG_HW_RANDOM_TIMERIOMEM is not set # CONFIG_ISL29020 is not set # CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set # CONFIG_BT_HCIH4P is not set -- 1.7.0.4 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] [PATCH 2/3] kernel-source: Remove duplicates from config-mrst
Signed-off-by: Ameya Palande ameya.pala...@nokia.com --- config-mrst |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/config-mrst b/config-mrst index 984c4da..735c08c 100644 --- a/config-mrst +++ b/config-mrst @@ -26,8 +26,6 @@ CONFIG_USB_GADGET=y CONFIG_USB_GADGET_VBUS_DRAW=2 CONFIG_USB_GADGET_SELECTED=y CONFIG_USB_GADGET_LANGWELL=y -CONFIG_USB_GADGET_LANGWELL=y -CONFIG_USB_LANGWELL=y CONFIG_USB_LANGWELL=y CONFIG_USB_GADGET_DUALSPEED=y CONFIG_USB_STILL_IMAGE=y -- 1.7.0.4 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] [PATCH 0/3] kernel-source: Remove duplicates from config files
These patches are genereated against devel:kernel kernel pacakge in OBS. Ameya Palande (3): kernel-source: Remove duplicates from config-generic kernel-source: Remove duplicates from config-mrst kernel-source: Remove duplicates from config-ivi config-generic | 13 - config-ivi |2 -- config-mrst|2 -- 3 files changed, 0 insertions(+), 17 deletions(-) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Suggestions to Meego site Administrators / Developers
On 07/14/10 06:44, Alex Butum wrote: 1) Why Meego Project does not provide alternative downloads by Bittorrent protocol ? The way to download Meego now is *amazingly SLOW* and unreliable; using BitTorrent protocol would be better for data integrity and speed. We have discussed using alternate methods, including frontend hosting on akamai/amazon cloud (like we do now for official releases) and using bittorrent. For now we're still investigating BitTorrent, so no clear answer on that. 2) Please update the page for downloading Meego with Chrome browser ( http://goo.gl/9uAp ), it needs a MD5 sum: field like the page without Chrome browser( http://goo.gl/zNFg ) 3) Please add links to the md5sum at http://goo.gl/9IVZ , and write something there to make it easier for everybody to verify the integrity of the .img file. The location of that .md5sum file is IMO *obscure*. I searched for it more than 10 minutes after finally discovered the magic place http://goo.gl/F0GO (I later discovered it on the Meego for Netbooks page, i.e. the one without Chrome) this should be fixed I think, we can certainly add inobtrusive md5sum links in the release notes. Auke ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Suggestions to Meego site Administrators / Developers
On Jul 14, 2010, at 1:06 PM, Auke Kok wrote: 2) Please update the page for downloading Meego with Chrome browser ( http://goo.gl/9uAp ), it needs a MD5 sum: field like the page without Chrome browser( http://goo.gl/zNFg ) 3) Please add links to the md5sum at http://goo.gl/9IVZ , and write something there to make it easier for everybody to verify the integrity of the .img file. The location of that .md5sum file is IMO *obscure*. I searched for it more than 10 minutes after finally discovered the magic place http://goo.gl/F0GO (I later discovered it on the Meego for Netbooks page, i.e. the one without Chrome) this should be fixed I think, we can certainly add inobtrusive md5sum links in the release notes. We should definitely have the checksums in a place where normal human beings can find them without excessive digging. I've filed a bug for this request: http://bugs.meego.com/show_bug.cgi?id=3871 Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Simulator events
Dnia 2010-07-14, śro o godzinie 08:56 -0400, Bernd Stramm pisze: On Wed, 14 Jul 2010 08:52:07 +0200 Thiago Macieira thi...@kde.org wrote: Is there such a way to generate that kind of events inside the Simulator? A single-touch event is no different than a mouse event. So just click wherever you want the touch to happen. A touch with multiple fingers, however, is more complicated. I don't think there's any way to simulate that. Does anyone happen to know how to do touch events from touch pads on laptops? They come in as mouse events and wheel events. Probably some layer is doing hard work to hide the actual touch events and translate them into mouse and wheel stuff, before it gets into Qt. During recent Ubuntu Summit there were some discussions about (multi)-touch solutions. I was not there, but from IRC and streams it seemed that there was consensus on using evdev with support from UI libraries/toolkits. I was not there (only remotely participating) so do not have much details. https://wiki.ubuntu.com/X/Blueprints/Touchscreen/UDS-M https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-multi-touch-and-kernel -- Tomasz Rybak bogom...@post.pl GPG/PGP key ID: 2AD5 9860 Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860 http://member.acm.org/~tomaszrybak signature.asc Description: This is a digitally signed message part ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Community OBS looking for beta testers
Quick follow up... Due to the stunning download speed (50kbs) from the meego repos it took more than my allotted sunday to get the repos for :current in place. Then we had a couple of minor issues to fix. However, it now appears that building against :1.0 and :current work. Let us know as you find issues. David -- Don't worry, you'll be fine; I saw it work in a cartoon once... ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [Connman] [N900]: Very flaky connman behaviour regarding wifi, debug log linked
On 14/07/10 7:16 PM, ext Changming Sun wrote: Sorry,where can I found some document for connman? It's rare. Documentation are text files in the source code under doc/ -- Lorn 'ljp' Potter Senior Software Engineer, Nokia, Qt Development Frameworks ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Zypper, Yum, and private repositories
Hi daniel, If you just use zypper, then put your xxx.repo in /etc/zypper/repos.d/; If you just use yum, then put your xxx.repo in /etc/yum.repos.d; If you want to release your repo, then just do what meego-release do. 在 2010-07-14三的 11:41 -0300，Valfre, Daniel写道： Hi all, I'm adding a private RPM repository to a MeeGo install with our own apps. By looking at the system, there are Yum definitions in /etc/yum.repos.d/ and there are Zypper definitions in /etc/zypper/repos.d/ In order to integrate the repo definitions as smooth as possible and having the standard tools popup a notification when updates are available, where should I add the repo definitions? in Yum configuration? in Zypper configuration? both? Many thanks in advance. saludos daniel ___ 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] Zypper, Yum, and private repositories
I'll use zypper.. and simply ignore yum. On Thu, Jul 15, 2010 at 9:27 AM, An Yang an.eurof...@gmail.com wrote: Hi daniel, If you just use zypper, then put your xxx.repo in /etc/zypper/repos.d/; If you just use yum, then put your xxx.repo in /etc/yum.repos.d; If you want to release your repo, then just do what meego-release do. 在 2010-07-14三的 11:41 -0300，Valfre, Daniel写道： Hi all, I'm adding a private RPM repository to a MeeGo install with our own apps. By looking at the system, there are Yum definitions in /etc/yum.repos.d/ and there are Zypper definitions in /etc/zypper/repos.d/ In order to integrate the repo definitions as smooth as possible and having the standard tools popup a notification when updates are available, where should I add the repo definitions? in Yum configuration? in Zypper configuration? both? Many thanks in advance. saludos daniel ___ 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 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
