Re: Kernel compilation
On Tuesday 22 January 2013 11:02:04 Sébastien NOBILI wrote: Hi, I recently got an old N770 tablet. It works correctly with OS2005 version of Maemo. I installed OS2008-HE, which is also working quite correctly (I have an issue with WiFi but I'll address it later). My plans with this machine is to upgrade it to a Debian distro (I'm quite comfortable with Debian). Before this can be achieved, I need to install a recent kernel on the N770. The current Debian stable kernel is 2.6.32. I installed a cross-compiling environment (scratchbox2) on my PC and compiled the 2.6.32 kernel for the N770. I have a zImage that I can flash on the device. I compiled my kernel with the following commands: sb2 make n770_defconfig sb2 make zImage sb2 make modules I've flashed the kernel, modified the initfs to include 2.6.32 modules and tried to boot, but it fails. I have the Nokia splash screen for around 20 seconds, then the device halts. I enabled RD mode, expecting messages to be displayed on spash screen, but no message is printed. I guess the kernel is not even loaded. Is it possible to have a vanilla kernel working on such a device (I guess so) ? Are there any specific steps I should have run to have my kernel working (bootloader stuff, etc.) ? Did I miss something (I also guess so) and what ? Are there (for testing purpose) any ready-to-use recent kernel images for N770 ? Thanks. Sébastien Hello, Maemo systems needs its own patched kernel by Nokia. Prior N900 device kernels contains some close source kernel drivers which working only on some specified kernel versions. So upstream kernels will propably not work with Maemo. If you want to use another linux distribution you propably want to try use patched Nokia kernel which working. But if your distribution depends on some new version, then you have problem. Upstream kernels does not have proper support for Nokia devices. More drivers missing and other does not working correctly. Also there is no support for watchdogs (for 770/N8x0) in upstream kernels, so you get instant reboot after few seconds. You can try to look at meego/mer/nemo team. They have some updated kernels for N8x0, so maybe you find something for 770 too. Btw, for testing kernels, do not flash it into device, rather load it. Nokia flasher has option for it (-l) which load kernel+initfs images via usb and then run it without flashing. 0x flasher has this option too. And do you really want to have Debian on Nokia 770? Maemo is Debian like distribution, so you have dpkg/apt-get on device and you can compile and install deb packages without problem. -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: information required to replace Maemo5 wlan bits
On Friday 20 July 2012 04:13:05 Jonathan Wilson wrote: /system/osso/connectivity/IAP/wlan_tx_power /system/osso/connectivity/IAP/%s/type /system/osso/connectivity/IAP/%s/wlan_security /system/osso/connectivity/IAP/%s/wlan_ssid /system/osso/connectivity/IAP/%s/wlan_wepdefkey /system/osso/connectivity/IAP/%s/wlan_wepkey1 /system/osso/connectivity/IAP/%s/wlan_wepkey2 /system/osso/connectivity/IAP/%s/wlan_wepkey3 /system/osso/connectivity/IAP/%s/wlan_wepkey4 /system/osso/connectivity/IAP/%s/nai /system/osso/connectivity/IAP/%s/temporary /system/osso/connectivity/IAP/%s/wlan_hidden /system/osso/connectivity/IAP/%s/EAP_wpa2_only_mode /system/osso/connectivity/IAP/%s/powersave_after_scan /system/osso/connectivity/IAP/%s/wlan_powersave /system/osso/connectivity/IAP/%s/wlan_adhoc_channel /system/osso/connectivity/IAP/%s/EAP_TLS_PEAP_client_certificat e_file /system/osso/connectivity/IAP/%s/EAP_default_type /system/osso/connectivity/IAP/%s/EAP_wpa_preshared_passphrase /system/osso/connectivity/IAP/%s/PEAP_tunneled_eap_type /system/osso/connectivity/IAP/%s/EAP_MSCHAPV2_username /system/osso/connectivity/IAP/%s/EAP_MSCHAPV2_password /system/osso/connectivity/IAP/%s/EAP_GTC_identity /system/osso/connectivity/IAP/%s/EAP_wpa_preshared_key /system/osso/connectivity/IAP/%s/EAP_SIMPLE_CONFIG_device_passw ord /system/osso/connectivity/IAP/%s/EAP_MSCHAPV2_password_prompt /system/osso/connectivity/IAP/%s/EAP_manual_username /system/osso/connectivity/IAP/%s/EAP_use_manual_username /system/osso/connectivity/IAP/%s/TLS_server_authenticates_clien t_policy_in_client If you want to specify password for EAP_GTC_identity store it to: /system/osso/connectivity/IAP/%s/EAP_GTC_passcode -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: What's wrong with Extra-Asistant's autobuilder?
On Saturday 17 November 2012 12:06:24 Nguyễn Hồng Quân wrote: Hello, I want to upload my package to Extra-Asistant, build after clicking Move to builder button, nothing is done: my package is not pushed to queue and built. I repeated many times but no result. Any help? Autobuilder on garage is not working... You need to wait until some maemo admin fix it. -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 0xFFFF 0.5 released
On Tuesday 18 September 2012 17:25:57 you wrote: Hello all Maemo developers! Now after 4 years new version 0.5 of Open Free Fiasco Firmware Flasher 0x was released. It is only bug fix release which fixing generating and unpacking Fiasco images used on Nokia N900. Download page: http://nopcode.org/0x/?p=down Now I'm rewriting 0x source code for better Fiasco image support, future protocol support (cold flashing, eMMC flashing). When it is finished it will be full replacement for proprietary i386 Nokia flasher-3.5. Development source code: https://github.com/radare/0x Hello, I need dumps from flashing via original flasher-3.5 application. I need to see different control messages which are used to initialising nolo flashing. I created small ld preload library which print control messages to standard output. See TMO thread: http://talk.maemo.org/showthread.php?t�969 -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
0xFFFF 0.5 released
Hello all Maemo developers! Now after 4 years new version 0.5 of Open Free Fiasco Firmware Flasher 0x was released. It is only bug fix release which fixing generating and unpacking Fiasco images used on Nokia N900. Download page: http://nopcode.org/0x/?p=down Now I'm rewriting 0x source code for better Fiasco image support, future protocol support (cold flashing, eMMC flashing). When it is finished it will be full replacement for proprietary i386 Nokia flasher-3.5. Development source code: https://github.com/radare/0x -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 0xFFFF 0.5 released
On Tuesday 18 September 2012 12:03:16 Anderson Lizardo wrote: Hi, On Tue, Sep 18, 2012 at 11:25 AM, Pali Rohár pali.ro...@gmail.com wrote: Now I'm rewriting 0x source code for better Fiasco image support, future protocol support (cold flashing, eMMC flashing). When it is finished it will be full replacement for proprietary i386 Nokia flasher-3.5. Development source code: https://github.com/radare/0x Good to see 0x still being developed! Do you have plans to add support for N9 as well? Not sure how much effort is needed. Best Regards, Hi, I do not have N9, so I cannot test and create needed code. But, NOLO protocol seems to be same for all devices (770-N900) and I think it is still same on N9. And N900 using Mk II protocol (Not NOLO) for flashing eMMC and this protocol is used on N9/N950 for flashing other parts. Mk II is not implemented yet, but some my RE documentation is already in git tree. https://github.com/radare/0x/blob/master/doc/mkii So when eMMC flashing for N900 will be implemented, somebody can look at code and add needed parts for N9... Note that restriction for N9/N950 downgrade is implemented in bootloader, not in flasher! -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N900 dbus interfaces
On Saturday 28 July 2012 12:16:43 Jonathan Wilson wrote: I have created a Wiki post to document the known Nokia-specific dbus interfaces used on the N900. http://wiki.maemo.org/N900_dbus Let me know if you have any feedback on the page or if you have anything to add to it. Hi! This is really good page. Maybe usefull would be write for each dbus interface which daemon it handle (+deb package which install that daemon). Also can you add if daemon/package is proprietary or open source? -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Everybody please fix bug in your scratchbox installation!
Hello Maemo Community! Now after long time I found a very very *big* problem in Nokia Maemo SDK virtual image which can be downloaded from location: http://tablets-dev.nokia.com/maemo-dev-env-downloads.php file Maemo_Ubuntu_Lucid_Desktop_SDK_Virtual_Image_Final.7z Problem is in scratchbox and may be in regular scratchbox installation on desktop too (not only in virtual image)! That Virtual image contains *thumb* string in scratchbox shell variable DEB_BUILD_OPTIONS which cause that some applications will be compiled with thumb instructions. Thumb is unstable on default Maemo 5 for Nokia N900 and applications which are compiled with thumb-2 will crash without any reason. Check if you have problematic scratchbox: 1. Login to scratchbox: run /scratchbox/login 2. print DEB_BUILD_OPTIONS in scratchbox: echo $DEB_BUILD_OPTIONS If it does *not* show thumb your scratchbox is already fixed and thumb is disabled. If it *show* thumb, disable it. Instructions how to disable *thumb* string in scratchbox: 1. Login to scratchbox: run /scratchbox/login 2. Edit file /targets/FREMANTLE_ARMEL.environment 3. Remove thumb from that file 4. Save file and *logout* from scratchbox Note that scratchbox is loading DEB_BUILD_OPTIONS variable at startup, so you need to restart scratchbox to take effect. After restarting please check again if thumb is really disabled. -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: New tool available to decrypt encryped N900 backups without a N900
On Monday 05 March 2012 18:34:55 Jonathan Wilson wrote: Thanks to Pali finding some old osso-backup source in http://repository.maemo.org/pool/maemo3.2/free/source/, I was able to build a tool that decrypts encrypted osso-backup files without the need to have a working N900 Fremantle install. The download is at http://www.cncmods.net/files/backupdec.zip and is compiled via backupdec.sh. It will compile in scratchbox if you have libosso-gsf-1-dev, libglib-2.0-dev and libssl-dev installed or it should compile in a normal linux environment if you have normal libgsf, glib and openssl headers installed (you will need to edit the sh file pkg-config options for this) To run the compiled binary, run backupdec in out password where in is the encrypted zip file from the backup, out is the name of the output unencrypted zip file and password is the password used when the zip file was created. It can also be used to decrypt zip files on the N900 itself if you want to decrypt the files without actually restoring the backup. (i.e. build an arm binary of this and run it on the phone) If someone has a specific need for a binary of this built for a specific platform, let me know and I will see what I can do to get a binary. Hi, thanks very much for decrypting backup file format! -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Supertesters - Make, accept, nominations
On Thursday 16 February 2012 08:31:47 robert bauer wrote: We are in need of supertesters to promote packages on Extras. This is a crucial function which is currently suffering because the list of supertesters and promotion rules have not been updated in a long time. [url] http://lists.maemo.org/pipermail/maemo-developers/2012-January/028825.html[/ url] Of the [URL=https://garage.maemo.org/projects/qatesters/]current list[/URL], I propose to keep Andre Klapper and Harald Schmitt because they continue to be involved. If anyone has been involved and I missed it, please speak up. I'm sorry and you will be kept as well. For new supertesters, we should have people who have a demonstrated interest in maemo and ability to test maemo packages. It is vital that supertesters are trusted members of the community. A single supertester will be able to promote someone else's (not their own) package. [U]Please feel free to suggest different or more objective criteria for supertesters.[/U] So far the following have been nominated: Pali freemangordon nicolai merlin19xx MAG Rob (This has also been posted on the forum.) We (Maemo Community) really need people with ability to promote packages which do not maintain (e.g not on maintainer list). See how log took to promote package rootsh, version 1.8 to Extras (more than year?). Old version in Extras had critical bug which cause not possible to uninstall package. And maintainer abandoned Maemo community, so nobody had permission for it! I would like to see permission for promoting packages which I update and not wait while old maintainer give me needed permisstion! -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Subtle difference in behavior of installation packages
Hi, On Wednesday 08 February 2012 13:10:25 John Pietrzak wrote: Hi folks, I've been working on a small Maemo app, and have reached the point where I've pushed it up to Extras-Devel. Almost everything works perfectly, except for one item: I've created a sudoers file for the app, in order to allow it to call modprobe to load a kernel module. (This is the lirc_rx51 module, needed for access to the IR hardware.) This file needs to go into the /etc/sudoers.d directory. I can install and uninstall the file just fine using the debian package I've constructed locally. When installing the app from the Extras-Devel repository, however, the application manager can place the file into /etc/sudoers.d, but seems unable to remove it when uninstalling. Try to run apt-get remove package in xterm. This is what application manager doing... Also see error in application manager log. I'm using the Qt SDK, and have recently upgraded to Qt Creator 2.4.1, so maybe the latest Qt software creates debian packages differently than the Extras system does... So, I guess these are my questions: 1) Do I need to do something special to install/uninstall files to the /etc directory in Maemo? I think nothing special. Only add your /etc files to conffiles in debian package, but this is done by debhelper script for dpkg-buildpackage. So really nothing. 2) Should I even be using /etc/sudoers.d to let my app access modprobe? What is the preferred way for an app to make requests of the kernel? Yes add sudoers file, run script for updating sudoers.d and use: sudo modprobe module Thanks! --John -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Subtle difference in behavior of installation packages
On Wednesday 08 February 2012 21:04:26 gregor herrmann wrote: On Wed, 08 Feb 2012 19:21:16 +0100, Pali Rohár wrote: I can install and uninstall the file just fine using the debian package I've constructed locally. When installing the app from the Extras-Devel repository, however, the application manager can place the file into /etc/sudoers.d, but seems unable to remove it when uninstalling. Try to run apt-get remove package in xterm. This is what application manager doing... Also see error in application manager log. apt-get remove without --purge won't remove conffiles, which would explain why /etc/sudoers.d/foo is still there ... And that's on purpose at least in Debian. If HAM can't be told to purge a package there's not much that can be done (short of using brute force in the postrm maintainer script. Ehh, this sounds ugly.). Cheers, gregor You can create sudoers.d file in postinst file and remove it in postrm. echo ... /etc/sudoers.d/... Or you can force debhelper to not add that sudoers file to conffiles. -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [ANNOUNCE] N9/N950 TV out control application
On Friday 13 January 2012 08:51:21 Ville =?ISO-8859-1?Q?Syrjälä?= wrote: On Thu, Jan 12, 2012 at 09:55:21AM +0100, Pali Rohár wrote: Checking if and which Maemo version is running on build system server can be detected by pkgconfig package maemo-version. That's not available in harmattan. But anyway I realized I need to change the build dependencies anyway, so I just removed the packaging from the master branch and moved it to fremantle and harmattan branches for each platform. Can you merge CSSU repository (with new control panel status menu plugin) into main maemo-tvout-control repository? -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [ANNOUNCE] N9/N950 TV out control application
On Thursday 12 January 2012 10:37:12 Ville =?ISO-8859-1?Q?Syrjälä?= wrote: On Mon, Jan 09, 2012 at 12:36:02PM +0200, Ville Syrjälä wrote: On Mon, Jan 09, 2012 at 10:46:14AM +0100, Pali Rohár wrote: I think that the best will be to have one repository for tvout-ctl, one for fremantle (here will be fremantle plugins) in CSSU project and one for harmattan. What do you think? Sounds good. We don't really need a harmattan specific GUI repo, at least yet. The standalone Qt GUI should work in both fremantle and harmattan if the tvout-ctl API is the same. Some clever way to handle packaging may be needed if there are differences. Perhaps keep the packaging stuff in separate branches and merge master to them when the actual code changes. I now merged both Xv and XRandR codes to libtvout-ctl [1]. I changed the license of this library to LGPL 2.1. There's a configure option to select the backend at build time. The debian packaging will build the Xv backend. I'm not quite sure how I'll sort the issue on how to build for harmattan. The same packaging otherwise works for both platforms, so it would be nice to have some decent way to detect the platform during the build and use that to select the backend. It would avoid having to duplicate the packaging and maintaining multiple branches. Run-time backend selection would be another option, but seems a little pointless considering you have to build separate binary packages for each platform anyway. I updated both maemo-tvout-control and n9-tvout-control to use the new library. [1] https://gitorious.org/maemo-tvout-control/libtvout-ctl Checking if and which Maemo version is running on build system server can be detected by pkgconfig package maemo-version. -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [ANNOUNCE] N9/N950 TV out control application
On Friday 13 January 2012 08:51:21 Ville =?ISO-8859-1?Q?Syrjälä?= wrote: On Thu, Jan 12, 2012 at 09:55:21AM +0100, Pali Rohár wrote: Checking if and which Maemo version is running on build system server can be detected by pkgconfig package maemo-version. That's not available in harmattan. But anyway I realized I need to change the build dependencies anyway, so I just removed the packaging from the master branch and moved it to fremantle and harmattan branches for each platform. So configure script can check if maemo-version exist. If yes build system is fremantle otherwise harmattan. -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [ANNOUNCE] N9/N950 TV out control application
On Monday 09 January 2012 10:39:43 Ville =?ISO-8859-1?Q?Syrjälä?= wrote: I finally managed to make some progress on porting maemo-tvout-control to harmattan. Code is here: https://gitorious.org/maemo-tvout-control/n9-tvout-control What you'll find there is a a very simple QWidget based GUI, and backend code utilizing XRandR. The backend supports a few extra knobs, when compared with fremantle. However, I was too lazy to write the extra GUI code. So the current GUI offers the same controls that maemo-tvout-control has. The ultimate plan is to write a nice QML GUI for this stuff, although I don't know when I'll have time to learn QML. Another idea I have is to move the backend code to a separate library. The same should be done for the fremantle Xv based backend code. This would provide a unified TV out control API for both platforms. Hello, last year I merged maemo-tvout-control with control panel settings plugin for Nokia N900. Code is now in Community SSU on gitorious https://gitorious.org/community-ssu/maemo-tvout-control and is based on your orignal code https://gitorious.org/maemo-tvout-control/maemo-tvout-control I created new tvout status menu plugin, it is in that CSSU repository too. It is possible to merge my changes on CSSU to your project? I think it is not good idea to have 2 separated projects which has same code. (I sent you mail before I forked your code, but you do not responce...) -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Announce: Open Source Cold Flasher for RX51
Hello, I decoded cold flashing process in proprietary Nokia Maemo flasher-3.5 program and I created open source program which can cold flash 2nd x-loader and NOLO images. Cold flashing is needed when X-Loader or NOLO bootloader (on boot partition) is damaged and/or cannot enter to normal flashing mode. See thread: http://talk.maemo.org/showthread.php?t840 -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Adding extra languages into Welcome screen
Hello, you may noticed that Maemo 5 Welcome screen (which appears after instering battery or flashing) does not show all extra installed Maemo 5 translations. Problem is because, osso_startup_wizard (Welcome screen application) read language table from library libi18n-locale-resolver0. And that libray read languages from binary file /usr/share/i18n-locale-resolver/lra_language.data (and not try to check which translations are installed) I created small shell script which can modify (add/delete) language strings (e.g en_US) to that binary file and thus Welcome screen show/hide other languages. Script is in Extras(-devel) package locale-resolver-config http://maemo.org/packages/view/locale-resolver-config/ and install file /usr/sbin/locale-resolver-config For example adding Slovak language (which is not by default in Maemo) call: $ locale-resolver-config add sk_SK and to remove $ locale-resolver-config del sk_SK Maintainers of extra Maemo 5 translations could modify their postinst/postrm scripts to call this script for adding/removing their language to/from Maemo 5 Welcome screen. -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Done: Merged tvout desktop widget and tvout control panel plugin
Hello, now process of merging tvout widget and control panel plugin is done. my code is on http://atrey.karlin.mff.cuni.cz/~pali/maemo-applet-tvout.git/ This git repository is based on https://gitorious.org/maemo-tvout-control commit 7c62daed482fb9dcf5e830609b338ca24b4736b0 It contains open source clone of tvout control plugin - written in Gtk and new status menu plugin (which show status if tvout cable is connected). status menu plugin handle tvout gconf keys and receive/send x11 events for chaning tvout attributes. Can be my status menu and control plugin pushed into CSSU? In CSSU is already repository for tvout control panel: https://gitorious.org/community- ssu/libcptvout Builded deb packages are here: http://atrey.karlin.mff.cuni.cz/~pali/maemo-applet-tvout_2.0_armel.deb http://atrey.karlin.mff.cuni.cz/~pali/maemo-tvout-control_2.0_armel.deb http://atrey.karlin.mff.cuni.cz/~pali/status-menu-applet-tvout_2.0_armel.deb -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Done: Merged tvout desktop widget and tvout control panel plugin
hello, control panel plugin and desktop widget change only gconf keys. status menu plugin is responsible for changing x11 tv attributes (tv standard attribute is handled by ohm and dres), so it monitor for gconf key changes (as ohm). so both control panel plugin and desktop widget depends on status menu plugin. all 3 plugins using shared header file (which contains gconf keys definitions) so it is better to have only one repository. now this repository is on top of the https://gitorious.org/maemo-tvout-control and has no code from actual CSSU libcptvout (I implement my own control panel plugin in Gtk, I not used CSSU libcptvout Qt code). So merge request for libcptvout is not possible. On Sunday 13 November 2011 16:28:09 Mohammad Abu-garbeyyeh wrote: Yes, I see no problem in including this in the CSSU, can you make a merge request for the control panel applet? I'll make a repository for the status menu plugin as soon as I'm done with uni. Regards, Mohammad Abu-Garbeyyeh On Nov 13, 2011, at 3:59 PM, Pali Rohár pali.ro...@gmail.com wrote: Hello, now process of merging tvout widget and control panel plugin is done. my code is on http://atrey.karlin.mff.cuni.cz/~pali/maemo-applet-tvout.git/ This git repository is based on https://gitorious.org/maemo-tvout-control commit 7c62daed482fb9dcf5e830609b338ca24b4736b0 It contains open source clone of tvout control plugin - written in Gtk and new status menu plugin (which show status if tvout cable is connected). status menu plugin handle tvout gconf keys and receive/send x11 events for chaning tvout attributes. Can be my status menu and control plugin pushed into CSSU? In CSSU is already repository for tvout control panel: https://gitorious.org/community- ssu/libcptvout Builded deb packages are here: http://atrey.karlin.mff.cuni.cz/~pali/maemo-applet-tvout_2.0_armel.deb http://atrey.karlin.mff.cuni.cz/~pali/maemo-tvout-control_2.0_armel.deb http://atrey.karlin.mff.cuni.cz/~pali/status-menu-applet-tvout_2.0_armel .deb -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Looking for help from a GTK guy with 2 projects
Hello, On Sunday 13 November 2011 11:11:41 Jonathan Wilson wrote: I am looking for someone with some GTK skills to help me with 2 projects. The first is my Cell Broadcast SMS widget, I need someone who can help me write the control panel/settings thing (including use of whatever settings storage method makes the most sense) I already written hildon control panel plugin (clone of maemo-applet-tvout: http://atrey.karlin.mff.cuni.cz/~pali/maemo-applet-tvout.git/ ), so I can help you. But What is Cell Broadcast SMS? The second is related to my virtual keyboard work. Rather than create an identical clone of the existing virtual keyboard, I have realized that its better to figure out exactly what the external interface to libhildon-im-vkbrenderer is and then have someone else with the right GTK skills write a new virtual keyboard that confirms to the same externals (and is therefore a drop-in replacement) Please let me know if you have the skills and can help me. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
