[maemo-developers] [OT] Opinion about an area in Helsinki
Sorry for the OT, this is a request from a next OSSO team member trying to allocate the family in Finland. Do you have any opinion about this area in Helsinki: http://maps.google.com/?q=Helsinki,+Finland&ie=UTF8&z=17&ll=60.221902,24.841837&spn=0.002552,0.01354&t=h&om=1 We have found a house to rent and it looks good. I only want to know a bit about impressions of the area - if locals think that phantoms wonder at night because there was an ancient cemetery, those kinds of things. ;) I have also asked at http://www.finlandforum.org/bb/viewtopic.php?p=171614 and #maemo - you know how quick these opportunities go from your hand. Thank you! -- Quim Gil /// http://desdeamericaconamor.org ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] flasher not flashing rootfs?
DJ Delorie wrote: I'm pretty sure the jffs2 image is OK, as I can mount it on my desktop via mtdram. Better would be to paste your mkfs.jffs2 line directly. I guess you did use something like # mkfs.jffs2 -r rootfs -o rootfs.jffs2 -e 128 -l -n right? I guess '-e 128 -l' is critical. You can also flash rootfs via mtd-utils when booted from mmc but flasher probably has some reason why it is refusing the flashing. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] docpurge in maemo 2.1
Hi, I've noticed something odd in maemo 2.1. When installing / upgrading packages in scratchbox, in the "Setting up" stage apt/dpkg can get stuck for large amounts of time (forever?). I've found this in gtk2.0-examples for instance, in the context of sardine work. It looks like apt/dpkg gets stalled while running /usr/sbin7docpurge with a large number of files listed in the command line. So: - Why is docpurge executed when installing packages in scratchbox environment in the first place? You don't really need (or want) to remove documentation there. - In any case, why does it get stalled? In the case of gtk2.0-examples it was still stalled after several hours. docpurge comes in the maemo 2.1 rootstraps, both i386 and armel. In the sardine build robot I work around this by deleting docpurge. It would be good to have this fixed. Br, Carlos ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] [OT] Opinion about an area in Helsinki
Hey! Oh! i haven't been living in espoo myself (although on the border area) but afaik, it's a nice place to live espcially if you have a car. At least i would prefer to live somewhere in Helsinki if my office is in Helsinki since i don't have a car. Two reasons: 1. It's easier and faster to travel to/from your work and 2. It's much cheaper to buy a ticket for the whole month or more altogether rather than buying it each time you travel but the regional ticket (which covers the areas around helsinki as well) is almost double the price so you don't save anything. Besides that, I have friends living in espoo and they are very happy there. Hope this helps. On 12/13/06, Quim Gil <[EMAIL PROTECTED]> wrote: Sorry for the OT, this is a request from a next OSSO team member trying to allocate the family in Finland. Do you have any opinion about this area in Helsinki: http://maps.google.com/?q=Helsinki,+Finland&ie=UTF8&z=17&ll=60.221902,24.841837&spn=0.002552,0.01354&t=h&om=1 We have found a house to rent and it looks good. I only want to know a bit about impressions of the area - if locals think that phantoms wonder at night because there was an ancient cemetery, those kinds of things. ;) I have also asked at http://www.finlandforum.org/bb/viewtopic.php?p=171614 and #maemo - you know how quick these opportunities go from your hand. Thank you! -- Quim Gil /// http://desdeamericaconamor.org ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- Regards, Zeeshan Ali Design Engineer, SW Open Source Software Operations Nokia Multimedia ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] docpurge in maemo 2.1
On Wed, 2006-12-13 at 13:07 +0200, Carlos Guerreiro wrote: > Hi, > > I've noticed something odd in maemo 2.1. > When installing / upgrading packages in scratchbox, in the "Setting up" > stage apt/dpkg can get stuck for large amounts of time (forever?). > I've found this in gtk2.0-examples for instance, in the context of > sardine work. > It looks like apt/dpkg gets stalled while running /usr/sbin7docpurge > with a large number of files listed in the command line. > > So: > - Why is docpurge executed when installing packages in scratchbox > environment in the first place? You don't really need (or want) to > remove documentation there. I agree it is not needed, but osso-ai metapackage depends on it and that is the reason why it's in there, I suppose. Actually I think it's wrong that osso-ai depends on docpurge, maybe it should rather suggest or recommend it? > - In any case, why does it get stalled? In the case of gtk2.0-examples > it was still stalled after several hours. > I quickly tried this and it doesn't happen in my environment. I have Scratchbox Apophis r4 with Scirocco rootstraps upgraded to Herring. The version I installed is gtk2.0-examples (2.6.10-2.osso25) and setting up phase is very fast. I tried inside armel target. > docpurge comes in the maemo 2.1 rootstraps, both i386 and armel. > In the sardine build robot I work around this by deleting docpurge. It > would be good to have this fixed. > IMHO, existence of docpurge is just a way to make a quick fix for poor packaging. I think that taking _all_ documentation out of the package where you have binaries would be the correct way and it would be nice if this happens in original Debian packages. This would help using Debian as it is as a platform for embedded/mobile systems and hacks like docpurge wouldn't be needed. Sincerely, -- Miko Nieminen <[EMAIL PROTECTED]> ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] docpurge in maemo 2.1
"ext Miko Nieminen" <[EMAIL PROTECTED]> writes: >> - Why is docpurge executed when installing packages in scratchbox >> environment in the first place? You don't really need (or want) to >> remove documentation there. > > I agree it is not needed, but osso-ai metapackage depends on it and that > is the reason why it's in there, I suppose. Actually I think it's wrong > that osso-ai depends on docpurge, maybe it should rather suggest or > recommend it? osso-ai is a meta package that should only be used when creating product flash images. It should not be in the SDK. >> docpurge comes in the maemo 2.1 rootstraps, both i386 and armel. >> In the sardine build robot I work around this by deleting >> docpurge. It would be good to have this fixed. >> > > IMHO, existence of docpurge is just a way to make a quick fix for poor > packaging. Well. :) Docpurge is a hack and should go away, agreed, but it's not entirely obvious what it should be replaced with. I think our best option is a combined approach of having dpkg filter certain files during installation, and splitting documentation out of arch packages if that makes sense. Whether splitting a package makes sense depends on how much we want to deviate from upstream if upstream doesn't want to follow us. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] flasher not flashing rootfs?
> Better would be to paste your mkfs.jffs2 line directly. I guess you did > use something like > # mkfs.jffs2 -r rootfs -o rootfs.jffs2 -e 128 -l -n > right? I guess '-e 128 -l' is critical. Yup, right from the tar2jffs2.sh script: mkfs.jffs2 -r $TEMPDIR -o $name.temp -e 128 -l -n It does the sumtool line too: sumtool -i $name.temp -o $name -e 128KiB -l -n > You can also flash rootfs via mtd-utils when booted from mmc but flasher > probably has some reason why it is refusing the flashing. I assumed there was some reason, but (1) it doesn't tell me, and (2) there's no source, so I can't figure it out myself. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] flasher not flashing rootfs?
DJ Delorie wrote: Yup, right from the tar2jffs2.sh script: mkfs.jffs2 -r $TEMPDIR -o $name.temp -e 128 -l -n It does the sumtool line too: sumtool -i $name.temp -o $name -e 128KiB -l -n Well, then it looks OK. Maybe your image is too small (4MB from your output? some test?) and this is bug/feature of flasher? In any case if you are sure the image is ok and want experiment with booting from mmc, have a look here http://fanoush.webpark.cz/maemo/#initfs for precompiled mtd-utils. Flashing rootfs can be done with this too when booted from mmc. Tried myself. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] flasher not flashing rootfs?
> Well, then it looks OK. Maybe your image is too small (4MB from your > output? some test?) I was working on a "minimum rootfs to get a console shell" test. The next step is "minimum rootfs to get an X app". > In any case if you are sure the image is ok and want experiment with > booting from mmc, have a look here What I did yesterday is make an ext2 file system image on my desktop, then dd it over to the 770 right into the mmc card (using Nokia's 2.1 rootfs, which I can flash). Now I can boot off the mmc card. I need to get a bigger card if I want to go much further with this, though ;-) > Flashing rootfs can be done with this too when booted from mmc. Tried > myself. Assuming you have a big enough mmc to hold a full rootfs image. I still only have the pre-supplied 64m card. But, I'll keep that in mind. It would be better if the flasher just worked, or at least told me why it wasn't. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] flasher not flashing rootfs?
On Wed, Dec 13, 2006 at 11:48:58AM -0500, ext DJ Delorie wrote: > > Well, then it looks OK. Maybe your image is too small (4MB from your > > output? some test?) > > I was working on a "minimum rootfs to get a console shell" test. The > next step is "minimum rootfs to get an X app". The minimum size for a rootfs is 4MB at the moment. Cheers, Daniel signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] flasher not flashing rootfs?
> The minimum size for a rootfs is 4MB at the moment. The image was a little bigger than 4Mb, but that was enough to help me out. I added gcc to the rootfs (now 12Mb) and if flashes now. I'll try to track down a more precise minimum size. Can you add a message to the flasher tool? Or release the sources so I can? Thanks! ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] How to determine if the screen has turned off?
In the Maemo coding style and programming guidelines document on maemo.org, it states the following: "Avoid updating the GUI when the application running on the background and when the screen has been turned off. Remove unnecessary graphical elements or constantly updated screen components." Now, it appears that hildon_window_get_is_topmost() or hildon_program_get_is_topmost() can be used to determine if an application is running in the background, but how does one programmatically determine if the screen has been turned off? I see in the latest version of libosso in SVN that there is a muali API that provides the ability to access the information via a callback, but it is unclear how to determine this on 2.0 or 2.1. Perhaps I can use XScreenSaverQueryInfo() ? Thanks, Aaron ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] flasher not flashing rootfs?
> The minimum size for a rootfs is 4MB at the moment. My testing shows that a jffs2 file of *exactly* 8 Mb (8,388,608 bytes) will NOT flash. Anything bigger than that (the next largest jffs2 image is 8,389,752 bytes) WILL flash. Note that this is the jffs2 image as produced by tar2jffs, including the sumtool step - i.e. this is the size of the file transferred to the 770, not the output of mkfs.jffs2. Thanks for the tips, I'm back to work now :-) DJ ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
On Wed, Dec 13, 2006, Aaron Levinson wrote: > In the Maemo coding style and programming guidelines document on > maemo.org, it states the following: "Avoid updating the GUI when the > application running on the background and when the screen has been turned > off. Remove unnecessary graphical elements or constantly updated screen > components." Now, it appears that hildon_window_get_is_topmost() or > hildon_program_get_is_topmost() can be used to determine if an application > is running in the background, but how does one programmatically determine > if the screen has been turned off? I see in the latest version of libosso > in SVN that there is a muali API that provides the ability to access the > information via a callback, but it is unclear how to determine this on 2.0 > or 2.1. Perhaps I can use XScreenSaverQueryInfo() ? http://maemo.org/platform/docs/api/libosso/html/index.html You can register a callback with osso_hw_set_event_cb, set the system_inactivity_ind flag in the osso_hw_state_t argument. -- Johan Bilien <[EMAIL PROTECTED]> ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
On Wed, 13 Dec 2006, Johan Bilien wrote: > On Wed, Dec 13, 2006, Aaron Levinson wrote: > > In the Maemo coding style and programming guidelines document on > > maemo.org, it states the following: "Avoid updating the GUI when the > > application running on the background and when the screen has been turned > > off. Remove unnecessary graphical elements or constantly updated screen > > components." Now, it appears that hildon_window_get_is_topmost() or > > hildon_program_get_is_topmost() can be used to determine if an application > > is running in the background, but how does one programmatically determine > > if the screen has been turned off? I see in the latest version of libosso > > in SVN that there is a muali API that provides the ability to access the > > information via a callback, but it is unclear how to determine this on 2.0 > > or 2.1. Perhaps I can use XScreenSaverQueryInfo() ? > > http://maemo.org/platform/docs/api/libosso/html/index.html > > You can register a callback with osso_hw_set_event_cb, set the > system_inactivity_ind flag in the osso_hw_state_t argument. Well, I had already examining the libosso APIs before sending the e-mail, and I did notice the system_inactivity_ind flag in the osso_hw_state_t struct. However, according to the libosso documentation, if the callback is called for system inactivity, this means that "the application should reduce its activity". I didn't directly associate this text with the screen being blanked, which I think is understandable, since screen blanking is not the same thing. What are the conditions that result in the callback for the system inactivity indicator being called? The statement "the application should reduce its activity" is somewhat open-ended, and perhaps this callback is used for more than just to indicate that the screen has been blanked. Thanks, Aaron ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
Aaron Levinson wrote: Well, I had already examining the libosso APIs before sending the e-mail, and I did notice the system_inactivity_ind flag in the osso_hw_state_t struct. However, according to the libosso documentation, if the callback is called for system inactivity, this means that "the application should reduce its activity". I didn't directly associate this text with the screen being blanked, which I think is understandable, since screen blanking is not the same thing. What are the conditions that result in the callback for the system inactivity indicator being called? The statement "the application should reduce its activity" is somewhat open-ended, and perhaps this callback is used for more than just to indicate that the screen has been blanked. Right, screen blanking is the only occasion where I have seen this callback triggered, but maybe it's used in other cases, Kimmo? -- Johan ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
