[MeeGo-dev] GStreamer Open MAX IL and codec support
Hi, could anyone clarify the status regarding Open MAX IL and codec support for GStreamer in Meego? http://meego.gitorious.org/maemo-multimedia/gst-openmax/blobs/master/README indicates that you should be able to use (even DSP) implementations of codecs such as h.264 via the Open MAX IL plug-in. However, issuing the #gst-inspect-0.10 command on a Meego Netbook 1.0 device (Asus Eee 1008) it seems there is no h.264 (or even Open MAX IL) support. If anyone could provide some info I would be grateful! --Stefan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] PyQt
I am looking at developing for MeeGo and I know C/C++ is one choice. Is it possible to develop MeeGo application using Python/PyQt? There's 2 Python binding for Qt implementation: - PyQt (RiverBank) - PySide At the moment, MeeGo doesn't have Python binding for Qt packages. I expect we'll have them at some point. Cheers, Fathi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] PyQt
Hi, If you want the PySide bindings which are supposed to be a better, more complete version of the original Qt bindings, Please, don't spread FUD but give facts. We have 2 competitors for the Python bindings. Both have pros/cons and both try to push their implementation. I let the reader to search the relevant information to make his own choice. Cheers, Fathi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] GStreamer Open MAX IL and codec support
Hi, On Mon, Jul 26, 2010 at 9:17 AM, stefan hakansson stef...@gmail.com wrote: could anyone clarify the status regarding Open MAX IL and codec support for GStreamer in Meego? http://meego.gitorious.org/maemo-multimedia/gst-openmax/blobs/master/README indicates that you should be able to use (even DSP) implementations of codecs such as h.264 via the Open MAX IL plug-in. However, issuing the #gst-inspect-0.10 command on a Meego Netbook 1.0 device (Asus Eee 1008) it seems there is no h.264 (or even Open MAX IL) support. If anyone could provide some info I would be grateful! Let me clarify that gst-openmax is only a bridge from GStreamer to OpenMAX IL. Even if MeeGo had gst-openmax, it would be useless without an OpenMAX IL implementation. So, my understanding is that MeeGo doesn't come up with proprietary codecs, for that you'll need to ask codec vendors (Aricent, Fluendo, etc.), and they might in turn use gst-openmax, gst-dsp, or gst-vaapi. -- Felipe Contreras ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] PyQt
Dear Fathi, That was not my intention, well, in better- I meant heading to bind some new libs that did not exist when PyQt was created and thought of a couple of features that I will *personally* very much like in PySide once their finished, like this[0] one for example. Sorry for mis-phrasing! Indeed, there are pros/cons to each and one should use the best tool for the job (tm) :-) Not to mention that PyQt is probably more spread and is heavily used all over since it has been around for longer. Thus could be easier to get going with since there are repository packages and tons of material to get started with both online and printed. This also shows promise to enable to port back and forth at relative ease[1]. [0] http://www.pyside.org/docs/pseps/psep-0102.html [1] http://stackoverflow.com/questions/1297660/pyside-vs-pyqt Fathi, please take liberty to make me stand corrected if I'm wrong and note my notes are just in-my-experience recommendations and should not be considered as authoritative advice. Cheers, Sivan On Mon, Jul 26, 2010 at 9:39 AM, fathi.bou...@nokia.com wrote: Hi, If you want the PySide bindings which are supposed to be a better, more complete version of the original Qt bindings, Please, don't spread FUD but give facts. We have 2 competitors for the Python bindings. Both have pros/cons and both try to push their implementation. I let the reader to search the relevant information to make his own choice. Cheers, Fathi ___ 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] nfs package in meego ?
On Jul 26, 2010, at 07:25, Carsten Munk wrote: 2010/7/23 Auke Kok auke-jan.h@intel.com: On 07/23/10 14:23, adhyas.avas...@nokia.com wrote: Do we have the nfs-utils and nfs-utils-lib package for MeeGo 1.0 somewhere in the repo? Can you please point me to it? I tried installing a public rpm but that is not sufficient to configure the nfs server on MeeGo. neither, MeeGo doesn't support NFS, nor do we have the needed kernel options enabled or tools packaged. There is one quite legit use for NFS, which is general handset development. Traditionally many porters use NFS as boot medium for their boards to not constantly rewrite NAND or SD cards with system images on them, effectively speeding up their development cycles. For non-netbook configurations like handsets or development boards, modules may be considered useful to have enabled. Chances are though that board porters will just enable NFS in their kernel configurations. This doesn't mean the utils have to be there, at least in N900, we use busybox to fullfill that within a boot initrd. There are always going to be use cases for NFS, especially from developers or sysadmins who are more familiar with NFS than something else. But I think as far as the current discussion goes, Arjan is making sense. sshfs can pretty much replace NFS plus it gives you encryption for free! It has somewhat less complexity that NFS, and has somewhat fewer dependencies. I use it to develop on my N900 and don't miss NFS at all. I'm not fully convinced there is a need to maintain NFS in MeeGo and I think everyone would prefer less complexity so perhaps we can define an end user use case which clearly demonstrates the need for NFS that sshfs doesn't fill? Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] PyQt
On Monday 26 July 2010 10:30:34 Sivan Greenberg wrote: That was not my intention, well, in better- I meant heading to bind some new libs that did not exist when PyQt was created Just a smallish note from someone who follows PyQt development fairly closely - I would not be surprised if those new libs (or at least a major subset of them) popped up as supported under PyQt. My OBS-foo is not yet strong enough to allow me to tinker with bindings under MeeGo, but it is on my (rather longish) to-do list, as, though some might disagree, I still feel there is some advantage of having two bindings. OTOH I do think MeeGo should (have) push(ed) for full platform level python availability from day 1, picking a preferred/official binding if necessary. Best regards, Attila ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] PyQt
Atilla, On Mon, Jul 26, 2010 at 12:30 PM, Attila Csipa me...@csipa.in.rs wrote: Just a smallish note from someone who follows PyQt development fairly closely - I would not be surprised if those new libs (or at least a major subset of them) popped up as supported under PyQt. My OBS-foo is not yet strong enough to allow me to tinker with bindings under MeeGo, but it is on my (rather longish) to-do list, as, though some might disagree, I still feel there is some advantage of having two bindings. OTOH I do think MeeGo should (have) push(ed) for full platform level python availability from day 1, picking a preferred/official binding if necessary. Just to second that- and I know we've already discussed this on IRC, but I strongly support the idea to have full platform support for Python, to the extend of reaching the OVI store and more monetary (but not necessary paid) style distribution channels. I actually agree with every word , and couldn't say this better. The issue is I guess with maintainer ship, who when and how? (having two frameworks strictly speaking suggests 2 maintainership efforts?) Sivan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] FAQ? Cannot create UBI image for N900 MeeGo codedrop
2010/7/26 Anthony Lee anthony@linux.intel.com: I never succeed to use RAW image with kernel by flasher downloading to boot up N900 with MeeGo. I like to try UBI to flash into the NAND device on N900. However, UBI image never can be generated correctly due to wrong usage in mic-image-creator and its associated Python script. Hi, Show up at #meego-arm on irc.freenode.net and let's work it out. You want to use -raw images as kernel doesn't really boot into ubifs by defaut. Best regards, Carsten Munk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] GCC 4.5 in use for arm building since when?
hi, It seems that build 1.0.80.10.20100713.1 is the last one with gcc 4.4. I'm playing with v7 only at the moment. I did not comment to BMC#3936 as everything I could have said was said already. I just voted ;) I don't have had yet time to try with patches. Thanks, Jyrki 26.07.2010 05:17, Zhang, Austin kirjoitti: In trunk, it is about mid of July. For BMC#3936, it was fixed with mentioned patch and is on the way to trunk. And specific to this bug, it is more like issue related with ARMv7, do you run into in v7 only or both in V5 and V7 in meego? Can you please described your issue in BMC#3936 also? *From:* meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] *On Behalf Of *Jyrki H?m?l?inen *Sent:* Sunday, July 25, 2010 4:59 AM *To:* meego-dev@meego.com *Subject:* [MeeGo-dev] GCC 4.5 in use for arm building since when? Hi all, I did run into some problems in running rootfs built from daily repos. Yes, I like to live dangerously. The problems seem to relate to gcc4.5 adoption at some point of time. e.g. http://bugs.meego.com/show_bug.cgi?id=3936 Could someone point me the date when new gcc was taken in use, so I could try to build a working image? It is probably announced somewhere, but I was not able to find this info. Cheers, Jyrki ___ 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] Problem in flashing meego kernel image to n900 device
Hi Mifraz, Were you able to bring up the Handset UX on Nokia N900 device? or just the terminal? -- Regards, Sharavana ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] nfs package in meego ?
On Monday 26 July 2010 10:29:19 Jeremiah Foster wrote: I'm not fully convinced there is a need to maintain NFS in MeeGo and I think everyone would prefer less complexity so perhaps we can define an end user use case which clearly demonstrates the need for NFS that sshfs doesn't fill? I think end-user use cases will be quite rare -- but then that is what the community is for: to support rare or niche end-user requirements. My use case is a developer use case. I am sure I am not the only developer to have my development environment built around NFS. Files live on servers and are accessed over NFS. Workstations, build machines, regression test machines, manual test machines all create, edit or access the files in the same way, over NFS. While NFS is not perfect, it works quite well for this sort of setup and I have been using it for close to 20 years. Many of those machines are virtual, and are running all sorts of strange software (for example I have several different VMs running different Maemo build instances). Not only am I unwilling to completely change my development environment for one target platform, but my use of VMs means I really feel the impact of every CPU cycle expended, particularly in automatic (nightly) builds and automatic testing. My builds already can't all run in one night so some platforms only build every 2 nights. If I had to use sshfs I am sure the slowdown would be very significant and I would be looking at nightlies happening every 3 or 4 nights! The lack of NFS means I am currently limited to doing all MeeGo building and testing in chroots, not in VMs. If/when I want to start supporting MeeGo Handset that will probably be a problem. My guess is that this sort of environment is not that unusual. On the other hand, it could be supported just as an SDK configuration, without being available on production systems. Graham ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Problem in flashing meego kernel image to n900 device
i was able to load the handset UX in my N900 from the day 1 code drop. i did test the daily build this weekend and no luck. after flashing, it only shows the kernel is loading and then it goes dark. restarting the phone just boot from the original kernel. not sure if this is related to the following bug: http://bugs.meego.com/show_bug.cgi?id=3936 any idea? On Mon, Jul 26, 2010 at 4:45 PM, Sharavana Ram Kumar Sundaresan ssrk...@gmail.com wrote: Hi Mifraz, Were you able to bring up the Handset UX on Nokia N900 device? or just the terminal? -- Regards, Sharavana ___ 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] Problem in flashing meego kernel image to n900 device
On Mon, 2010-07-26 at 16:02 +0200, ext Mifraz Marzoon wrote: i was able to load the handset UX in my N900 from the day 1 code drop. i did test the daily build this weekend and no luck. after flashing, it only shows the kernel is loading and then it goes dark. restarting the phone just boot from the original kernel. not sure if this is related to the following bug: http://bugs.meego.com/show_bug.cgi?id=3936 any idea? In that case, can you try it for arm v5 architecture (instead of v7)? Cheers, Ameya. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Advise on upgrading hardware for Meego
I have two computers both of which are using AMD CPU's that are perhaps two years old. One is a laptop with a Nvidia graphics chip set, the other is a desktop with a ATI Radion HD 5600 serries chip set. I cannot get Meego to display in the Zepher (?) X session in either one. the start-meego-debug reports errors with the X server. By the way, these are both using Kubuntu 10.4 32 bit. I don't know if Meego is ever going to support non-Intel hardware, so I am thinking about buying a Intel graphics card. Is there a such a thing as a discrete Intel graphics card, I do not see one at newegg.com (only Nvidia and ATI). Can anyone offer some advise here. I really don't want to buy a whole new system, aside from the cost I just don't have room for another computer box. Any practical advise on how resolve things greatly appreciated. I 'd really like to learn how to develop for Meego, but have been frustrated by this lock out. Thanks David ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] What do I need for XENARC touch screen?
All, (or a question to Harbaum / Wmills about http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch#Touchscreen) What module, driver, rpm-package do I need for the XE1020TSV? I got no different position on the x or y axis: ./abscal /dev/input/event3 Name: eGalax Inc. Touch Supported event types: Event type 0x00 (Synch Events) Event type 0x01 (Keys or Buttons) Event type 0x03 (Absolute Axes) Event type 0x04 (Miscellaneous) x min: 0 x max: 0 y min: 0 y max: 35936 touch topleft released at: 0 0 touch bottomright released at: 0 35936 -- but from the USB point of view, it is connected: lsusb -v -d 0eef:0001 Bus 001 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0eef D-WAV Scientific Co., Ltd idProduct 0x0001 eGalax TouchScreen bcdDevice1.00 iManufacturer 1 eGalax Inc. iProduct2 Touch iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 HID-USB Touchscreen bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 44mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.12 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 141 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x0002 (Bus Powered) Remote Wakeup Enabled Thanks and best regards, Axel. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Advise on upgrading hardware for Meego
On 07/26/10 14:43, David Boosalis wrote: Kind of sad that a open source platform is wed to a rather closed platform for their SDK. I'm not sure what you're referring to here, but you can develop MeeGo applications on any MeeGo platform FOR any MeeGo platform. I'm -as we speak- running the handset UI on a plain ol' netbook. Auke ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Advise on upgrading hardware for Meego
On 07/26/10 10:20, David Boosalis wrote: I don't know if Meego is ever going to support non-Intel hardware, so I am thinking about buying a Intel graphics card. Is there a such a thing as a discrete Intel graphics card, I do not see one at they do not exist. Intel has never sold separate graphics cards for its line of gfx chipsets, as they are integrated in the chipset. offer some advise here. I really don't want to buy a whole new system, aside from the cost I just don't have room for another computer box. how about a netbook? sub-400$, small, low power I doubt you'd have to make much room for it as well. Professional CDK's for handsets are 2-4K USD, seems like netbooks are a great value offering almost all the same functionality. Auke ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] How to submit a package
Hi all, If we want to submit a package for meego, where and how to do it? Thanks in advance. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Problem in flashing meego kernel image to n900 device
Hi Ameya, ok i did try to bulid the v5 from the original nokia ks file and getting the following error while bulding: Error: failed to create image : Failed to build transaction : xorg-x11-drv-fbdev-sgx-0.4.0-2.7.armv5tel requires ld-linux.so.3(GLIBC_2.4) xorg-x11-drv-fbdev-sgx-0.4.0-2.7.armv5tel requires libpvr2d.so xorg-x11-drv-fbdev-sgx-0.4.0-2.7.armv5tel requires xorg-x11-server-Xorg meego-handset-icon-theme-0.0.4-2.10.noarch requires gtk2 rootfiles-8.1-4.3.noarch requires ncurses meego-handset-icon-theme-0.0.4-2.10.noarch requires libmeegotouch = 0.20.1 next i tried by modifying the ks files to point the meego dialy repo to armv5tel and bulid, and getting the following: Error: failed to create image : Failed to build transaction : xorg-x11-drv-fbdev-sgx-0.4.0-2.7.armv5tel requires libpvr2d.so anything i have to do before bulding for v5? i used the following mic command: sudo mic-image-creator --run-mode=0 --cache=mycachedir-daily-v5 --format=raw --arch=armv5tel --save-kernel --config=ks-file On Mon, Jul 26, 2010 at 8:03 PM, Ameya Palande ameya.pala...@nokia.com wrote: On Mon, 2010-07-26 at 16:02 +0200, ext Mifraz Marzoon wrote: i was able to load the handset UX in my N900 from the day 1 code drop. i did test the daily build this weekend and no luck. after flashing, it only shows the kernel is loading and then it goes dark. restarting the phone just boot from the original kernel. not sure if this is related to the following bug: http://bugs.meego.com/show_bug.cgi?id=3936 any idea? In that case, can you try it for arm v5 architecture (instead of v7)? Cheers, Ameya. ___ 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
