Selling n900
Hello. Sorry if this is considered spam - I do not know where else send it. I have n900 but I do not use it anymore and it is just gathering dust. I would like to sell it for 100EUR (+shipping), preferably to some developer (preferably in EU). I bought n900 in 2009; it was my main phone for 3 years. It was restarting, so it had replaced motherboard in middle 2010. I have never overclocked it, never installed power kernel nor CSSU. Best regards. -- Tomasz Rybak 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QT map widget
Dnia 2010-06-13, nie o godzinie 14:39 +0300, Alberto Mardegan pisze: (off topic: if you can find some way to reproduce it reliably, please file a bug -- although if you really need to take out the battery, that cannot be a bug in the application itself) I had similar problem and even filled a bug: https://bugs.maemo.org/show_bug.cgi?id=9743 Could not reproduce it with PR1.2 so closed it. If you want to you can reopen it - I will gladly test some use cases. Regards. -- 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: OpenCL on Maemo
Dnia 2010-03-29, pon o godzinie 18:52 +0200, Ove Kaaven pisze: Tomasz Rybak skrev: So, official Nokia document requires Maemo devices to provide OpenCL capabilities but currently there is no possibility to write code using OpenCL. Is it just left for later to implement (first go updates, additional features must wait) or MeeGo changed everything and there is no hope for OpenCL? No, it wasn't left for later either. From my understanding, the Maemo Base Port is/was a requirement document for future Maemo devices. It never applied to the N900. OK. thanks for the information. As MeeGo is in the very early phase I guess there is nothing for it yet. On the other hand, I found following post from QtLabs blog: http://labs.trolltech.com/blogs/2010/04/07/using-opencl-with-qt/ So it looks like there is work on integrating Qt with OpenCL and we could expect some progress - but for now it is pure speculation on which devices it will be available. -- 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: To jest część wiadomości podpisana cyfrowo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Builder now runs PR1.2 SDK with Qt 4.6 support
Dnia 2010-03-27, sob o godzinie 16:00 +0300, Matan Ziv-Av pisze: On Wed, 24 Mar 2010, Niels Breet wrote: Hi, I've installed the new PR1.2 SDK on the maemo.org Extras autobuilder. Developers are encouraged to test their application in the PR1.2 SDK to see if everything still works as expected. If I understand correctly, now developers who depend on maemo.org repositories to distribute their cannot distribute updates to users. Users of applications in extras-devel who delete an application for some reason cannot reinstall it. Since Nokia does not comment on schedule of future releases, we might remain in this state for a long time. Similar situation exists for packages from SDK. I have Crash Reporter installed on my n900 (I installed it for Bug #6334). Installed version is 1.27+0m5. Few days ago phone displayed information about available updates; new version of Crash Reporter was uploaded to repository. New version is 1.29+0m5, but it is not upgradeable because of missing dependencies: libhildon1 = 2.2.5 lihlindonfm2 = 1.2.28.32+0m5 libosso1 = 2.29 libpixman-1-0 = 0.15.16 I assume that if someone now would have problems with the phone, he or she would not be able to install Crash Reporter to attach core dumps to error reports. This might make debugging harder, esp. for lower-level problems. -- 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: To jest część wiadomości podpisana cyfrowo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Deleting Project PyGTKEditor from Garage
Dnia 2010-03-24, śro o godzinie 10:52 -0500, Michael Cronenworth pisze: Benoît HERVIER wrote: Once the package will be removed from extras, extras-testing, and extras-devel you will be able to install the new version from my own repository. Why are you attempting to divide the Maemo community? I have bought n900 knowing it is Debian and therefore I can, if needed, to create my own repository with my packages. So I do not believe that creating own repository is dividing community - on the contrary, it allows for others to provide users with packages. For example recently Opera created repository with Debian/Ubuntu packages ensuring that users have Opera browser updated the same way other software is updated. On the other hand I doubt ordinary users will add some strange repository - I, for myself, would though about it carefully. So this might be way for distributing software, but only for the most hardcore users. As for promotion to extras - I took part in Saturday's testing marathon, and some packages worked on my phone while not working on others, and vice-versa. So I think necessity of having 10 votes is valid. Maybe _just_ for bugfixes it could be lessened - but there is risk of abusing this approach. Debian *-security repositories for security patches. Ordinary packages must go usual way (10-days waiting period, no RC bugs) - but when security problem is detected, package with fix goes to *-security repository. This is not the same situation, but maybe this will give someone idea for solving problem of getting high quality packages into extras while not forcing developers to wait too long for package transition. My 0.02 -- 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: To jest część wiadomości podpisana cyfrowo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Residual configuration after package reinstallation
Hello. After Saturday's testing marathon I was checking free space on my device and found out that many of packages that I have installed to test left configuration files after removal. I have used `dpkg -l | grep -v ^i` in terminal to find them. There were many packages with status rc in the first column - which means that they were Removed with Configuration files left. I have removed all such packages by `dpkg -P name` but few question remain: 1. Configuration files do not take much space but when one is experimenting and testing many programs there can be many such files left. Another possible problem is that such packages are kept in database (on Debian in /var/lib/dpkg) where list of all package files, configuration files, checksums, etc. Such files sizes can add and take precious bits of rootfs. 2. I can imagine that someone install old version of package, uninstalls it while documentation is left, then after some time package gets more mature, the same person install new version which has problems because of old configuration. Another possibility is that old configuration has disabled some functionality (e.g. it was not stable at the moment) and new version keeps it disabled because of old residual config files. I know that package maintainer should take configuration updates into consideration but it might be hard - this week there was problem with updated qtirreco losing configured remotes: https://bugs.maemo.org/show_bug.cgi?id=9601 So what is reason for HAM to leave configuration when uninstalling packages (removing them but not purging)? Regards -- 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: To jest część wiadomości podpisana cyfrowo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
OpenCL on Maemo
Hello. I have been reading Maemo Base Port Technical Requirements v 1.1 from 25.1.2010 by Jari Palojärvi In chapter 3.4.4 OpenCL one can read: The Base Port should provide an implementation of the OpenCL 1.0 interface for general-purpose parallel programming of heterogeneous systems, especially for the use of GPUs for computation (Khronos group standard). I have enabled Extras, Extras-testing and Extras-Devel repositories but could not find any package regarding OpenCL. `apt-cache search opencl` returned no packages. I have found only two threads on t.m.o mentioning OpenCL http://talk.maemo.org/showthread.php?t=35950 http://talk.maemo.org/showthread.php?t=32475 both of them from 2009, and both ending with it would be good to have. So, official Nokia document requires Maemo devices to provide OpenCL capabilities but currently there is no possibility to write code using OpenCL. Is it just left for later to implement (first go updates, additional features must wait) or MeeGo changed everything and there is no hope for OpenCL? Best regards. -- 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: To jest część wiadomości podpisana cyfrowo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
