Wishlist (was:Re: N800 and USB host mode)
Hitting the Wishlist is almost only a matter of writing down a sensible rationale. You can do it. (..) I will put USB host mode in the Wishlist. I plan to update the roadmap page on Fridays (if we have stuff to update). So it seems I sent my suggestion to the wrong Wiki. Here it is again, then. It's user interface, I don't know where it belongs. Wish #1: Extend the current drag-to-shift paradigm on the virtual keyboard to 8 directions. Use these to implement accents for accented languages (e+NE for é, e+NW for è, c+SW for ç, etc), and to remove the need for shifting in general. Show the shifted letters in very small colored font in the corners of the keys. Possibly implement more complex gestures (e + NE then SE for ê, for example, or tilde, etc). Rationale: French (but also Polish, Spanish and other) has a lot of accents and current input method is a pain. Proposed change should be simple to implement, considering that 4 directions are already there. Showing the shifted characters when they are not obvious (i.e. for the symbol keys, not for the letters) will benefit everybody, not only the French :) Wish #2 Provide system-wide gestures for common operations (send window back, close window, etc) and for more specific ones (e.g in the browser and in the file manager, right drag on a link/folder to open it in a new window, left drag for back, etc). Publish an API and a style guide. I also support the following wish of the old wiki: Add a third Hybrid mode between Handwriting recognition and Keyboard input. It uses the keyboard screen as the main input source but also has a handwriting-recognition drawing square that replaces where the number pad is on the keyboard layout. Then, as we're typing, we can also use our default 16 user-defined macros we're allowed in the Teach area of the Handwriting Recognition window. This would allow for the best of both worlds in one screen, for those of us who can't get a BT keyboard right away. Although of course, handwriting recognition should be performed in all the text input fields (possibly zoomed in place for the occasion), not in a graffiti-like area. The two input modes would just become: show the keyboard, or don't. I acknowledge that this requires a lot of GTK rewriting. Best regards, Florent ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Problem with Home plugin
Hi, ext Vladislav Vasiliev wrote: Could you please help me with the issue I have with Maemo? When I update my omweather home plugin package https://garage.maemo.org/projects/omweather/ on Nokia 770 I have to reboot the device because plugin isn't unloaded from the memory. Switching plugin off doesn't help. The same thing happens with any home plugin. I've just encountered a problem with omweather where it made some of the statusbar plugins not to work properly. Disabling omweather didn't help in this problem and re-enabling it crashed desktop. The problem wasn't reproducable, but are you doing something funny with D-BUS in omweather? - Eero The lsof output clearly shows that plugin's stay in memory even when they're switched off. Here is example output of lsof when plugin iphome is switched off: Nokia770-39:~# lsof|grep iphome maemo-lau 856 user memREG 31,4 11692 40758 /usr/lib/hildon-home/libiphome.so Nokia770-39:~# In this tutorial http://maemo.org/platform/docs/howtos/maemo-plugin-tutorial.html#home-plugins I found that hildon_home_applet_lib_deinitialize should do the job: /** * @hildon_home_applet_lib_deinitialize * * @param applet_data Applet data as returned by applet_initialize. * * Called when Home unloads the applet from memory. * Applet should deallocate all the resources needed. * */ void hildon_home_applet_lib_deinitialize(void *applet_data); This very function when switching off the plugin is not called. Is this a bug? May be I miss understand the problem? However it seems that this function isn't called when switching off plugins or just doesn't unload plugins from memory. Is this a bug or have I missed something? How should it be done properly? Thank you. Vlad Vasiliev ___ 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
RFC: n800 suspend to ram
Hi; I've been doing some experiments with powersave on the n800. It seems you can't just put the n800 into suspend mode simply by doing a echo mem /sys/power/state, the retu watchdog kicks in if you leave it in that state too long. There is a flasher command to disable the retu watchdog, although through some horrible mistranslation it only stops the system from refreshing the watchdog -- it still goes off and brings down the system. Luckily there's an alternative, messy as it is - Refresh the retu watchdog, this will give you 64 seconds until it needs to be refreshed again. Next, set the retu rtc alarm; you only get one minute resolution, but that's jsut enough. Once the alarm is set, suspend; the alarm will wake the device out of suspend mode and the cycle repeats. Attached is a script to suspend the n800, the script is designed to run in the background and take advantage of the softoff state. (If you haven't done so already, I'd suggest editing /etc/mce/mce.ini and setting the power button to softoff). Once the softoff state is detected, the script will attempt to force the device into suspend. The script will spit out debug messages as it's run - wait the script is waiting for a softoff (backlight off, touch disabled) it will poll the system in 10 second intervals refresh updating the retu watchdog sleep XX suspending until rtc alarm in XX seconds awake (asleep X:XX:XX) device came back from sleep state before the alarm; likely the result of user interaction. X:XX:XX represents the total amount of time the script -attempted- to sleep for. Caveats - - the script must be run as root and should be run locally (not via ssh) - the device doesn't always suspend; particularly when the charger is attached - loadavg after exiting suspend is extremely high; probably miscalculated - the dsp REALLY hates it when you suspend with dsp activity There doesn't seem to be a good way of suspending dsp activity; I've read through the dsp documentation (http://dspgateway.sf.net) which seems to suggest the 'dspctl suspend' and 'dspctl resume' commands, which don't work. Once the dsp has crashed I can't find a reliable way to even restart it without rebooting. Requested - - completely disabling the watchdogs - help with dspctl/dsp_dld system The latest version of the script can always be found at http://mbm.openwrt.org/n800/suspend.sh suspend.sh Description: Bourne shell script ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Wishlist (was:Re: N800 and USB host mode)
On 3/7/07, Florent de Dinechin [EMAIL PROTECTED] wrote: Wish #1: Extend the current drag-to-shift paradigm on the virtual keyboard to 8 directions. Use these to implement accents for accented languages (e+NE for é, e+NW for è, c+SW for ç, etc), and to remove the need for shifting in general. Show the shifted letters in very small colored font in the corners of the keys. That could get a bit crowded on the small vkb -- how about showing the available tapdrag variants for a key on tapdrag (taphold repeats so it would make a weird trigger), using a larger area? What about capital accented letters such as É? Possibly implement more complex gestures (e + NE then SE for ê, for example, or tilde, etc). Rationale: French (but also Polish, Spanish and other) has a lot of accents and current input method is a pain. Proposed change should be simple to implement, considering that 4 directions are already there. Showing the shifted characters when they are not obvious (i.e. for the symbol keys, not for the letters) will benefit everybody, not only the French :) 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: RFC: n800 suspend to ram
Hello Mike, nice work, did you notice any differences in power consumption? I think main idea behind not having proper suspend on Nokia tablets is that power management is so good there is no need for something like this. All hardware should go to low power state when not used so there should be no difference between idle device and suspend to ram state you try to achieve. If there is a difference it should be probably reported as bug in maemo bugzilla :-) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Crash in maemo-launcher
On Tue, 2007-03-06 at 11:38 -0600, ext Matt Hoosier wrote: The relevant libraries in my build here are stock Glib 2.12.0, Gtk+ 2.10.6, and Pango 1.14.5. Are there any particular patches applied to Maemo's build of Pango, which are known to be required by the maemo-launcher? Alternately, it looks like the trouble reported by the various Pango functions above could be caused by an invalid GtkSettings object. Perhaps there's some other relevant bit in the Maemo fork of Gtk+ which I should be including? maemo-launcher (the gtk booster) is incompatible with gtk+ 2.10, we haven't worked on fixing the issue yet. https://maemo.org/bugzilla/show_bug.cgi?id=952 The crash is simply because the launcher (ab)uses the knowledge of gtk using pango/xft internally which is no longer valid assumption with 2.10 as it uses pango/cairo. -- Tommi Komulainen[EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: RFC: n800 suspend to ram
Hi! On Wed, 2007-03-07 at 05:01 -0600, ext Mike Baker wrote: Hi; I've been doing some experiments with powersave on the n800. Good, that's really good news. It seems you can't just put the n800 into suspend mode simply by doing a echo mem /sys/power/state, the retu watchdog kicks in if you leave it in that state too long. There is a flasher command to disable the retu watchdog, although through some horrible mistranslation it only stops the system from refreshing the watchdog -- it still goes off and brings down the system. Luckily there's an alternative, messy as it is - The wd in retu is a deadman's button. It comes from phones legacy, where a rebooting device can disrupt communications for others as well. In the tablet it still makes sense to have it for avoiding that if the devices becomes stuck, it also drains your battery. Refresh the retu watchdog, this will give you 64 seconds until it needs to be refreshed again. Next, set the retu rtc alarm; you only get one minute resolution, but that's jsut enough. Once the alarm is set, suspend; the alarm will wake the device out of suspend mode and the cycle repeats. Theoretically it's good; practically, i'm not so sure. The reason being that with runtime power management we get away quite cleanly with drivers not having to save/restore their state (we only ask them to use the clock fw). You probably would use suspend as an alternative to long idle periods, such as overnight, maybe using an idle timer to detect it. However, because of the 64s constraint, the energy price is not little when doing the wd kicking from userspace. A more power efficient solution (at the expense of stability) would be to do it from kernelspace, _whitout_ triggering the whole system thaw and re-enabling only those drivers required to talk with retu (since it contains both the rtc and the wd). But that's a very custom hack. Attached is a script to suspend the n800, the script is designed to run in the background and take advantage of the softoff state. (If you haven't done so already, I'd suggest editing /etc/mce/mce.ini and setting the power button to softoff). Once the softoff state is detected, the script will attempt to force the device into suspend. The script will spit out debug messages as it's run - wait the script is waiting for a softoff (backlight off, touch disabled) it will poll the system in 10 second intervals refresh updating the retu watchdog sleep XX suspending until rtc alarm in XX seconds awake (asleep X:XX:XX) device came back from sleep state before the alarm; likely the result of user interaction. X:XX:XX represents the total amount of time the script -attempted- to sleep for. Caveats - - the script must be run as root and should be run locally (not via ssh) - the device doesn't always suspend; particularly when the charger is attached - loadavg after exiting suspend is extremely high; probably miscalculated - the dsp REALLY hates it when you suspend with dsp activity yeah, that too There doesn't seem to be a good way of suspending dsp activity; I've read through the dsp documentation (http://dspgateway.sf.net) which seems to suggest the 'dspctl suspend' and 'dspctl resume' commands, which don't work. Once the dsp has crashed I can't find a reliable way to even restart it without rebooting. Requested - - completely disabling the watchdogs I'm not sure that will ever be an option, with the device having radios. - help with dspctl/dsp_dld system The latest version of the script can always be found at http://mbm.openwrt.org/n800/suspend.sh Never the less, congratulations for the effort. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- Cheers, Igor Igor Stoppa [EMAIL PROTECTED] (Nokia M - OSSO /Helsinki Finland) ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 and USB host mode
After asking some questions to the right person... On Tue, 2007-03-06 at 16:26 -0500, ext Larry Battraw wrote: There was never a removal of the functionality since this is a new chipset and support for it was not available for it (AFAIK) in the kernel until recently. I tried it out and it's pretty rough in (the current kernel version) 2.6.18; it would crash very quickly after booting up and I couldn't get it to actually do anything as far as host-mode is concerned. So no conspiracy, just no working code :-) I expect as support firms up we'll see it made available on the n800, particularly if people are interested enough to help out. Basically this is the story, yes. Savvy people interested in software (and hardware) hacking can get USB host mode to work but we can't currently offer official support on this functionality. It is in our plans to recover this functionality at some point. This is why it will go to to the roadmap (and not in Wishlist) when http://test.maemo.org/community/roadmap.html is updated. In the meantime you can have fun with kernel patches and some DIY bricolage. -- Quim Gil - http://maemo.org ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Wishlist
I wold also like to see the ability for some programs, like Maemopad, to extend the handwriting recognition out to the desktop - in other words, I'd like to be able to write on a line in Maemopad, and if the system recognizes my atrocious handwriting, convert it to ASCII. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Wishlist
Tuukka Tolvanen a écrit : On 3/7/07, Florent de Dinechin [EMAIL PROTECTED] wrote: Wish #1: Extend the current drag-to-shift paradigm on the virtual keyboard to 8 directions. Use these to implement accents for accented languages (e+NE for é, e+NW for è, c+SW for ç, etc), and to remove the need for shifting in general. Show the shifted letters in very small colored font in the corners of the keys. That could get a bit crowded on the small vkb -- how about showing the available tapdrag variants for a key on tapdrag (taphold repeats so it would make a weird trigger), using a larger area? What about I'm not sure it would get that crowded, because we have colors which are currently unused (considering the fantastic Mahjong graphics, the keyboard is really boring). More importantly, there is usually only one alternative for a letter, not 4. The only one with more than one alternative is e (éèëê). For this one we could only show the accent in the corner, not the full accented letter. That's for French. Polish has two accents on s and z. I don't think there is much worse than French, is there? (he said proudly) Then, for example, an à, even a full-size letter, in light red, in the NW corner, but in the background, so that the normal a hides it partly, would be perfectly clear. On the other hand, having the clicked key pop out with 2x magnification (instead of being boringly highlighted) would be interesting, but probably confusing when you try to type fast. As a conclusion: there are many possibilities, anyway I really wish the input improvement would be implemented for the next release. I'm sure it can be done in a matter of hours. Better have the improved input method now, and fancy graphics later. It will really be natural to use, even without visual help. capital accented letters such as É? For these, with a real keyboard, you have to caps-lock, then hit the letter. It would be no better, but no worse. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: OS 2007 / 770 hacker edition with sound and video
I'm trying the hacker edition and it's really nice, just a question: do you think it is possible to make a backup (for settings and preferences) on N800 and restore it on N770 hacker edition? -- Alessandro Pasotti w3: www.itopen.it ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: OS 2007 / 770 hacker edition with sound and video
Hi, I have not tried this particular combination, but the following ones seem to work at least: 770 = N800 770 = Hacker 770 However, I don't see why this one couldn't work as well... -Markku- Alessandro Pasotti wrote: I'm trying the hacker edition and it's really nice, just a question: do you think it is possible to make a backup (for settings and preferences) on N800 and restore it on N770 hacker edition? ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: OS 2007 / 770 hacker edition with sound and video
it worked! 2007/3/7, Markku Vire [EMAIL PROTECTED]: Hi, I have not tried this particular combination, but the following ones seem to work at least: 770 = N800 770 = Hacker 770 However, I don't see why this one couldn't work as well... -Markku- Alessandro Pasotti wrote: I'm trying the hacker edition and it's really nice, just a question: do you think it is possible to make a backup (for settings and preferences) on N800 and restore it on N770 hacker edition? -- Alessandro Pasotti w3: www.itopen.it ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
WLAN Question
Ok.. I have compiled a simple program to read RSSI now and it works using the new driver that was inserted. Here is a new issue that I am expericeing: Everytime I reboot, the n800 reverts to the old driver that doesn't contain the Prism headers. Does anyone know why this happens? Can't seem to figure out why it would revert to the old driver. Every time I reboot I have to run the following commands again: *move compiled cx3110.ko file to device and rmmod old driver* rmmod /mnt/initfs/lib/modules/2.6.18-omap1/cx3110x.ko *install your driver:* insmod /whereeveryourdriveris/cx3110x.ko chroot /mnt/initfs /usr/bin/wlan-cal Am I doing something that doesn't stay permanent? Thanks Michael ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Question
On Wed, Mar 07, 2007 at 12:10:08PM -0500, ext Michael Matalon wrote: Ok.. I have compiled a simple program to read RSSI now and it works using the new driver that was inserted. Here is a new issue that I am expericeing: Everytime I reboot, the n800 reverts to the old driver that doesn't contain the Prism headers. Does anyone know why this happens? Can't seem to figure out why it would revert to the old driver. Every time I reboot I have to run the following commands again: *move compiled cx3110.ko file to device and rmmod old driver* rmmod /mnt/initfs/lib/modules/2.6.18-omap1/cx3110x.ko *install your driver:* insmod /whereeveryourdriveris/cx3110x.ko chroot /mnt/initfs /usr/bin/wlan-cal Am I doing something that doesn't stay permanent? Yes, you're inserting a module. Modules aren't permanent, by their very definition: they're out of the kernel. You can move it over the cx3110x.ko in the initfs if you want it to stay permanent. The kernel can't guess where your new one might be. signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: Wishlist (was:Re: N800 and USB host mode)
Hitting the Wishlist is almost only a matter of writing down a sensible rationale. You can do it. (..) I will put USB host mode in the Wishlist. I plan to update the roadmap page on Fridays (if we have stuff to update). Wish #1: I'd like to request PowerVR chipset support (kernel driver, opengl and opensvg implementations). Rationale: The reasons are mainly superficial, however these are valid when you consider that users will probably like flashy games and interfaces, and therefore more devices may be sold (it will also make developers happy to have more cool hardware to play with!). The GUI could take advantage of the snazzy 2/3D features and therefore look nicer as well as being faster, as could 3rd party applications. Things like translucency would be both pretty and useful (e.g. full screen keyboard - thanks Tak). There are many other features and applications that I'm sure people could come up with if they had the option to use it. Game playability (and/or the range of games) would be improved having the 3D acceleration, anti-aliasing, fog, etc., effects. As I said, both of these things are in part superficial, however they would work to make the N800 a more saleable device. The final justification is that it's really annoying knowing the hardware is sat there doing nothing ;) Wish #2: I'd like support for the IVA (Imaging Video Accelerator) device to be implemented, or at least for some more information to be made available if Nokia can't justify the time. Rationale: This hardware is supposed to be able to improve large image display and can VGA decoding at up to 30fps. And again, it's just sat there. Cheers, Simon ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Question
On Wed, 2007-07-03 at 12:10 -0500, Michael Matalon wrote: Ok.. I have compiled a simple program to read RSSI now and it works using the new driver that was inserted. Here is a new issue that I am expericeing: Can you please not send HTML email to the mailing list, it's a royal pain. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Crash in maemo-launcher
On 3/7/07, Tommi Komulainen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 11:38 -0600, ext Matt Hoosier wrote: The relevant libraries in my build here are stock Glib 2.12.0, Gtk+ 2.10.6, and Pango 1.14.5. Are there any particular patches applied to Maemo's build of Pango, which are known to be required by the maemo-launcher? Alternately, it looks like the trouble reported by the various Pango functions above could be caused by an invalid GtkSettings object. Perhaps there's some other relevant bit in the Maemo fork of Gtk+ which I should be including? maemo-launcher (the gtk booster) is incompatible with gtk+ 2.10, we haven't worked on fixing the issue yet. https://maemo.org/bugzilla/show_bug.cgi?id=952 The crash is simply because the launcher (ab)uses the knowledge of gtk using pango/xft internally which is no longer valid assumption with 2.10 as it uses pango/cairo. Ah, that explains it. I'd like to follow the progress on that bugzilla ticket, but I don't see any mechanism to add myself as a CC. If you have permissions to do that, can you append the email address from which I'm currently sending. Thanks, Tommi. -- Tommi Komulainen[EMAIL PROTECTED] ___ 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
Re: [maemo-developers] Problem with Home plugin
On Mon, Dec 18, 2006, Vladislav Vasiliev wrote: However it seems that this function isn't called when switching off plugins or just doesn't unload plugins from memory. Is this a bug or have I missed something? How should it be done properly? Hi, sorry for the very late answer, home is not dlclosing the plugins, because many plugins (including the shipped ones) register GType. dlclosing the re-opening them results in them trying to re-register the types, even though glib already knows about them. The same handle from dlopen is reused if the applet is reopened. -- Johan ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Crash in maemo-launcher
On Wed, 2007-03-07 at 12:12 -0600, Matt Hoosier wrote: https://maemo.org/bugzilla/show_bug.cgi?id=952 The crash is simply because the launcher (ab)uses the knowledge of gtk using pango/xft internally which is no longer valid assumption with 2.10 as it uses pango/cairo. Ah, that explains it. I'd like to follow the progress on that bugzilla ticket, but I don't see any mechanism to add myself as a CC. The field is at the top-right. If you have permissions to do that, can you append the email address from which I'm currently sending. Done. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Question
Another Question regarding the WLAN chipset. How do I put it into monitor mode? Is it even possible? Thanks Michael On 3/7/07, Michael Matalon [EMAIL PROTECTED] wrote: Ok.. I have compiled a simple program to read RSSI now and it works using the new driver that was inserted. Here is a new issue that I am expericeing: Everytime I reboot, the n800 reverts to the old driver that doesn't contain the Prism headers. Does anyone know why this happens? Can't seem to figure out why it would revert to the old driver. Every time I reboot I have to run the following commands again: *move compiled cx3110.ko file to device and rmmod old driver* rmmod /mnt/initfs/lib/modules/2.6.18-omap1/cx3110x.ko *install your driver:* insmod /whereeveryourdriveris/cx3110x.ko chroot /mnt/initfs /usr/bin/wlan-cal Am I doing something that doesn't stay permanent? Thanks Michael ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Wishlist (was:Re: N800 and USB host mode)
On Wed, Mar 07, 2007 at 05:50:26PM -, ext Simon Pickering wrote: Wish #2: I'd like support for the IVA (Imaging Video Accelerator) device to be implemented, or at least for some more information to be made available if Nokia can't justify the time. Rationale: This hardware is supposed to be able to improve large image display and can VGA decoding at up to 30fps. And again, it's just sat there. Right now, the biggest bottleneck in video decoding is RFBI bandwidth (i.e. the bus between OMAP and the LCD controller we use), being too slow to push more than ~15fps through at 800x480. Beefing up the processor-side decoding doesn't help. We've been working on this and the next firmware update will give you significantly faster video (with a couple of caveats). So it's mostly just down to the large image display, which more or less suffers from the same problem. I don't think it would give us much benefit at all. As for PowerVR stuff, we're certainly well aware of that internally. Cheers, Daniel signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: RFC: n800 suspend to ram
On Wed, Mar 07, 2007 at 01:56:18PM +0200, Igor Stoppa wrote: On Wed, 2007-03-07 at 05:01 -0600, ext Mike Baker wrote: The wd in retu is a deadman's button. It comes from phones legacy, where a rebooting device can disrupt communications for others as well. In the tablet it still makes sense to have it for avoiding that if the devices becomes stuck, it also drains your battery. Refresh the retu watchdog, this will give you 64 seconds until it needs to be refreshed again. Next, set the retu rtc alarm; you only get one minute resolution, but that's jsut enough. Once the alarm is set, suspend; the alarm will wake the device out of suspend mode and the cycle repeats. Theoretically it's good; practically, i'm not so sure. The reason being that with runtime power management we get away quite cleanly with drivers not having to save/restore their state (we only ask them to use the clock fw). You probably would use suspend as an alternative to long idle periods, such as overnight, maybe using an idle timer to detect it. However, because of the 64s constraint, the energy price is not little when doing the wd kicking from userspace. A more power efficient solution (at the expense of stability) would be to do it from kernelspace, _whitout_ triggering the whole system thaw and re-enabling only those drivers required to talk with retu (since it contains both the rtc and the wd). But that's a very custom hack. I suppose the real issue here is what does suspend mode do that isn't done otherwise since even in userspace it seems to give better performance than just letting the system idle. A preliminary glance shows suspend disabling power to the MMC slots (VMMC and VDCDC3) which otherwise only happens when an MMC rescan event fails to find a card in the slot. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Serial through Bluetooth on N800
Hi sorry I'm new to writing apps on the N800 but want to write a program to interact with an embeded system I'm going to hook a bluetooth device to that, which is supposed to look like a serial port to the N800. So is there an application like serial port terminal or GTKterm which I use on my laptop since that would do for now. Also is there documentation on how to write a program that would use the serial port. I know I've seen that OBD-II sensor that uses a bluetooth to serial adapter to communicate to the N800 and it says right on nokia's product page that it can communicate via bluetooth to a serial port. I did download the code for the katix programs, I think Kate said that she is using the USB port like it is a serial port in there if I understood her correctly, and I've started to look through there to see if I can find anything useful in my situation also that code was written to work on the 770 so I don't know if it will be the same for the N800. Thank you for any help. -- -- Aaron Westerdaleseri ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Problem with Home plugin
Hi, ext Eero Tamminen wrote: ext Vladislav Vasiliev wrote: Could you please help me with the issue I have with Maemo? When I update my omweather home plugin package https://garage.maemo.org/projects/omweather/ on Nokia 770 I have to reboot the device because plugin isn't unloaded from the memory. Switching plugin off doesn't help. The same thing happens with any home plugin. I've just encountered a problem with omweather where it made some of the statusbar plugins not to work properly. Disabling omweather didn't help in this problem and re-enabling it crashed desktop. The problem wasn't reproducable, but are you doing something funny with D-BUS in omweather? Another problem with the omweather applet seems to be that it leaks *40* MB of RAM during the night while it's idling (and as a result applications will get OOM-killed by the kernel). - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Wishlist (was:Re: N800 and USB host mode)
Hi, ext Simon Pickering wrote: Hitting the Wishlist is almost only a matter of writing down a sensible rationale. You can do it. (..) I will put USB host mode in the Wishlist. I plan to update the roadmap page on Fridays (if we have stuff to update). Wish #1: I'd like to request PowerVR chipset support (kernel driver, opengl and opensvg implementations). Rationale: The reasons are mainly superficial, however these are valid when you consider that users will probably like flashy games and interfaces, and therefore more devices may be sold (it will also make developers happy to have more cool hardware to play with!). The GUI could take advantage of the snazzy 2/3D features and therefore look nicer as well as being faster, as could 3rd party applications. Things like translucency would be both pretty and useful (e.g. full screen keyboard - thanks Tak). There are many other features and applications that I'm sure people could come up with if they had the option to use it. Game playability (and/or the range of games) would be improved having the 3D acceleration, anti-aliasing, fog, etc., effects. Err. Translucency means compositing and keeping the composited items in memory. Due to additional memory accesses needed for this, it would be slower (and take more memory) regardless of how accelerated it would be. You can see this even on Desktop, just ask how many gamers are happy with integrated graphics cards which share memory with the rest of the system instead of having (hundreds of megs) of their own memory in which to store textures etc. and in where the operations can be done without loading the memory bus of the rest of the system (downside is that all this costs, adds to the computer power consumption heating). :-) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Problem with Home plugin
Hi, I wonder if the Home is already using GTypePlugin interface and dynamic types to handle the types registered by the plugins. That would be the right (tm) way to handle this in the scope of GObject... In the case of register_static one can newer unload the modules. -Markku- Johan Bilien wrote: On Mon, Dec 18, 2006, Vladislav Vasiliev wrote: However it seems that this function isn't called when switching off plugins or just doesn't unload plugins from memory. Is this a bug or have I missed something? How should it be done properly? Hi, sorry for the very late answer, home is not dlclosing the plugins, because many plugins (including the shipped ones) register GType. dlclosing the re-opening them results in them trying to re-register the types, even though glib already knows about them. The same handle from dlopen is reused if the applet is reopened. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [Fwd: [Fwd: Re: Coming back to Glade]]
Hi, Added CC to the developers list as I think this belongs there too. ext Marius Gedminas wrote: On Wed, Mar 07, 2007 at 05:55:58PM +0100, Claudio Scordino wrote: Never generate code with glade. NEVER. It's evil. glade-2 developers recommend to use only .glade files and load them using libglade. Glade-3 doesn't support at all generating code. Oh, now I see! Can I have more information about why glade-2 messed up generating code files ? Wasn't the problem fixable at all ? It is a generic problem when you use some UI tool/wizard to generate source code, and then modify the source code. If you later want to tweak something, you have to do it in the code (inconvenient), or if you use the same tool to regenerate code, you'll have to redo all your modifications (painful). There are many RAD tools which handle the round-trip (some less well than the others). AFAIK with Glade the issue was that it just doesn't belong into Glade, it should be done by other, specialized programs. For example each language which has separate Gtk/Glade bindings (C, C++ etc) could have it's own code generator tool. Anyway, for interpreted languages like Python, Ruby, PHP, Perl etc. loading the Glade file with libglade is probably faster than the generated code that would be interpreted. And on Desktop reading the .glade files directly is fast enough in itself I think, the problem is just embedded devices. Also, C (in which Glade is written) is not exactly known to be best language for doing language parses (for the round-trip), but e.g. Python has actually several modules for writing language parses. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
