Re: Python and GStreamer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jesse Guardiani schreef: And the related question is: given an existing program that sends stuff out to ALSA and doesn't use gstreamer, how difficult is it generally to port it so that it works properly? No porting necessary, really. mplayer comes with a decoder called libmp3. It's not optimized for ARM or anything, and it compiles without any problems. We don't use it in Kagu for A2DP though because there is another decoder out there called ffmp3 which doesn't use floating point math, so it's a little more efficient on ARM. use libmad (-ac mad), that works great on arm and x86. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG1sERMkyGM64RGpERAsWdAJ4+hsMXCDH8eiyMDPVbJfjBknDLMACbBvuf qoDtnZ5HfdOlgxxZommHfNc= =5/O8 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Python and GStreamer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jesse Guardiani schreef: Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jesse Guardiani schreef: And the related question is: given an existing program that sends stuff out to ALSA and doesn't use gstreamer, how difficult is it generally to port it so that it works properly? No porting necessary, really. mplayer comes with a decoder called libmp3. It's not optimized for ARM or anything, and it compiles without any problems. We don't use it in Kagu for A2DP though because there is another decoder out there called ffmp3 which doesn't use floating point math, so it's a little more efficient on ARM. use libmad (-ac mad), that works great on arm and x86. Any cpu savings over ffmp3? The mplayer maintainers tell me that ffmp3 is the best choice on ARM. No idea on that, but I'm wary of anything starting with 'ff' that pretends to be a shared lib. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG1sOIMkyGM64RGpERAle/AKCUUMw9FYl0qjbSSuPKI3pYb9MqDgCgj/pC ulYpOJKsqKpSvGgoJlOYLo8= =JzqT -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 3.2007.10-7 - Detailed change log?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] schreef: To be honest, your response is more along the same line of the previous responses, i.e. it's more complex than you understand which again just tells me Nokia either can't or won't provide this information. Makes me sad people see it this way without knowing enough. Makes me sad when nokia (employees) don't tell us enough and then try guilting us into shutting up with statements like the above. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGtvYkMkyGM64RGpERAnwcAJ4n7xhy/yyJ1s/L+5qoZamGLpOJfgCffT4J R7nCzJO33MnEsTcK4cAhslo= =0jBs -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 3.2007.10-7 - Detailed change log?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andy Mulhearn schreef: I understood the problem being discussed here is how to map that to public releases and for end-users? As Quim stated, this is being (slowly) improved. If slow improvement means not seeing any change over a period of six months then yes, there is slow improvement. Six months? I think you mean 2 years :( regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGs4JxMkyGM64RGpERApXnAJ9ENMUQbN84Il0O+MM6zAWeTjahZgCgqGln 60+EAGvIcQu2CIw8Psw9hg4= =rX1k -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Public maemo repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Stone schreef: (That our SDK could certainly be improved is a separate issue as to whether we should use OE/BitBake or Debian packages.) Again, that is not an 'or', OE is perfectly capable of creating debian packages, as the Mamona distro for maemo proves. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGrdivMkyGM64RGpERAkVtAJ44HZPsI12xuP25wMHjekYZM+DmrACgkxzW ZtDIHX/LVIOtaJZwBB/j+1A= =KSY+ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Public maemo repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rodrigo Vivi schreef: Some Months ago Koen said me a truth: Hackers like to code and don't want to spend their time packing To summarize the differences: * OE is a build and packaging tool * Scratchbox is a development tool They overlap in the 'compiling' part, but that's about it. Both systems were designed for different goals, so I don't see them as competitors[1]. regards, Koen [1] OE even has targets to generate scratchbox1 toolchains -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGqgT1MkyGM64RGpERAuAoAJ43FYJl0rXRiYAWPprdO7h8yDgTcACfR6Vz xYwQs2z799+4+lHzav7Myac= =RQ2z -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: sbox2 maemo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lauri Leukkunen schreef: Also note that SB2 is totally not interested in doing x86-x86 development, like what many people are doing today with SB1. People need to wake up, smell the coffee, integrate with debian proper and get with the program. I agree with that It's stupid to maintain a lame x86 port of maemo which nobody wants when all the components should be pushed to debian and ubuntu and get those bigger communities involved in their development. The big problem is that hildon depends on an old, forked version of gtk+ that nobody in their right mind wants on their x86 systems. The nokia people at guadec were unable to give me an ETA on when that will be fixed :( One day we will anyway be running debian/stable with a few custom components on the tablets. You mean switching back to OABI? That was the aim with this whole debian thing in the first place, remember? Not marketing targeted at geeks? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGqFVxMkyGM64RGpERAnQsAJwN6pV7jGNvhAsj9L3B2apdBEngWACcD7LI UJYH2aGwUWyMgVEehMoEpXY= =oMOm -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Features to improve the platform
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Hagood schreef: On Mon, 2007-07-02 at 10:36 +0300, Kalle Valo wrote: Yes, that's a problem. Does USB support multiple profiles at the same time? What I'm after here is that N800 would have both USB mass storage and usbnet enabled concurrently. That would be really cool. Yes, USB can have a different class for each interface, with multiple interfaces within a given configuration - so you can have an device with multiple configurations, one configuration offering USB storage, one offering USB networking, one offering USB serial, and one offering all of the above, each on different endpoints. Even better, the kernel patch doing exactly that was written by the Nokia research lab in brazil. Check linux-usb-devel archives (late feb, early march 2007). regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGigGDMkyGM64RGpERAtJzAJ9ejKvPqS/1KiKSXBiX3sBLljIbzgCfd4X7 zy1waVMB4Wg9aWCMQrvDz6Y= =5K06 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N800 WLAN driver sources
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Arnaud Patard (Rtp) schreef: Andrew Barr [EMAIL PROTECTED] writes: On Tue, 2007-02-20 at 16:51 +0200, Kalle Valo wrote: I just released a source package of the N800 WLAN driver: https://garage.maemo.org/frs/?group_id=12 Please send any questions to this list and also CC me, so that I don't miss it. Is this driver seriously truly open source--e.g. I don't see any binary objects in the tarball Look closer at the tarball and you'll notice that the umac.ko module is a dummy module. You still need the proprietary umac.ko that came with your device. Would a bit of objdump and objcopy magic make it work with self-compiled kernels (e.g. with gcc4)? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFF23fCMkyGM64RGpERArquAKCyM5Cz0seDJkiYooJLbiRoKYh4tgCbB5/7 3CmonGfyZSnSXIF9eZemHLU= =HYyl -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo ARMEL server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ramon Navarro Bosch schreef: Hi every body ! Thanks to Nokia and Free Software Department on Politechnic University of Catalonia I could put a ARMEL server on the NET. It's a hardware (600 Gbytes HDD, IOP intel 600 Mhz, 512 Mb RAM ) with armel kernel and maemo rootfs. It have also the debian rootfs on diferent chroot. If anybody needs host compiling ( because of crosscompiling is not an option ) you can ask to me and I will create a user. The hardware we used is an ALL6500 and I followed http://www.cyrius.com/debian/iop/ . Note that debian/armel is incompatible with maemo/armel. Maemo uses a gcc3 based toolchain with a glibc that supports EABI syscalls via a shim, while debian uses gcc 4.1.x and glibc =2.4. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFF0ZCYMkyGM64RGpERAlXJAJ4hE6cSEHtcwS+VZhbYXb5JTUdKkgCeJTv0 08OpkaNEdXNZDaq+Brkobhg= =j3Fi -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Dream Scenario (Re: Maemo roadmap, SDK improvements...)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Stone schreef: On Wed, Feb 07, 2007 at 10:33:17AM +0100, ext Hanno Zulla wrote: to me, the relationship between Maemo's FOSS parts and Maemo's closed parts are like the relationship between Ubuntu and its closed source driver packages (NVidia, WLAN firmware, etc.). I would be nicest if Maemo was distributed similar to that. Not quite: you can run Ubuntu without any non-free components, but you can't exactly boot the N800 without a bootloader. For Maemo as a platform, generally the split is similar to Ubuntu (i.e. non-free stuff makes use of free stuff, and not in the other direction), Did I miss the opensourcing of DSME? but as you hit the lower levels of the stack, it's not so clear-cut. Also, the FIASCO generator would presumably have to be opened for this to happen. Cheers, Daniel (who has no position on the matter, or influence, but is just drive-by commenting) ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFyZ/sMkyGM64RGpERAnExAJ9HDT9HEjexKeaebk6rgELscdCu5gCgr4fS 1JruCw6Leo/GNYElaOHGB/Y= =S/X/ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] cx3110x source code is for the nokia800?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Is the cx3110x source code is for the nokia800 available somewhere? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFv4NTMkyGM64RGpERAtSeAJ4katS4gbm15s9mDD7hDvXkkMKQ/QCgnPwz SMsVmRLAojP9ogu2mp+RkXs= =VPtb -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] cx3110x source code is for the nokia800?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Komal Shah schreef: On 1/30/07, Koen Kooi [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Is the cx3110x source code is for the nokia800 available somewhere? I don't think that it is available. It is binary only module Geez, how bad does nokia want to get sued for GPL violations? because of chip manufacturer and many other things. Where chip manufacturer and many other things read complete and utter bullshit -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFwEhrMkyGM64RGpERAjfeAJ4p75BiTx5A9oeipNsMvujx4A4nAQCeOm/a dW4hmfCdMMbenGEVd8VvXZs= =V0gE -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: sapwood documentation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Forwarding as requested :) Michael 'Mickey' Lauer schreef: Koen, could you send this to [EMAIL PROTECTED] on my behalf? -- i have tried twice, but it seems I'm stuck on some filter or something. Thanks! Hi, the OpenMoko [1] team is evaluating to use the sapwood theming engine on our forthcoming Linux distribution for the Neo1973 mobile phone. Is there any documentation -- apart from the source code, of course -- about the additional keywords and functionality provided on top of the pixmap engine? [1] http://www.openmoko.com Thanks, :M: -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFtOvMMkyGM64RGpERAtAgAKCBqVds9VS1g+l4oz+ZjPb6/PDVUwCeM6Zr MYjOQEaSscSQqg8UO8CLR+w= =CGil -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Weinehall schreef: On mån, 2007-01-15 at 11:50 -0800, ext Ty Hoffman wrote: Y'all, I haven't seen any specs on the n800 camera (resolution, etc.). Can anybody point me in the right direction? Thanks. Oh, and for what it's worth, I'm now getting annoyed with the speed of the n800 developer discount program...I want to buy an 800, but of course would like to know if I'm one of the chosen ones for the discount. Don't want to buy one and then get the 'you're a winner!' email. I don't like to complain, because I know it's probably tough to manage a discount program and be fair, but a little more alacrity would be good. Meanwhile I'll just sit here on my hands for a few days more before I make the drive to CompUSA. Any ETA out there?? Yeah, I understand how annoying it is that it has been a whole week (gasp!) since the product launch without any decisions on what developers will be picked for the developer discount program. Oh and woes if it would take another week or two. Maybe not *all* virtues are lost, but patience certainly seem to be dead and buried. On a more serious note: the reason this is taking time is simple: we've spent enormous amounts of energy on getting the N800 out in time in the first place. We simply haven't had any time to focus on the developer discount program, since it did not have a firm deadline; CES did... I take nokia is going to refund the €300/$300 price difference for people that bought an n800 already but are going to be in the dev program? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFrMitMkyGM64RGpERAl+UAKCUqTA7z5/FznOJQVGEyrOXlNPaRQCgjFC8 M9O5bo8qVWcSDv2pM2V7i/8= =LKbj -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Cairo performance comparison, 770 / N800 / PXA-320
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marius Gedminas schreef: On Sun, Jan 14, 2007 at 07:53:06PM +0200, Marius Gedminas wrote: On Sun, Jan 14, 2007 at 12:11:37AM +0200, Siarhei Siamashka wrote: Also Nokia 770 runs not at 220MHz as stated on your page, but at something closer to 250MHz as shown by this test code program (and confirmed to be actually 252MHz by somebody from Nokia on #maemo about half a year ago). So http://maemo.org/faq/faq.html#faq-N10129 is lying? The OMAP1710 page from Texas Instruments also claims 220 MHz is the maximum frequency: http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123navigationId=11991contentId=4670 I've seen 330MHz 1710 units. It's a matter of how nice you are to TI :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFqnQ+MkyGM64RGpERAkisAKC75qv11d38aYMSeWxCvsDUUqlwCACfQU8q T57VA065vmgILpyB1WQW/SE= =bWlS -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Discussion of a possible project - offline calendar project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mathias Uebelacker schreef: Hello, i would like to invitate you to discuss a project idea that i have. In the last past weeks a played around with an idea to create an offline caledar like the go ogle calendar. After my device chrashed yesterday this project becomes a higher priority. Till yesterday a worked on my timetracker project. Exactly on a modul which creates for every task an file which can be imported by the calendar. snip So you're basically reimplementing either 'gpe-calendar' (syncing with google calendar) or 'dates' (cool UI, integration with eds-dbus). regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFqrBYMkyGM64RGpERAlGhAKCuJuEWONzuvqJKtkn3lppT2v5bTQCgnYMs 4KZpzCGKZSX0c/f7dn84ulQ= =qPN9 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Cairo performance comparison, 770 / N800 / PXA-320
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Siarhei Siamashka schreef: On Saturday 13 January 2007 21:00, Kalle Vahlman wrote: As for optimizing code for ARM (targeting Nokia 770), there are a few things that are slow (maybe this list is still incomplete): 1. Floating point math is slow without vfp (cairo contains a lot of fp math) Actually not very much if you build it with --disable-some-floatingpoint regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFqWDBMkyGM64RGpERAs5EAJ9ooyKzO9GbT5aFffpdWKOfvZ31ZgCgt7Tr bOkcruGVr+RNqw2NNPwUjFs= =v9oM -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] OS2006 roadmap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Grimme schreef: I'm pretty sure that there are good reason for the compatibility problems, such as more recent libraries on ITOS 2007. If ITOS 2007 uses a Cairo-enabled GTK version (and I guess it does), then there's no point in running ITOS 2007 on the 770. It would be too slow. If you use a recent pango, cairo and gtk+ the speed difference is neglible for most widgets. Have a look at http://dominion.kabel.utwente.nl/koen/cms/cairo-performance-improvements-on-arm regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFpheOMkyGM64RGpERAvhMAJ4nn/VX+WxagHIY3D3BmaSkujBIpwCeOeF3 YvrVoCkM7QkLc+yKI5ywb00= =EXJi -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: OS2006 roadmap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ross Burton schreef: On Thu, 2007-01-11 at 11:57 -0800, Carl Worth wrote: I have no information about what version of GTK is used on the newer model, Maemo 3.0 uses GTK+ 2.6.10-2osso27, which of course is *heavily* patched. but I hope the meme of GTK and cairo are too slow for embedded will die soon. We in the cairo community have been working hard to make a lot of improvements during the cairo 1.3.x snapshots, (and particularly performance improvements for machines without hardware floating-point units). The week before Christmas I put the latest Cairo/Pango/GTK+ on a Zaurus, and was blown away by the improvements. I never got around to benchmarking it but visually the original GTK+ 2.8 release was painful, this is actually usable. I second that, with cairo 1.3.10 and pango 1.15.2 gtk 2.10.7 feels *fast* compared to 2.8 and about as fast as gtk 2.10.6 with Xan's xft patch to rip out cairo. Although a 620MHz pxa270 is a bad comparision to a omap1710. Making it even faster is of course better :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFpqXDMkyGM64RGpERAvkjAJ9m2gtH7bxOAvJqjlx/EEQjai4ZqgCfauI5 jyVJ6XkfIIs+/VbAW/QdN80= =SUFD -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] libgpsbt 0.1-18 license?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I couldn't figure out this part of the libgpsbt license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. Those are the *first* 4 lines of COPYING. I see no 'above copyright notice', just a MIT like disclaimer *below*. Could one of the nokia people give me the right license (MIT, BSD, APL, etc)? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFo2XsMkyGM64RGpERAhzoAKCSBfH0RYebJXNYSmkH0DfuVhcjDwCfb9kN defrbhB9XBJv6K+umJKR7Lg= =q7oR -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] libgpsbt 0.1-18 license?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi schreef: Hi, I couldn't figure out this part of the libgpsbt license: Same goes for libgpsmgr 0.1-10 regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFo2aaMkyGM64RGpERAt75AJ9A3LZedm/GZlQeYAFj7SekFB+nOwCeLNhx 7019CPg9+NKi0WW3gg5fIRg= =S1z3 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] missing out source?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the Sources file says: Package: outo Binary: outo Version: 0.1.1-2 Maintainer: Tommi Leino [EMAIL PROTECTED] Build-Depends: debhelper (= 4.0.0) Architecture: any Standards-Version: 3.6.0 Format: 1.0 Directory: pool/bora/free/source Files: 0d32aefa302f4d17c652c9359f98bb79 311 outo_0.1.1-2.dsc 798eb3a03c519bd5f829775f5b219a91 171181 outo_0.1.1.orig.tar.gz 7e13ba221b3ece2dace6f6118b4acafd 255866 outo_0.1.1-2.diff.gz But I can only find outo_0.1.1-2.dsc in pool/bora/free/source. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFo2roMkyGM64RGpERApX8AJ4/HWyE37mnnJL3Q4ft8MYFkkXW4wCcDyep 0421E1ASdITTL9O3w3dF6FI= =CUFj -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] missing out source?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] schreef: Hi, Outo is open source package copyrighted by Tommi Leino. I know, and I also know I can get outo from http://outo.sf.net. BUT what I'm after is: 7e13ba221b3ece2dace6f6118b4acafd 255866 outo_0.1.1-2.diff.gz which looks like a nokia patch to outo. regards, Koen Br, Karoliina -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Koen Kooi Sent: 09 January, 2007 12:14 To: maemo developers Subject: [maemo-developers] missing out source? Hi, the Sources file says: Package: outo Binary: outo Version: 0.1.1-2 Maintainer: Tommi Leino [EMAIL PROTECTED] Build-Depends: debhelper (= 4.0.0) Architecture: any Standards-Version: 3.6.0 Format: 1.0 Directory: pool/bora/free/source Files: 0d32aefa302f4d17c652c9359f98bb79 311 outo_0.1.1-2.dsc 798eb3a03c519bd5f829775f5b219a91 171181 outo_0.1.1.orig.tar.gz 7e13ba221b3ece2dace6f6118b4acafd 255866 outo_0.1.1-2.diff.gz But I can only find outo_0.1.1-2.dsc in pool/bora/free/source. regards, Koen ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFo3CwMkyGM64RGpERAv0CAKCbj7S/0LzZZ/pgOaNm7a15G4x1AQCfZH6c V+yHUaPCuUMv0gr+d3c8hFE= =ALHH -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] missing out source?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kimmo Hämäläinen schreef: On Tue, 2007-01-09 at 11:38 +0100, ext Koen Kooi wrote: [EMAIL PROTECTED] schreef: Hi, Outo is open source package copyrighted by Tommi Leino. I know, and I also know I can get outo from http://outo.sf.net. BUT what I'm after is: 7e13ba221b3ece2dace6f6118b4acafd 255866 outo_0.1.1-2.diff.gz which looks like a nokia patch to outo. I'm not aware of any Nokia patches to Outo, so any Outo version should do... (You need it only for running some unit tests.) http://repository.maemo.org/pool/maemo3.0/free/source/outo_0.1.1-2.diff.gz :) regards, Koen BR; Kimmo regards, Koen Br, Karoliina -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Koen Kooi Sent: 09 January, 2007 12:14 To: maemo developers Subject: [maemo-developers] missing out source? Hi, the Sources file says: Package: outo Binary: outo Version: 0.1.1-2 Maintainer: Tommi Leino [EMAIL PROTECTED] Build-Depends: debhelper (= 4.0.0) Architecture: any Standards-Version: 3.6.0 Format: 1.0 Directory: pool/bora/free/source Files: 0d32aefa302f4d17c652c9359f98bb79 311 outo_0.1.1-2.dsc 798eb3a03c519bd5f829775f5b219a91 171181 outo_0.1.1.orig.tar.gz 7e13ba221b3ece2dace6f6118b4acafd 255866 outo_0.1.1-2.diff.gz But I can only find outo_0.1.1-2.dsc in pool/bora/free/source. regards, Koen ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFo3PCMkyGM64RGpERAkVRAKC3+VSRHEIIzPjuQMgDX6MZaZKmxgCeNZ9i cD1TRx9stwwlxICSJZ3jhWk= =CtNQ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building 'maemo 3.0' against stockbase libraries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] schreef: Hi, I'm interested in getting 'maemo' to build against stock base libraries when possible and use it on various non-nokia devices (including my x86 workstation, maemo-mapper at 1600x1200... drool...). We have been already working with that. I had a quickdirty demo along with me in Ubuntu Developer Summit Mointain View which was hacked together by Johan in insanely short time and was not any near production quality stuff. So it wasn't ready for anything but just showing that Hildon Desktop runs on Desktop with some hacking and it can be done. However, this thing is going to be based on the new Hildon Desktop our guys are working on (Johan, Lucas, Moises), it is not the trunk version but in branches and though it is not very mature yet. The Hildon Desktop is the package formerly named as maemo-af-desktop, we decided to rename it for consistency one day. But that is intended to become the version which is gong to work in addition to Nokia devices also on desktop Linux such as Ubuntu/Debian/yourdistrogoeshere etc. If you want to help, you might want to look to stage's branches, branch titled new_hildon_desktop. If you want send patches for it, feel free to send them to us. Thanks, I'll look into those. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFo54jMkyGM64RGpERAhJbAKC8OANE7GJUlDrCSiR1zRwDb26tpwCcD2kZ VELicJ1nvxgiLMo4e/CQQyM= =BkZu -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Translate Canola to your language!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gustavo Sverzut Barbieri schreef: I hope to see your language in next canola! :-) I hope to see the next release of canola to be opensource! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFomXkMkyGM64RGpERAuz1AJ9TNartmVwbenpNIkpmrE/YqqowbACfaMdm Scg3grzl1eL0QGocE6cE7pk= =oCTp -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Building 'maemo 3.0' against stock base libraries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Since Nokia decided that my n770 is unworthy of OS2007[1], I wanted to see how much trouble it is to compile the various maemo3 components against a stock gtk/cairo/esound/dbus/etc and run that on my 770. * hildon-base-libs built fine (yay!) * hildon-libs errored out with an implicit declaration of gtk_style_lookup_logical_color (booo, hiss!), which according to http://maemo.org/maemowiki/MaemoGtk210Changes is to provide old hidon logical color API. So, before I go on a quest to get it working and waste a lot of time that could have been spent on the control engineering course, I wanted to ask a few questions: * is hildon-libs going to depend on old hildon API forever? * if so, can someone comment on the bad thing that would happen if I rip those parts out * is there a configure option/patch available to stop using old hildon API stuff? regards, Koen [1] http://jaaksi.blogspot.com/2007/01/more-from-vegas.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFosxqMkyGM64RGpERAseFAJ9A9pVSymB588VcEPCEQlrrva1kqgCfeH+n 6wbOWfGIDworx2qiq0yRXYg= =XcUy -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Nokia's Linux-powered N800 Internet Tablet sneaks out early
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew J. Barr schreef: I wish they'd have gotten a keyboard into this bad boy...one of the reasons I like my Zaurus a bit better (not to mention the 400MHz ARM processor). An omap 24xx at 320 MHz is insanely faster as any xscale, thanks to it's vfp, dsp, iva and unaligned access options. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFoUM0MkyGM64RGpERArRuAJ96NlU5C7FljFZdTK4uh7Zn/caJWwCeII3c Hd1AU0tMTAvBPQ59/AwslTM= =TyPI -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Source availability for 'base' maemo applications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, There was a discussion in #maemo yesterday about the where to get the sources for various maemo apps that aren't in svn. You can download a 200MB tarball from maemo.org, but that requires the wlan MAC (sigh). Bandwidth challenged people can rejoice: http://linuxtogo.org/~koen/maemo/unpacked/ Have fun with it :) Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFdVaRMkyGM64RGpERArHMAJ4vgFKuqQIRogKpRCN57gyewNmPHACgjv5R gfdj7yCWbslDPiWgcrbg4Lw= =7J4e -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Taste the Herring!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Flegg schreef: On 11/30/06, Carlos Guerreiro [EMAIL PROTECTED] wrote: Hi Klassjan, Since you state applications have to be ported to Maemo 3, will Maemo 3 be backward compatible with Maemo 2.x applications? [snip] We are working on documenting the changes and on a porting guide. Stay tuned. How far off is Bora? If it's next week, there's little point in continuing to port existing applications; if it's 6 months, then I'll carry on :-) You mean like the 'Roadmap' we both have been asking for in the past? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFbrLVMkyGM64RGpERAkrAAKCZAC6E0uNaxbvVo8PYALQEQhmA5QCgvA8I YJ/GHaibKo3NxRsqAIgOiY8= =er+W -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Taste the Herring!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [I'm subscribed to this list, so quit with the reply-all nonsense] Carlos Guerreiro schreef: Officially Maemo is still that, an application development platform with SDKs, but we are experimenting with community development and eventually Maemo might develop into a community effort. I hope people will understand the difficulty of doing this, unfortunately it can't happen overnight. As mentioned on #maemo: the cynic could argue how about over a year? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFbsc+MkyGM64RGpERAu4PAJ9HtuilAfj5lHa/p0lixaSTaRENVgCguCzq 0nhAQyII6daTpg9d0J6lqJE= =RUrp -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Java on 770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Murray Cumming schreef: On Thu, 2006-11-23 at 18:02 +0200, Tommi Komulainen wrote: On Mon, 2006-11-20 at 15:13 +0200, ext Tommi Komulainen wrote: * http://maemo.org/pipermail/maemo-developers/2006-November/006188.html Java on the 770 Now that Java will be put under the GPL is there any plan (from Nokia) to integrate it into the firmware? We don't have any plans at the moment. On personal note, if someone makes nice packages it would be easier to gather some community effort around Java. It would also make our lives easier when the question about integrating Java comes up again. So, something for a new garage.maemo.org project. Then we can just apt-get install it from extras. Do we really need a garage project for something that is basically a Makefile? I can already see it happening that someone is going to but the java sources in garage svn because it's easier and we end up with a unmaintainable fork. I'm all for java packages for maemo, but lets do it in a sustainable way. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFZs5oMkyGM64RGpERAj+kAJ0YqwWOG83uHj5rtjeC3uZP8+K14ACcCfMu LxJu5aUnbWnnLfihG6nd7io= =Vfvy -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] IMPORTANT: vulnerability in ApplicationManager, please check your repositories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] schreef: It puts a serious pressure on contributors to post here, as comments coming from @nokia.com address often undergo scrutiny and start speculations. Lets keep the discussion on the technical level. We are engineers, not marketing and sales. Keep that in mind when reading our posts and please bear with us :) If so, those people should not use their @nokia.com mail address when making statements, but their own, non-work address. regards, Kien -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFQG8mMkyGM64RGpERAtRGAJ9Ar6RQ9LGbegcxzWmbJ3eTHcHM8ACfXWz/ eVEXNFB4/T887DdMNRJZzmI= =UBBF -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] IMPORTANT: vulnerability in Application Manager, please check your repositories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Weinehall schreef: On ons, 2006-10-25 at 16:24 +0100, ext Andrew Flegg wrote: On 10/25/06, Ian [EMAIL PROTECTED] wrote: maybe its more helpful to ask if there is anything we (the community) can do to help get it out of the door?? ... That presupposes there *is* another official release planned. Until we know that, how can we offer to help? If the fact that marius.volmer @ *** nokia.com *** wrote: and 4.22.1 will be in the next maintenance release of IT 2006. doesn't indicated that another official release is planned from your point of view, you live in a very twisted world indeed. No, we are just used to people from nokia saying 'a' and doing 'b'. Remember the clock framework discussion? And smartass replies from an @nokia.com address aren't creating a lot of community goodwill either. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFP4Z4MkyGM64RGpERAjNeAJ4veZxwXqewuFiqj4wqhz/dfCkd8ACfXa68 jHbqgq9Fno3iOM7L1rx4QTw= =nOUD -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Unresolved issues (Week 42)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tommi Komulainen schreef: Here is a list of issues raised on this list I think have not been concluded so far, in no particular order. The easiest way to get off the list is to provide answers, but you can also try convincing me other ways. This is an attempt to improve our communication by providing a short summary reminder for busy people to act on. I'll try to keep up with the experiment for a few weeks and see what happens. I've said it on IRC before, but will say it again where (hopefully) more nokians will see it: I really appreciate these summaries! Let's work on giving the community enough information to help themselves and the developers more time and oppertunity to give us a helping hand in more difficult situations. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFPqqxMkyGM64RGpERAk1GAJ9A7JvC3CMpoBAtaJ4MPIUsFbJrPwCfbKUp s9uzBlaEnqqsFOqjtDBQqqs= =TNhc -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Too busy to accept help?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Murray Cumming schreef: I'm not seeing any significant improvement to this situation, and Nokia's developers seem no less busy. So I'm still wasting time chasing incredibly minor patches. I still think a dedicated empowered community liason would fix this. A liason that actively comminucates, instead of passively. Things like herring are a great initiative, but if it's only mentioned on IRC after some questioning it will never be of great value to non-developers. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFOdi2MkyGM64RGpERAtvMAJ9mRvLjup8BXOC4NQlDEQnowHc0iQCdGbXL nB0DIBEMkpkjtmuKd2C8HXM= =Z1BW -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Flash player 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Malix schreef: As announced on Adobe Flash release manager blog http://weblogs.macromedia.com/emmy/ Flash 9 for Linux is here. You think that this can be used under Maemo? Before now Flash was a big pain and I had a lot of crash with older versions on Linux, but now I think that Adobe is seriously considering Linux as big OS player. Under Maemo I have a lot of browser crash that, may be erroneously, attribute to flash player, so using the new Flash player 9 may resolve those problems. What do you think? Flash is evil -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFN8ouMkyGM64RGpERAgV1AKC5MEIE9kNagkLi0qmZ02QwmcNo6wCcCjXU cDm4ODFpAP8ytBZj39BsGq4= =kgOM -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] building an application with custom kernel-headers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry Battraw schreef: I believe you need to use the capital 'I' option like so: gcc -c -Wall -g -O2 -isystem -I/usr/src/su-18-kernel-headers/include conftest.c No, -isystem is largely equivalent to -I. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFNRb9MkyGM64RGpERAoAbAJ43ItGqZZqs50SGG/oE51GRU+ZshgCaAmFZ xCkyNddk2scoh1R58cFgK5k= =6xLt -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] End-user roadmap?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Flegg schreef: Hi, I'm wondering what the plans for Maemo and the 770 are: In April we had the Maemo 2.0 roadmap[1], which was development environment and technology focussed. When the 770 was launched (11 months ago) it was with the knowledge that 2006 OS was coming. And it came. But where to now? Sardine is a lovely effort, albeit a little smelly according to #maemo. There haven't been any bug fix releases of 2006 OS in the last three months (compare with the first few months of 2005 OS!) There's a vague mention of 2007 OS in a Bugzilla comment[2], but no visible progress on user reported bugs being knocked off. What's the future with the 770? Is it worth us investing our time in it, if it is being abandoned by Nokia? Can I encourage new end-users to buy one if the software's going to stay in the currently rather unstable state?[3] If nothing else (and I understand why future hardware products wouldn't be announced) In the short term, when's the next release planned, whether that's a 2006 OS bug fix or whatever's planned for Sardine. What *is* the plan for stabilising Sardine (and the other stuff which is (hopefully) changing outside of Sardine) and releasing a new version for end users? I'm curious about that as well. regards, Koen [1] http://maemo.org/platform/docs/roadmap.html [2] https://maemo.org/bugzilla/show_bug.cgi?id=663 [3] https://maemo.org/bugzilla/show_bug.cgi?id=805 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFM8SRMkyGM64RGpERAvQoAJ9DfgCNuIhRjtTvgf5Z1hwz0TQNZgCfY0ez VF9saPFIUDNI2NVHEYA/27Q= =jw0z -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: merged some Maemo-Mapper patches
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
koos vriezen schreef:
2006/10/3, Armin M. Warda [EMAIL PROTECTED]:
Hi Cezary,
Hi,
I merged your 'GPS-Info patch' for Maemo-Mapper 1.1
http://eko.one.pl/files/n770/maemo-mapper/gpsinfo/gpsinfo-20061002.diff
with my set of patches.
Is the original project dead, there have been no traffic in SVN the
last months or so. In a forom thread I also posted a patch (attached
because link is broken) that 'fixes' my bt jam (using the method in
one of the older versions of mapper, now when a certain time no data
arrived). Also i noticed that 'g_io_channel_read_line' is a real power
consumer when lines only arrive partial, it keeps generating input
events until the eol is arrived (ironically this increases the bt jam
occurrence).
I'm a victim of the bt jam as well, so can this patch get integrated into the
aw builds as
well? Other than that, maemo-mapper-aw really rocks!
regards,
Koen
One other thing I noticed that the screen blank protection didn't work
in fullscreen mode. (I always start an extra app that does that too).
Given that I have now used mapper over quite some distances, often
more than four hours drive, and mapper w/o these patch is jammed
within 10 minutes or so, I'm starting to believe that it's rather
stable for me.
Index: src/maemo-mapper.c
===
--- src/maemo-mapper.c(revision 26)
+++ src/maemo-mapper.c(working copy)
@@ -505,6 +505,12 @@
/** The file descriptor of our connection with the GPS receiver. */
static gint _fd = -1;
+/** Track how often we fail to read a line as an indication of a bluetooth
jam*/
+static gint _fd_read_timeout_check;
+static gint _fd_read_failure;
+static gint _fd_read_timeout_timer;
+static gchar _gps_read_buf[256];
+static gchar _gps_read_buf_pos;
/** The GIOChannel through which communication with the GPS receiver is
* performed. */
@@ -1448,6 +1454,11 @@
g_source_remove(_input_sid);
_input_sid = 0;
}
+if (_fd_read_timeout_timer)
+{
+g_source_remove(_fd_read_timeout_timer);
+_fd_read_timeout_timer = 0;
+}
/* Destroy the GIOChannel object. */
if(_channel)
@@ -1468,6 +1479,7 @@
}
static void rcvr_connect_later(); /* Forward declaration. */
+static gboolean channel_cb_data_timeout(gpointer data);
/**
* Connect to the receiver.
@@ -1497,6 +1509,9 @@
rcvr_connect_later();
else
{
+_gps_read_buf_pos = 0;
+_fd_read_timeout_check = TRUE;
+_fd_read_timeout_timer = g_timeout_add(3,
channel_cb_data_timeout, NULL);
_channel = g_io_channel_unix_new(_fd);
g_io_channel_set_flags(_channel, G_IO_FLAG_NONBLOCK, NULL);
_error_sid = g_io_add_watch_full(_channel, G_PRIORITY_HIGH_IDLE,
@@ -5116,6 +5131,42 @@
}
static gboolean
+hci_cb_reset(gpointer data)
+{
+fprintf(stderr, %s %d %d\n, __PRETTY_FUNCTION__, _fd_read_failure,
_fd_read_timeout_check);
+
+if (_fd_read_failure 100 || _fd_read_timeout_check) /* recheck */
+{
+/* An bt jam - reset hci. */
+rcvr_disconnect();
+_fd_read_failure = 0;
+system(/usr/bin/sudo -l | grep -q '/usr/sbin/hciconfig *hci0
*reset'
+ sudo /usr/sbin/hciconfig hci0 reset);
+track_add(0, FALSE);
+
+if(_conn_state RCVR_OFF)
+{
+set_conn_state(RCVR_DOWN);
+rcvr_connect_now();
+}
+}
+vprintf(%s(): return\n, __PRETTY_FUNCTION__);
+return FALSE;
+}
+
+static gboolean
+channel_cb_data_timeout(gpointer data)
+{
+fprintf(stderr, %s\n, __PRETTY_FUNCTION__);
+if (_fd_read_timeout_check)
+g_timeout_add(0, hci_cb_reset, NULL);
+else
+_fd_read_timeout_check = TRUE;
+vprintf(%s(): return\n, __PRETTY_FUNCTION__);
+return TRUE; /* keep alive */
+}
+
+static gboolean
channel_cb_connect(GIOChannel *src, GIOCondition condition, gpointer data)
{
int error, size = sizeof(error);
@@ -5356,39 +5407,61 @@
static gboolean
channel_cb_input(GIOChannel *src, GIOCondition condition, gpointer data)
{
-gchar *sentence;
+gchar *sentence = _gps_read_buf;
+gsize bytes_read;
vprintf(%s(%d)\n, __PRETTY_FUNCTION__, condition);
-
-while(G_IO_STATUS_NORMAL == g_io_channel_read_line(
+_fd_read_failure++;
+
+if (G_IO_STATUS_NORMAL == g_io_channel_read_chars (
_channel,
-sentence,
-NULL,
-NULL,
-NULL) sentence)
+_gps_read_buf + _gps_read_buf_pos,
+sizeof(_gps_read_buf) - _gps_read_buf_pos -1,
+bytes_read,
+NULL))
[maemo-developers] WARNING: backups are broken with sardine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I just found out that backups made with sardine don't work with IT2006. Great. Thank you. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFI4dbMkyGM64RGpERArFuAKC52tU9RdYoQBTY4Tx/EeVdB9lfywCfYbK3 q87az/yUcj7X5mDT1mako8c= =UwjE -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] WARNING: backups are broken with sardine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] schreef: Hi, Same as extracting your IT-2006 backup on IT-2005 device - this will just not work - the backup is meant to work in the other direction. I guess I read Do not overwrite it with backups made with Sardine since these will not be reliable differently is you. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFI635MkyGM64RGpERAiPrAKCT4C85aSZ32tkBh5JhzLdAVDUrOQCffRvY lVS/LXb9diL+EjrQuRD27mA= =ejKF -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: USB 2.0 Re: [maemo-developers] speeding up MMC (with success)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frantisek Dufka schreef: Koen Kooi wrote: Frantisek Dufka schreef: Yet when usb cable is inserted kernel says something about full speed config. Unfortunately full speed is 12Mbps USB 1.1 speed. USB 2.0 is called high speed. usb 2.0 high speed = 12Mbps usb 2.0 full speed = 480MBps welcome to usb marketing speak :( Are you sure? I haven't come across this meaning yet. http://www.everythingusb.com/usb2/faq.htm http://www.linux-usb.org/usb2.html But anyway in kernel full speed realy means 12Mbps. Looks like g_file_storage can handle USB 2.0 (CONFIG_USB_GADGET_DUALSPEED) but it is not enabled. It looks like the host mode is only 1.1 (there is only ohci-omap, not ehci) but can at least the client/OTG mode do USB 2.0? Or is 'USB 2.0 device mode for PC connectivity' here http://europe.nokia.com/A4145105 a mistake? You can retroactively label usb 1.1 devices '2.0' and the pxa270 can only do 12Mbit regardless of what intel's marketing department labels it. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFIMZCMkyGM64RGpERAiwQAJ9HMCHJAJhgWNlGPK2uSM/xdQ4qAACfZgHx 4dRda2QP9CSBWxDVZDEQqs8= =J9Sj -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: USB 2.0 Re: [maemo-developers] speeding up MMC (with success)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi schreef: Frantisek Dufka schreef: Koen Kooi wrote: Frantisek Dufka schreef: Yet when usb cable is inserted kernel says something about full speed config. Unfortunately full speed is 12Mbps USB 1.1 speed. USB 2.0 is called high speed. usb 2.0 high speed = 12Mbps usb 2.0 full speed = 480MBps welcome to usb marketing speak :( Are you sure? I haven't come across this meaning yet. http://www.everythingusb.com/usb2/faq.htm http://www.linux-usb.org/usb2.html But anyway in kernel full speed realy means 12Mbps. Looks like g_file_storage can handle USB 2.0 (CONFIG_USB_GADGET_DUALSPEED) but it is not enabled. It looks like the host mode is only 1.1 (there is only ohci-omap, not ehci) but can at least the client/OTG mode do USB 2.0? Or is 'USB 2.0 device mode for PC connectivity' here http://europe.nokia.com/A4145105 a mistake? You can retroactively label usb 1.1 devices '2.0' and the pxa270 can only do 12Mbit regardless of what intel's marketing department labels it. And by the looks of it the omap1710 as well :( -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFIMZ+MkyGM64RGpERAtQ7AKCAB3G2QJhXpTCRMWiZ0Pgd4jNH9ACgqqDO NIZPq3L0XvtoaYyria/Vw+I= =K/DX -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] speeding up MMC (with success)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frantisek Dufka schreef: Yes, unfortunately current USB mass storage functionality seems to use only USB 1 speed so transfer over USB still has ~800KB/s limit. I wonder why USB 2.0 is not used. It is mentioned in N770 specs http://europe.nokia.com/A4145105 and OMAP 1710 should support USB OTG (which is IMO superset of USB 2.0 specifications). Yet when usb cable is inserted kernel says something about full speed config. Unfortunately full speed is 12Mbps USB 1.1 speed. USB 2.0 is called high speed. usb 2.0 high speed = 12Mbps usb 2.0 full speed = 480MBps welcome to usb marketing speak :( regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFH68oMkyGM64RGpERAtt5AJ9mVQK4dGBIWtCK+C6S+iJ3wiaBlwCfdLqi AFr5tB9rjCHJi7/L0oUYgLI= =50Q/ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Proposal for streamline maemo repositories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Flegg schreef: On 9/14/06, Devesh Kothari [EMAIL PROTECTED] wrote: Proposal to streamline maemo repos. PLEASE give your feedback and concerns. If anyone can improve or shoot this down, then it is YOU. Proposal: 1. To change the name of the contrib repository name to extras [snip] Impact to developers/contributors/users of contrib - Currently configured repository in /etc/apt/sources.list would have to be changed [snip] Sorry, I think you're too late. You should have considered these issues in advance, and introducing another please change your settings to users just looks a little unprofessional so soon after the EABI change (which we all agree was worthwhile, but the users don't think they see the benefit). *If* you want to make such a change, make sure you release a new firmware image that has all the changes and have a short changeover period to minimize the annoyance. And if you are going to release a new firmware image, please release an RC first to get rid of the most obvious bugs. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFCRT9MkyGM64RGpERAquiAJ45posQBexwcLGEnA3XyasOvBYbpwCeNm2k IcY4HaGuQ/SWDnKOJ3/ivhA= =0nKW -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] spam at maemo wiki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Landers schreef: The first (and perhaps most significant) is to include 'rel=nofollow' in all links, and to prominently display the following message on all edit pages Wouldn't that also keep a large part of the wiki out of google? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFBuSPMkyGM64RGpERAmYTAKCwT7jKweSnyjt69wN8tZxLwbkciQCgvcgq fknNgg2UiGrD85Oaeld3ChU= =uHob -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Sardine releases feed working again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carlos Guerreiro schreef: Hi, The Sardine releases RSS feed (http://repository.maemo.org/sardine/rss20.xml) is now working again. It was broken for over a week due to insufficiently robust parsing of the changelogs in the feed generator. I hope I got that right this time ;-) That's very good news! I have just one request: Can the 'Fixes: NB#37947' tpye messages be a bit more verbose? I love it when bugs get fixed, but a bug-title or summary would even better :) regards, KOen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFAxlnMkyGM64RGpERApBuAKC0R6tbQnSILFl5VnQ2fF5zPyJcbgCgi2Bt nyBPXsjlEVqbV+9ezR3D1Gg= =Xx7R -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Touchscreen API
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastien Bourdeauducq schreef: Hello, I'm trying to port Qt Embedded and Opie to the N770. So far, I have managed to stop the X server and have the example Qt applications running straight on the framebuffer. However, I still lack touchscreen support. The device node seems to be /dev/input/event2 but nothing happens when I configure Qt to use this device. Running cat /dev/input/event2 and playing with the touchscreen does nothing, contrary to other input devices (ie. when you move a mouse, the screen gets covered with garbage). I have tried every node in /dev/input/, they all behave the same. You need tslib and some patches to unbreak the broken qt/e tslib handling. I suspect the opie(-devel) mailing lists would be a better place for your questions, since maemo-developers is a mailinglist dedicated to the GTK+ based maemo environment :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFAC2+MkyGM64RGpERAj7uAJ9c/awEhuSRyJXBJ7RPjApX3e97OACfYS50 zcuPwpNp4i2KwIPAKtFT/MM= =RNQL -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: Sardine build environment broken?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carlos Guerreiro schreef: I was able to upgrade it on a i386 scratchbox though I had to forcefully install (dpkg --install --force-all) libbluetooth2 (a known problem). Bug #750 for the curious :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE/dlMMkyGM64RGpERAjv0AJ9z+2Lt3+MkxeTZIeRFf+HdEQSZNQCdE1mg m9dy5lDPzzTC4BSRjD/OH7I= =LE4U -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] kernel code
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kalle Vahlman schreef: The version in IT2006 is http://repository.maemo.org/pool/mistral/non-free/k/kernel-source-2.6.16/ Non-free !?!? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE+oqIMkyGM64RGpERAscZAJ48SRyV9LT4bHZp88OcMfbUjbzPGACcC2FV xp9tiNb0Fv8S7nhbF0U35vY= =JdVA -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Scratchbox is not an emulator
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eero Tamminen schreef:
snip
1. cross-configure Autotools (autoconf, automake etc)
using Linux desktop software, nor tried to
2. cross-build Debian packages
1) Is something that only OpenEmbedded provides in addition to Sbox
and even with OE, you need to create a specific recipe for the package
build to succeed (I think). For problems with SW using Autotools, see:
http://www.scratchbox.org/documentation/general/tutorials/explained.html
To expand a bit on that: in OE it should be a matter of doing 'inherit
autotools'[1][2],
but that only works if people didn't hand edit the generated configure file
afterwards or
include bogus macros in aclocal.m4.
And once you enter the realm of crosscompiling you will notice that people make
stupid
assumptions[3] and do -I/usr/include into the Makefile.{am,in}, and guess what,
the
arm-gcc compiler chokes on x86 asm from that headers.
Scratchbox makes life easy for developers since it's the closest thing you'll
get to
native *compiling* you'll get on your workstation. If you want to thoroughly
test it, you
can't escape using the device (with or without cpu transperency), and you still
have to
package the stuff yourself. If you just want to have a package, OE would be
right for you,
if you want to develop 'natively', scratchbox is the way to go, but there is no
'click
this button to do everything' solution yet.
Koen
[1] http://www.openembedded.org/user-manualdpage=ch02s04
[2] http://www.openembedded.org/user-manualdpage=ch07#autotools_class
[3]
http://www.openembedded.org/repo/org.openembedded.dev/packages/gimp/gimp_2.3.10.bb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFE9U8aMkyGM64RGpERAlDvAJ9RtXXmbPED5tU+EfflfGLl147emgCffHF8
3DY7gW97phjpqLjhCFQyAPs=
=mcVQ
-END PGP SIGNATURE-
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RE: Nokia 770 sources...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kalle Vahlman schreef: Hmm, I've always been under the impression that any kind of combination of binary-only and GPL code would be in violation... IANAL of course. Slightly a different issue, but a nice read anyway: http://www.kroah.com/log/linux/ols_2006_keynote.html closed source kernel modules are unethical regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE9cnGMkyGM64RGpERApQIAKCSBPxJkcuhGUClj2k1lwfgHQPIVwCdHJ/f YJb/wto/FZHSDPML2vMohrI= =jowI -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] library updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adrian Neumaier schreef: I suppose you read this: http://www.debian.org/doc/maint-guide/ on how to build proper debian archives. But for that lib problem: it can't be too hard to write a control file like this: snip Build-Depends: libfoo-dev ( = 1.0.0-1), bar (= 1.0.0) /snip This will pull libfoo in a package version = 1.0.0-1 from the archive whilst installing via apt-get install (i suppose this works with this graphical installer too *g*) If libfoo 2.1.0 is in the archive this will still work. If the archive has two libs, same name, but different abi then the libs look like this libfoo1 (this has soname 1) libfoo2 (this has soname 2) so in the end if your software needs libfoo1 you add to the build-depends libfoo1-dev (= ) whilst software which uses libfoo2 has libfoo2-dev (= ...) in the build-depends. Cute, but the real problem is something different: Day 1: Florian uploads gpe-calendar 0.99-12 + libeventdb1 0.36-17 Day 2: Neal fixes bug in gpe-calendar, florian upload 0.99-13 Koen uses the AI, gets the updated calendar and rejoices Day 3: Neal fixes a bug in libeventdb1 without affecting API or ABI florian uploads libeventdb1 0.36-18 Koen uses the AI and doesn't get the update, and is sad Day 4: Florian upload libeventdb1 with a Section: user/lib Koen uses the AI, sees the update, and is happy I hope this clears it up a bit :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEwIU5MkyGM64RGpERApoJAJwPkkuuDKieaU86X5795RKkg1LfrACeLygR 0FOXdY33pjTtc+KZt0SRkJw= =kJWy -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] library updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adrian Neumaier schreef: What was the section before? just lib? Afaik a section user/lib isn't available in debian :) Neither are packages for armel ;) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEwOzXMkyGM64RGpERAnA/AKCycluSd9933be36joqYTTMx5y+ZwCeIvS7 4xFVZId/1bXyKVcFzSOVgs0= =PjPp -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] GTK2.8 ??
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kalle Vahlman schreef: 2006/7/20, [EMAIL PROTECTED] [EMAIL PROTECTED]: As far as I know, the current SDK2.0 and IT2006 is based on GTK+ 2.6.10. Is there any roadmap that GTK2.8 with Cairo would be employed for further software releases? http://maemo.org/maemowiki/MaemoGtkRoadmap states that it's unfeasible in the short term, so probably not soon. naive Hasn't gtk 2.10 fixed all those problems? /naive Regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEvyYeMkyGM64RGpERAndKAKCdLA5dVcCg+G2LaH/WdqYGTHm6wwCgm5Fm wgf1FLmCkt3dmQpZCzj8HYs= =JNmJ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] GTK2.8 ??
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Robinson schreef: On Thu, 2006-07-20 at 06:29 +0300, ext [EMAIL PROTECTED] wrote: As far as I know, the current SDK2.0 and IT2006 is based on GTK+ 2.6.10. Is there any roadmap that GTK2.8 with Cairo would be employed for further software releases? It depends on performance, we're looking into it. It's not much fun to be stuck with unmaintained series. However we'll probably skip 2.8 now that 2.10 is out. I think the perforance will improve with whatever release of GTK supports cairo 1.4 which is suppose to be the 'performance release' so I think that'll be the one to look at. Also the OLPC project work should also assist in getting the performance we're after which will be nice. The OLPC has an FPU, the 770 hasn't, so unless cairo grows a complete fixedpoint backend + renderer it will always be ~10 times slower as the good'ol gtk 2.6.x regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEv0JvMkyGM64RGpERApWyAJ9BWNb24Xd/FDZijm93B/SBnPJBuACeOlzX Yx0L+DAN4o1N4nM2RkU6xhc= =Vkca -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] GTK2.8 ??
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gustavo Sverzut Barbieri schreef: On 7/20/06, Koen Kooi [EMAIL PROTECTED] wrote: The OLPC has an FPU, the 770 hasn't, True so unless cairo grows a complete fixedpoint backend + renderer it will always be ~10 times slower as the good'ol gtk 2.6.x False, Cairo itself is all fixed point/integer math, however their API expose float point parameters, which are converted to fixed internally. Using soft-float here may help, since we'll get no TRAPs to kernel do it for us in software. But being fixed point doesn't make things fast on its own. Maemo already uses softfloat and it's still slow. Carl (cairo guy) said that he was taking care about API, not the core, so he did the whole thing naively, however correctly, and will optimize later... since Carlos (nokia) did give him a 770 in order he can test it, we may expect something great really soon. Don't count on it, Carl has had a long history of playing with arm based machines, even before cairo was started. But we'll see, but I won't have high hopes, even if I *really* like cairo. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEv2pRMkyGM64RGpERApNSAKC3PQuxyo8v0puTf8i29nsWVIUCmQCgpBQU kaEE8gMnGX0KJe6sUI1xw5c= =X4AM -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Internet Tablet OS 2006 final at maemo.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ferenc Szekely schreef: Hello, Nokia published the final release of the 2006 Software Edition. The image is available at http://maemo.org/downloads/nokia_770 . Cool. Happy flashing ;) Can't we apt-get distupgrade it? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEpVsCMkyGM64RGpERAtjvAKC37NddMo2T6iFYTjJti77L1jqy9wCgpbIM UCKd6I+elxVcEBHGdYZiRx4= =wa2I -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Changes to GTK
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Madhusudan E schreef: This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! Ehm. Shouldn't e-mails containing crap^H^H^H^Hstuff like this be discarded? With stuff like gmane, google-groups and list archives maemo/nokia is in for a world of hurt, legally speaking. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEfX01MkyGM64RGpERAia+AKCCufGm5KmaP+Bck98/ln4mGx1lUACeLgB6 2pLCcNmXxeFKKxAmsJsG3Ac= =bXC1 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Happy birthday Maemo!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greg Morgan schreef: snip MoinMoin wiki is ok. Would you also consider switching MoinMoin to MediaWiki http://www.mediawiki.org/wiki/MediaWiki at this point in time. If you were worried about using a database with a wiki Database? It only supports mysql, which I wouldn't call a database, it's more like a fast way of loosing your data ;) regards, Koen and selected MoinMoin because it was file based, then you may want to consider mediawiki with the advent of the garage. MoinMoin was the first wiki I ever used. However, MoinMoin seems limited in the type of documentation that can be produced by it. Thanks for listening to the suggestion. Thanks, Greg ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEeJytMkyGM64RGpERAkoEAJ9k9C6U8kqArcchRudtICg/oRBhswCfcZSy rHHgeVwrM8rPopPnczDPd+I= =Mh6E -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] http://press.nokia.com:80/PR/200605/1051308_5.html
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, In case anyone missed it: http://press.nokia.com:80/PR/200605/1051308_5.html The biggest error in the statement: It is downloadable free of charge from the Internet www.nokia.com/770. nokia.com only has IT2005 downloads :( regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEaXsbMkyGM64RGpERAiBNAKCoCa78FXVd2iOUfoMDYhK64qHmigCaAuvE CrgO5MdKsud9/Hz7UU22fyg= =9jXc -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers]http://press.nokia.com:80/PR/200605/1051308_5.html
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nils Faerber schreef: Devesh Kothari schrieb: I also think it would be a good policy that the community will always get information first before official press releases ;) The only actual news was integration with gizmo and a commitment to deliver it in june, the rest[2] has been on http://maemo.org/platform/docs/roadmap.html for some time now. regards, Koen [2] and on the debian-arm and maemo-dev mailinglists as well -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEacPgMkyGM64RGpERAmLrAJ9uOeXQlgUrA2Az60TPp3CKZfPp1ACgtMRr fNsiL4rk3M43kBmt5gcPNZY= =5hvJ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] New 2006 software version on tuesday?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nils Faerber schreef: Hi! German Heise IT newsticker just had a quite confusing report about the new 2006 edition of the software (the article even suggests that there will be new hardware announced!?). The old media had a saying: verify, verify, verify. It seems that every news-site is copying the original post without checking. They claim that the new 2006 software edition will be announced next Tuesday. Is that correct? Will there be corresponding donwloads on Tuesday too? I have to admit that I almost cannot await it ;) Same here! Can't wait for another developer discount ;) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEZ2G9MkyGM64RGpERAtB+AKC4hx7TgjymoXHCJoxXE4/B3+g5VACfUbt7 f8nD4SjgNHwqpaBJjJJdK4M= =qXGt -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Bugzilla annoyances or we at nokia don't have a 770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, During the last few days people have voiced their annoyance with how nokia handles maemo bugs. Please take a look at the responses from Maemo QA in the following bugs: https://maemo.org/bugzilla/show_bug.cgi?id=184 https://maemo.org/bugzilla/show_bug.cgi?id=264 Don't you have a 770 with the latest consumer firmware at nokia to test it yourselves? And more importantly, why is it taking so long to ship a firmware with working timezone for places other than Helsinki? slightly annoyed, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEV12wMkyGM64RGpERAu2vAJ9/ncHhKr91ETYZJCbLtYZJjTkrLwCgrmE1 zEu5NGxy2vQEksr7wai5MrY= =Es6S -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] gcc options for smallest size, best speed, etc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Clemens Eisserer wrote: Hi, I'd expect -g -Os to do all appropriate code size optimisations regardless of the architecture. Well -g is a bit stupid in this scenario, since this means you tell gcc to optimize for size but include debugging informations too. I would recommend -O2 as the best option to use. It does a fine job deciding wether a optimization is really worth the extra bloat, which is especially important when it comes down to the small i-cache the N770's processor has. - -Os uses the same optimizations as -O2 but takes size into account, so that should be even better for small caches. From my tests -Os is sligtly faster as -O2 since you need to load less from jffs2 (less zlib stuff). regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEUfAsMkyGM64RGpERAg4QAJ9foVR72/3hV/YGPOXHO24kEO/sFQCdFIBx nm4+tMzQSGRs/dNCVShAFF0= =DQOO -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] gcc options for smallest size, best speed, etc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philippe Laporte wrote: Hi, I would assume that this list be a top source for the following question: what are the compile options for ARM for gcc for the smallest possible size, etc. For both smallest size, and best speed, seperately of course. Or where should I look? Have a look at http://free-electrons.com/articles/optimizations/ , that explains the most commonly used optimizations. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEUIyAMkyGM64RGpERAvvoAJ9rVeBogUkxZM+BuB1LmkEcb1nw/QCgtuXs xhjNNDCWmQWlfRXLI8MRpX4= =Y58a -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jussi Kukkonen wrote: snip Great, looking forward to it. On a somewhat related note: Would it be a bad idea if the maemo-commits mailing list posts included the full diff? Following the changes via the list is currently a little tedious since it requires constantly changing from email-app to browser and back... And can it a trigger be added to inform http://cia.navi.cx/ so we can have rss feeds and maybe an IRC bot to announce commits? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEMQWYMkyGM64RGpERAp3uAKCH3wqXYfDsh41gfMjLOngIuMwiLQCfalb0 Qw4+svBk7yiflAAH1SkstzU= =yAWY -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] OGG support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Juha Yrjölä wrote: On Mon, 2005-10-31 at 13:53 +0100, ext Koen Kooi wrote: What's nokia's position on EABI[1]? At least this part of Nokia thinks that EABI is cool. It seems you have company*: http://lists.debian.org/debian-arm/2006/03/msg00058.html regards, Koen *pun intended -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEK58bMkyGM64RGpERAnW3AKCMnxmEEy7GlPASKqLXtKYicyrA4gCfTzI9 Kfh63qQkSTfhWn04DNxN1i4= =3pxR -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] New Software Version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Flegg wrote: On 3/30/06, Peter Robinson [EMAIL PROTECTED] wrote: Does anyone have a date on when Nokia expects to release the next version of the software? I've seen Q1 2006 a few places, but I'm curious if anyone has any more concrete information. Nope. [...] Although it would be nice if they'd start releasing some alphas of the corresponding Maemo release [...] Especially since there are API changes and the Application Installer is not going to be backwards compatible. As well as a complete new ABI by the looks of it. End users who upgrade immediately are going to have zero third party software they can install if there's no early developer release. That would be a pretty good way to poke the community in the eye regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFELASnMkyGM64RGpERAjK3AJ9b0RMBic6VtJQB3cGjBcLwyuw/YQCcCdKf 4xwwN61V4Z0ijZxn9jnrrII= =UmKJ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Optimized memory copying functions for Nokia770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Pickering wrote: snip benchmarks I think I can explain the difference between the two zaurus benchmarks: Xscale cpus really need the -mtune=xscale parameter to take advantage of the pipeline, which AFAIK gcc 2.95 doesn't know about. OZ 3.5.4 also uses a recent 2.6 kernel (.14 or .15) which has the copy-page locks removed, so memory access is a lot faster compared to 2.4 and 2.6.smaller as 14. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEInsxMkyGM64RGpERArTFAJoC6aj38bYBdg4zv8iz6r3JwW5SsgCfcidV 5knI63wki0VasW2x0I+/mio= =H2YS -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] J2ME on Nokia 770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Hello, I've read some discussion on that list about the possibility of running J2ME MIDlets on Nokia 770. As I've found, the problem is because of lack of J2ME implementation for that device. I'm an author of MicroEmulator (http://www.sf.net/projects/microemulator) - pure java CLDC/MIDP implementation. I think it would be possible to create port of MicroEmulator on Nokia 770 to fill that gap. If anyone is interesested in that please send info and I could look into more deeply. gcj now works on arm as well. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEDXx0MkyGM64RGpERAiNIAKCi2M7BCOC1algXH7ebe+R2aZUtOgCdFeKK iuT1fWrmsjcEIfjFe6/xFGQ= =btld -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Adding swapon/off to Jakub's Load-Plugin applet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Armin M. Warda wrote: On Thursday 23 February 2006 01:34, David D. Hagood wrote: [EMAIL PROTECTED] wrote: Any suggestions? How about hooking swapoff to the hotplug event for the MMC card cover opening? Maybe even insertion also. Yes, I really would like to try this, but I do not know how this has to be done. Can anybody lend me a hand? (Of cause I would make this feature optional, with an enable/disable checkbox in the settings.) Yes, *please* hook the cover open/cover close events and enable/disable swap as appropriate. But this will only make sense for a swap living on the RS-MMC. If you are running with a swap file on the internal flash, you would not want to swapoff when the RS-MMC lid is opened... Please tell me I'm reading this wrong: 'swap file on the internal flash'. You do know that flash is broken after ~100k writes/cell, right? And you know that will break your 770, right? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD/bTGMkyGM64RGpERAsnLAKC3ev+fcJMjURrWC2QVedBpsp6JIgCdErIw ufGwdwWFKeF3mxnPynWywHc= =GXOS -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] hildon-lgpl is now gone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Hi Devesh, snip We still provide a dummy hildon-lgpl package requireing hildon-libs, to preserve compatibility A few other changes are planned for the coming weeks, adding new APIs, we will provide then migration instructions. Is there any ETA on the new APIs and such? I'll have some time in the next weeks to update the maemo 1.0RC bits in OpenEmbedded to a recent 'release', but as I'm lazy I want to do it right the first time :). regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD9LewMkyGM64RGpERArGuAJ0W/zy7JKzzYlwRFRMpNdeNsSpxLQCffQZE HV9DnDqySmb/t23lqjsSqPQ= =oBHu -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: testing pango with 770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eero Tamminen wrote: Note: In Maemo UI user cannot resize windows and applications themselves do that very rarely for dialogs, so this is fairly moot point for Maemo. Try popping up the vkb. Opera takes ~4 seconds to resize the first time. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDtFsJMkyGM64RGpERAsekAKC5UhvLKHVxLL8SHFq8dT2vePFYAQCfeFZ9 7EAK01TeKkiFyDG230Yew+0= =Bw+t -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: testing pango with 770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Clemens Eisserer wrote: It's disappointing that with every release gtk gets slower... I absolutly agree - GTK-1.2 has been a nice and fast toolkit but since the jump to 2.0 GTK is just one of those too-bloated-to-be-tuneable pieces of software no one wants to touch since it could break something. This thread is pretty funny. Nokia tests 1 version of gtk with different versions of pango and suddenly people say that *different* versions of gtk were tested and jump to conclusions Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDsoXtMkyGM64RGpERArTqAJ9mRUbj319IHPfzaThsxgTEmhrbigCgq+H+ z7vbZmBclp2XCeKnkr+Nvu8= =gn8L -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Java jamvm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Clemens Eisserer wrote: Hi again, xfwm suffers from this bug as well, so I'm inclined to lart the gtk people, but they are probably too busy breaking ABI/API right now :( So this is definitivly a bug in maemo's X server? No, this is a bug in the assumptions GTK makes about bitdepths. Thanks a lot for replying, lg Clemens ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDsQ3KMkyGM64RGpERAtcXAJ0euSaadR1GWsUTlf7ZIe//C8E67QCdGUPg NpJP20Ru9BSI8mB2rOGk/20= =7qSC -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Java jamvm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Clemens Eisserer wrote: Hello, If you search the list a bit, I reported this problem some time ago but sadly was not able to fix it or to figure out whose fault this problem is. The java-gtk peers create a pixmap with 24-bit depth (as suggested by gdkrgb) and a pixmap with this depth can be created but asking for a colomap fails. I already asked at the gtk-users and gtk-devel lists as well as on meamo-developers but no one thinks that this bug is his fault. xfwm suffers from this bug as well, so I'm inclined to lart the gtk people, but they are probably too busy breaking ABI/API right now :( regards, Koen The GTK-devs say that there should be a colormap available if GDKRGB returns this bit-depth as preferred value, Maemo-devs say that there is simply no colormap assigned (and how could I assign one?). There were other problems as well (no expose-events were sent to the windows if overwritten by hildon-menus) so I gave up trying to fix that. I also did not receive any useful help from the Nokia nore the GTK devs. I am not a really good coder, so I hope you get it done, good luck! lg Clemens 2005/12/22, Andreas Langhoff [EMAIL PROTECTED]: Hello to all, I am interested in running a Java J2SE trading platform on the 770. Jamvm as a virtual machine is installed, but at launch I get the following fatal errors: jamvm[1153]: GLIB CRITICAL ** Gdk - gdk_colormap_alloc_colors: assertion `GDK_IS_COLORMAP (colormap)' failed java.lang.InternalError: Gdk: gdk_colormap_alloc_colors: assertion `GDK_IS_COLORMAP (colormap)' failed at gnu.java.awt.peer.gtk.GdkGraphics.setFGColor (Native Method) at gnu.java.awt.peer.gtk.GdkGraphics.setColor (GdkGraphics.java:372) at javax.swing.JComponent.getComponentGraphics (JComponent.java:890) Will there be a fix in the future? Best regards Andreas Langhoff ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDsEV5MkyGM64RGpERAojBAKC0nPDX8cM3asaj+ZwI3rpDk4glgwCfU92J QlP6Fe819HLJx6AfNVKlJo4= =LLOQ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Luc Pionchon wrote: Hi, On Tue, 2005-12-20 at 16:29 +0100, ext Erik Bågfors wrote: My first thinking when it comes to this is to port maemo to an existing machine, such as a IPAQ which already runs linux and today GPE. Sounds like a great idea. Did anyone out there give it a try already? It's as easy as pointing $DISPLAY to your handheld: http://dominion.kabel.utwente.nl/koen/blog/pyblosxom.cgi/2005/May/29 regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDqVi+MkyGM64RGpERAveKAJ9b9K8gIy1y2ePBylxVtUHCY4YlUACeIg1e C6JzxrdrXmck7OPHZYMqBZ0= =Vc2D -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eero Tamminen wrote: Hi, that an interesting screenshot because it illustrates some basic scalablility issues even at 640x480 which isn't that different from the 770. Is there anything that couldn't be fixed just by finetuning the theme files i.e. without touching any code? The titlebar is just single large image. By: - changing titlebar gfx to uglier tiled one, and - setting statusbar panel to more suitable position in the Matchbox theme should fix the most obvious problems. There would still be the problem that application title will have very little space to show the text. Porting Maemo to a common 240x320 PDA will be challenging I think you'll need completely new application layouts, or in case the physical screen size is the same, just make the font much smaller and fine-tune the theme files. If maemo had a notion of DPI this would be much easier, but as Tommi pointed out, requires us to fix most of the internets css files :( regards, Koen - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDqXRiMkyGM64RGpERAvzwAKCOvxnmexTQ4AmJ0VEVtFXEqBU35gCeNLT7 7TE72WvHWxcxd8WWU4RsxwA= =kGX6 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] screenshot tool?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eloi Crespillo Itchart wrote: CPU/Mem/Screenshot applet Home Page: [WWW] http://koti.welho.com/jpavelek/tmp/770/ This is starting to be a very recurrent question... It just proves people are too lazy to read either the FAQ or http://maemo.org/maemowiki/ApplicationCatalog (system-tools - CPU/Mem/Screenshot applet) Koen On Monday 12 December 2005 19:37, Shawn Gordon wrote: Hi, We've been hunting around for a tool to take screenshots on the device but haven't found one. Any suggestions? thanks. Best Regards, Shawn Gordon President ProgRock Records www.progrockrecords.com www.mindawn.com (949) 713-3276 --- Tune into the best progressive rock station on the planet - ProgRock.com at http://boa.mediacast1.com:9288/prog1.ogg ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDoAyXMkyGM64RGpERAgDHAKCPTnt+efLLtLsE+UySinfqitCcfwCfUIEz BDRCpFDR8OtMn9PbYNpXm1A= =P1f5 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] bluetooth keyboard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frantisek Dufka wrote: Hello, just to let you know. I've got uinput.ko module compiled and got kbdd working with my iPAQ bluetooth foldable keyboard. Now I need to add some gui. Either to integrate in into existing keyboard applet or create new one. You could use the gui gpe uses as a start: http://handhelds.org/cgi-bin/cvsweb.cgi/gpe/base/gpe-conf/keys/keyboard.c?rev=1.10content-type=text/x-cvsweb-markup regards, Koen kbdd + uinput module binary is here http://fanoush.webpark.cz/maemo/kbdd.tgz diff to kbdd for btfoldable type is here http://fanoush.webpark.cz/maemo/btfoldable.diff No README, description how to make it working is here http://handhelds.org/moin/moin.cgi/kbdd but you need to insmod the uinput.ko module first (as root). It would be great if Nokia could add uinput module to standard N770 kernel. Regards, Frantisek Frantisek Dufka wrote: Tomas Junnonen wrote: However, the kbdd program (http://handhelds.org/moin/moin.cgi/kbdd) mentions supporting your keyboard, and I can't think of any immediate reasons why this would not work on the 770 with a bit of hacking. Just tried binary from http://familiar.handhelds.org/releases/v0.8.2/feed/base/kbdd_0.8+cvs-20050331-r3_arm.ipk and it need uinput kernel driver. Nokia770-43:~# ./kbdd -p /dev/rfcomm0 -t foldable failed to open uinput device: No such file or directory init uinput failed If someone has nokia kernel source lying on his/her computer and would compile module from http://handhelds.org/cgi-bin/cvsweb.cgi/linux/kernel26/drivers/input/misc/uinput.c for me, that would be great. If not, I'll try this as soon as possible (probably this weekend). BTW, I managed to pair the keyboard, connect to it and got some garbage from /dev/rfcomm when typing on keyboard so it definitely works and hopefully needs only kbdd running with proper kernel module. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDlVJtMkyGM64RGpERAoGnAJwP03XYWwV8FboXbwSFWKUcs/fYhQCeMpXN Xfo+8zKWHugfZjof/Wndq/g= =P8Wm -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] ipkg vs dpkg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zeeshan Ali wrote: Repeat after me: the 770 is not an embedded system. It is a small computer with neither a qwerty keyboard nor a big hard drive, nor a really fast processor. You are kidding, right? Anything is an embedded system if it: 1. has a small memory and secondary storage 2. has a slow processor 3. is intended to serve some 'specific' purpose(s). Most of the computers I owned (from XT to the first ibm cyrix CPUs) have a slower cpu, less ram and less storage than the 770 and served some 'specific' purpose(s) are these embedded systems too? Are the new sharp pda models (400MHz Xscale, 64MB ram, 4GB microdrive, keyboard) embedded systems or not? The label 'embedded' is fuzzy and in boils down to 'no real keyboard' most of the times. How do you define an 'embedded system'? I usually try not to :). The term 'embedded' gets misused almost as often as people calling NAND/NOR flash 'ROM'. regards, Koen -- Regards, Zeeshan Ali ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDjD+NMkyGM64RGpERArESAJ98njJmeyfGfZ/iA1cYm6KW2ketjwCgktp7 pu1/0i3unSoP0n5pDJeSxGk= =/C5R -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] ipkg vs dpkg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kalle Vahlman wrote: 2005/11/29, Matthew Allum [EMAIL PROTECTED]: the 770 is not an embedded system - OK :) You understand my point though - we could argue all week on if my digitial watch for example was a small computer or an embedded system. And that wouldn't resolve the real issues with the device which are the RAM shortage and less-than-optimal graphics performance wrt screen size. tar cfz - /var/lib/dpkg | wc -c gives somewhat less than one megabyte on the SDK, and I expect it to be about the same or less on the device (if it indeed had the dpkg stuff there, the product image does not currently). So we are talking about changing a rarely used utility to save less than one percent of the flash space? With modifications to who knows what amount of the packages included? I wouldn't call ipkg rarely used, Familiar, OpenZaurus, openwrt, SlugOS, pdaXrom, sharpROM and several other distros have been using it for years. Or is ipkg a drop-in replacement for dpkg, requiring no changes to build environments or the packages themselves? a .ipkg should be compatible with a .deb (ar wrapped tarballs). See http://handhelds.org/moin/moin.cgi/Ipkg for details. Iirc ipkg should be able to install .debs and dpkg should be able to install .ipks. Could you specify what you mean with 'build environment' and 'packages'? Could I apt-get source foo from a Debian repo, compile the package for ARM with an utility like dpkg-buildpackage and stuff it to the device like I can now (from the command line, and if AI would support real debs from it too)? you can, ipkg-buildpkg will do the grunt work for you. Systems like OpenEmbedded will make live even easier by autogenerating control files. -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDjFIgMkyGM64RGpERAhQBAKCM+rt1TrVXArSCnstjky8ywvtMLwCfbB/O mIIkCyXGFscpeFR0Ne1cmb0= =bUgo -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] ipkg vs dpkg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tomas Frydrych wrote: Kalle Vahlman wrote: Build environment as in the Maemo and packages as in the existing dbus/ dir contents (bad wording, sorry). If you need to port all of Maemo to a new pkg management just to use ipkg, well... Granted, you need to recreate the packages for AI currently too so perhaps it's not an issue. In fact, there is very little involved in making a deb package work with the AI -- if your app is well designed, you basically just need to pass --prefix=/var/lib/install/wherever_you_want_it to configure, and make sure to replace any standard system dependencies with the 'maemo' dependency; there are useful scripts in ApplicationCatalog to help with this. So far in this discussion nobody has been able to demonstrate any genuine advantage to using ipkg over dpkg on the 770. ipkg resolves dependencies like apt, dpkg can't. regards, Koen More significantly, the dpgk is already on the system and maintains a database of installed applications. It really escapes me what the issue here is, other than Nokia wanting to keep the system (under /) completely separate from the applications installed by the AI (under /var/lib/install) -- unless Nokia changes this policy, there is not much to be discussed; your packages need work with the AI. Tomas ___ Yahoo! Model Search 2005 - Find the next catwalk superstars - http://uk.news.yahoo.com/hot/model-search/ ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDjGykMkyGM64RGpERAvwJAJ4r8XXLlpG7AnApzGqb09X8TJ9S8gCgkAcQ HvTtwoz9iCnCI800xDMKKj8= =4WqI -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Debugging on virtual 770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antti P Miettinen wrote: Kimmo Hämäläinen [EMAIL PROTECTED] writes: It's also possible to attach gdbserver to a process on the 770 .. Or, how about debugging on a virtual 770, now that qemu has system emulation support for ARM [1]. Well - this would probably be more useful for kernel debugging, but anyway - if someone is looking for a project, how about implementing emulation for some 770 peripherals :-) In case someone is interested in adding OMAP1710 specifics to the qemu ARM system emulation, it might be useful to know that 1710 seems very similar to OMAP5912. I haven't been able to find 1710 docs from TI web site, but 5912 docs are available [2]. Isn't the OSK 5912 just a starterkit for the omap 1710 cpu? regards, Koen [1] http://article.gmane.org/gmane.comp.emulators.qemu/9963 [2] http://focus.ti.com/docs/prod/folders/print/omap5912.html -- www.iki.fi/~ananaza ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDiM6mMkyGM64RGpERAq3TAKCahcKMo2n+axU4J/1hgtzvRhvingCfQmLh uVgip+cEZZBppBgVUqYjgms= =1dlJ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] rotating the screen (was: Maemo and Independent software vendors or commercial software vendors)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eero Tamminen wrote: Hi, The screen is brilliant and bright enough for day use. However it is currently not possible to rotate the content. In the SDK it's easy to test how rotating the screen affects Maemo. Just use 'xrandr' to rotate / resize the Xephyr screen and see how the SW and gfx works in portrait mode... If HW doesn't support rotation, all operations need to go through X shadow framebuffer which can slow down things considerably. Matthew Allum pointed me to a patch that can help with this sort of thing: https://bugs.freedesktop.org/show_bug.cgi?id=4537 We are using an adapted patch for kdrive in OpenEmbedded for devices where the real framebuffer doesn't match the orientation of the screen. regards, Koen - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDa1BOMkyGM64RGpERArxVAJ4v1ZDf0Pxjfs1KlJ9HrZ1IjPePDgCfUM0v GrlBZ0EjW5JPaPQ/H46axFs= =5mcl -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] OGG support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Grimme wrote: Hi, Am Sonntag, den 30.10.2005, 11:10 + schrieb Clemens Eisserer: Wow, really great someone is really doing it finally, although I can't really underand why they did not include it in the default distribution - ogg is THE next generation audio compression format. I am looking excited foreward to test the first version! I think the reason why Nokia didn't support Ogg until now was that the standard Ogg decoder heavily relies on floating point operations and is thus way too slow on the Nokia 770. The alternative integer-only decoder Tremor doesn't have a gstreamer plugin yet. Nonsense, gst-plugin-ivorbis has been around for a while now. The only problem is that the gstreamer people forget to apply small API tweaks every time gstreamer gets improved. Cristian has mentioned (http://blogs.gnome.org/view/uraeus/2005/10/28/0) that they will port ivorbis to gstreamer 0.9. regards, Koen Personally I do not care which project is used as basis as long as: - The package does not use too much flash space when installed ( 3mb or so) - Can handle playlists - Would be great to have: volume management using the dedicated buttons ;-) I have a player like this in mind. :) But I also wouldn't mind Nokia porting the Tremor decoder to the DSP. ;) Regards, Martin ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDZL4yMkyGM64RGpERAn5fAJwNjWVNgWtt8PqA2p6iJd7JIZ6LnwCgrDFv Uf8IOgCJmYUG7l40tZ1ufc8= =ehRU -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] OGG support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zeeshan Ali wrote: Hey buddies, Nonsense, gst-plugin-ivorbis has been around for a while now. The only problem is that the gstreamer people forget to apply small API tweaks every time gstreamer gets improved. Cristian has mentioned (http://blogs.gnome.org/view/uraeus/2005/10/28/0) that they will port ivorbis to gstreamer 0.9. 'small' API tweaks? Are you familliar with the changes between 0.8 and 0.9 for plugin writers? I was getting at 0.8. The ivorbis plugin doesn't play nice with playbin, while other plugins do (the mad one). This is currently stopping GPE from having reliable ogg support on arm based handhelds. The main point of my reply was: there is an ivorbis plugin, so stop saying it doesn't exist. regards, Koen -- Regards, Zeeshan Ali -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDZN6BMkyGM64RGpERAuHqAKC3kaTKsM30A8btTp51/VQms3dfhACfbsUN tQV3F1IVU3aD5Sg7D125HGs= =vDfV -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Control Panel / Memory App crash after GPE install.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Grimme wrote: Hi, Am Donnerstag, den 27.10.2005, 11:17 +0200 schrieb Laurent Lieben: after flashing back my device with the actual retail software, i could launch the Memory App flawlessly Thereafter, i reinstalled GPE-TODO / GPE-CONTACT and all belongings libraries. Then, the Memory App from the control panel crash. does it have anything related with GPE installation? Since I did exactly the same, and the Memory App was working before, I believe this is really caused by the installation of GPE in some way. Uninstalling the GPE packages did not fix the crash. Either it is because of installing packages in general, or the GPE packages are buggy. Packages installed via the AI can't touch anything outside /var/lib/install, so this must be a bug in Maemo. The memory applet on my 770 started failing after installing the xterm packages, which was the first pacakge I installed. regards, Koen Martin ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDYJ7wMkyGM64RGpERAijyAKCWS15Ox39f/OoVfrRtsTC8weBMhgCfSoT7 kDROK8zqSEzkxgQ+QytCYv4= =/uR2 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Packet Telephony?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Komal Shah wrote: --- Andre Magalhaes [EMAIL PROTECTED] wrote: is correct. No other open source telephony apps use GStreamer (that I know of) and it looks like you'd have to hack it to make it work on an n770 and a desktop from the same code base... assuming you had software plugins for the codecs for GStreamer (do those exist?). Yes, they do exist. Where? I am not able to find gstreamer package with modified plugins (eg. mp3sink etc) in maemo repository or elsewhere? _or_ do we have to wait for such code until device gets released. AFAIK it's part of the closed source 'dark side' of maemo, which means there aren't any .debs available (yet). Unless you have a omap1710 on your workstation the plugins aren't of much use. Could one of the nokia people comment on the possibility of dsp plugins only containing stubs for the SDK_PC? regards, Koen ---Komal Shah http://komalshah.blogspot.com/ __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDYKoNMkyGM64RGpERAvRXAJ9vh378f8yL/lkQP39EF3veqDkZzACfWNpR FjYN20apxVPtKoltX4tPajQ= =hURI -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] kernel sources
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi wrote: Paul Mundt wrote: On Fri, Oct 21, 2005 at 11:31:40AM +0200, Koen Kooi wrote: Any news on the kernel sources? http://lkml.org/lkml/2005/10/12/87 I guess the dev program doesn't count as 'sale' or 'distributing'? Anyway, I'll wait for the source to be available on maemo.org. And the wait is over! The source is available from the debian repo. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDYLIrMkyGM64RGpERAkijAJ41Mg/xQD2HLZSwvETZ6E5PiKgAngCgnoF0 7nVD1UjoIs25qQyECI78Ucs= =6ouU -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Synchronization Application?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florian Boor wrote: snip Concerning syncing there was/is a project as part of Goolgle's summer of code based on the new OpenSync framework to enable PIM synchronisation with a desktop - currently Linux desktop. So if you interested in this then I would suggest to have a look at this SOC project and OpenSync. Yes really... that will be the best way to start. You can download a binary of gpesyncd from http://dominion.kabel.utwente.nl/koen/maemo/gpesyncd (25kB). Put it somewhere where it is in $PATH when logging in over ssh (see the wiki for how to install an ssh server). Then follow the instructions in http://handhelds.org/cgi-bin/cvsweb.cgi/gpe/base/gpe-opensync/INSTALL?rev=1.3content-type=text/x-cvsweb-markup and you should be able to sync your via your workstation. A really cool project would be to package opensync+plugins for maemo and make a small gui to sync the 770 to your phone/palm/etc using opensync. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDXi5cMkyGM64RGpERAsmRAKCaz0rqx2eszMqJJ040rUiw+7i3ggCfb2bX MGD12SjZHQcp4P+Z1XThWpM= =T8RC -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] kernel sources
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Any news on the kernel sources? I'd like to get those into OpenEmbedded as soon as possible, but I can't find anything resembling kernel sources and patches on maemo.org. And no, saying they are on kernel.org is not specific enough. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDWLV8MkyGM64RGpERAjO2AKCOKG2CBQ39ovhnipIrd7MtwJ/6jgCgrfLy 9sj4vhgWk0d7bDzr7L692Go= =Zitk -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Announce: Applications for download available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nils Faerber wrote: Hello! Since the developer program's devices are being shipped now we have created an easy download web page for our application ports to the Maemo platform: http://oss.kernelconcepts.de/maemo/app-install.shtml There you will find step by step download links that will directly install the applications and depending packages on your new device! The applications provided are: GPE-Todo - A todo list application GPE-Contacts - A contacts database Plucker - The well known ebook reader Yay! More to come over time (e.g. GPE-Calendar is being worked on...) Something like gpe-today would be nice to have. I suspect Philippe will update http://handhelds.org/~philippe/maemo/ with new gpe-mini-browser bits soon too. We tested the download and install procedure and it should work pretty well with the shipped developer devices. If you have any problem, please feel free to contact us! Also of course any other feedback is welcome too... What do you think about shipping a .tar (or .zip) containing the latest bits? That way I don't have to click on 9 different links to get all this goodness :) regards, Koen Enjoy! kernel concepts team nils faerber florian boor ole reinhardt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDV3m+MkyGM64RGpERAlSzAKCWN5keJHw26R61p7wIdgqvuq+zGwCeI1ip cV1omQMhpP+IuNLnVdf9Nys= =3xc2 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo on hx4700 ipaq
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tommi Komulainen wrote: On Mon, 2005-10-03 at 02:24 +1300, ext Bernard Mentink wrote: Will support for resolutions other than 800x480 be supported at any time soon so that Maemo can be run on the likes of the hx4700 (640x480)?? Technically speaking you can already run Maemo on any resolution, it'll just look goofy. You can easily check how badly things will break by running Xephyr in desired resolution rather than 800x480 We are aware of the hardcoded limitations in places and are working to make things more flexible in the future. However as you probably know the next software release is still going to be running on the same hardware. Is there changes to the UI that could be done at present to allow that resolution? There are some changes you can do simply by replacing the png files with a bit smaller ones and editing the gtkrc accordingly. For others you need to change (or preferrably remove) some hardcoded pixel measurements in the code. In some cases you may even need to do a different layout, like remove the number pad from the VKB. Currently the VKB is probably the trickiest part as the code isn't open, but for the rest it's just work to be done... Are the layouts built in to the binary or do they live somewhere in /etc or /usr/share? If it's the former you could use matchbox-keyboard (http://projects.o-hand.com/matchbox/) instead. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDQn6bMkyGM64RGpERAqRDAKCRZAae6OeeKg9EQrhGH/xAzfghtACfdSqJ 8fxNQBakS3cmwVSv4rhDdXY= =uZ5r -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Mono on Nokia 770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paolo Molaro wrote: I guess people on this list would be interested: Mono runs on the Nokia 770, including Gtk# apps. There is a tarball of the binaries here: http://primates.ximian.com/~lupus/mono-nokia.tgz It includes a README with a couple of instructions to setup env vars. You should be able to just copy a Gtk# app and have it run. There is no support yet for Hildon-specific widgets. Happy hacking! Can mono/ARM be cross-compiled using a x86 host? regards, Koen lupus -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDMSiQMkyGM64RGpERAjZKAJ0XBSudKAoXS62xlmBr3RfhHW4qqQCgqS49 PkawU10r8Kwzs/EHY1n5Ixk= =UZEZ -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] program close automatically on maemo emulator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 rh wrote: Hi all, I have program and running it on the maemo emulator. But after couples time my program is close by it self. Is there a problem with my program or is it emulator problem ? I've seen this happen when the app (gpe-todo) didn't register itself with osso. See http://www.maemo.org/platform/docs/tutorials/Maemo_tutorial.html#Maemo-Initialization for more information. Hope this helps, Koen Thanks Ronny ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDAGuAMkyGM64RGpERAlVIAJ9bbXpChdzHK3JZNUadR+8/gJ8CYgCgjAb8 69XUnHTFLsVnuy0g8p4CzHg= =X8YP -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo Terminal - 0.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wooky wrote: Looks very nice. Can I suggest: 1)Tabs, very useful in a device with limited screen real-state such as the N770; 2)configurable window name, i.e., allow it to display user, directory, etc. This also is useful to save space inside the terminal, since the user won't need to configure the prompt to show that. On a side note, is there a shell included in the N770 packages? bash, zsh? I'm not very familiar with zsh but it is said to have great command-completing built in, so it might be useful in the N770. I'm fairly certain at least busybox' ash will be included regards, Koen Message: 5 Date: Sat, 13 Aug 2005 21:28:15 +0530 From: Mayank Jain [EMAIL PROTECTED] Subject: [maemo-developers] Maemo Terminal - 0.1 To: maemo-developers@maemo.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 Hi all, I'm feeling very happy to announce the release of Maemo Terminal v0.1. Its a very basic implementation of a shell prompt for Nokia 770. More sophistication will follow ;-) You can download the tarball (which i've finally made after much hair pulling) from http://makuchaku.info/stuff/projects/maemo.terminal/MaemoTerminal-0.1.tar.gz Some screenshots can be located here... http://makuchaku.modblog.com/?show=blogviewblog_id=709200 Please direct your valuable comments, either to the maemo-developers mailing list or in the comments section of my blog :) http://makuchaku.modblog.com/?show=blogviewblog_id=709321#blogcomments Thanks :-) PS: Don't forget to read the THANKS file... -- regards, makuchaku --- http://makuchaku.info When you speak out with the courage of your convictions, people listen! -- Valmik Thapar, Wildlife Conservationist. -- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers End of maemo-developers Digest, Vol 4, Issue 18 *** -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFC/8sHMkyGM64RGpERAvNPAKCpAyINgHHpVZymBTHFpWjRDHO+WACeJga4 iAbxkU04M4ffqRx1kRA7c5o= =q3q4 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
