Re: DSME code?
Jesse Guardiani wrote: > I'd personally love to see DSME open sourced. In particular, there are > screen ON/OFF/Notify > events that it sends/receives via dbus that I'd love to extend. For > example, I've got a DSME > related ticket that I'd like to close using dbus, but that probably > isn't possible with DSME as-is: > https://www.guardiani.us/projects/kagu/ticket/52 > I'm not sure what exactly you want but blanking screen is possible via dsme somehow. At least there is dsmetest program ini initfs that communicates with dsme deamon and it can do it. Just run # chroot /mnt/initfs /usr/sbin/dsmetest to see the help. -d 2 is the one to turn display. You may probably use strace to see what it is writing to /tmp/dsmesock Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSME code?
Frantisek Dufka wrote: > Same for https://garage.maemo.org/mailman/listinfo/dsm-devel > > It doesn't matter whether I am logged-in to garage or not. > Same 'page not found' with IE on XP, Firefox on XP, Firefox and lynx on Ubuntu. However I did have success with wget but that one is quite hard to use to browse list archives :-) Something strange is happening here. Either you guys are in some inner circle or the problem is on my side. I suppose the latter. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSME code?
Simon Pickering wrote: > I happened to come across this commit mailing list: https://garage.maemo.org/pipermail/dsm-commits/ Is this related to the 770/N800 closed source DSME code at all? It looks like it might be. >>> The first post is a large patch containing the entire source from the >>> looks of it. >> >> Oh, it is gone. Page not found. I was very interested in that :-( > > Still there for me: > > https://garage.maemo.org/pipermail/dsm-commits/2006-July/00.html > I can see listinfo here https://garage.maemo.org/mailman/listinfo/dsm-commits but clicking DSM-commits Archives link brings me a nice Garage page with blue 'PAGE NOT FOUND' text and search box. Maybe you have it cached? Same for https://garage.maemo.org/mailman/listinfo/dsm-devel It doesn't matter whether I am logged-in to garage or not. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DSME code?
Simon Pickering wrote: > Hi Neil, > >> I happened to come across this commit mailing list: >> https://garage.maemo.org/pipermail/dsm-commits/ >> >> Is this related to the 770/N800 closed source DSME code at all? It >> looks like it might be. >> >> (I have no strong interest in this myself, but I know that from time >> to time questions are asked about what DSME is, so I thought this >> might be useful to point out...) > > Good spot, I was wondering what goes on inside DSME. > > The first post is a large patch containing the entire source from the > looks of it. > Oh, it is gone. Page not found. I was very interested in that :-( Currently there is an issue with bootmenu network recovery mode over usb in initfs with N800. 770 works fine but initfs (dsme?) in N800 doesn't like staying too long in initfs and powers the device off after some random time. It is good enough to enter few commands but not good enough to save/restore rootfs. I'd want to keep dsme happy somehow while staying in initfs for longer time. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: hacker edition status and future?
Joni Valtanen wrote: > > But yes. 2.6.18 is possible to get work. but there is needed some > dsp+kernel guru to do this. What would help for the start is making old initfs from first hacker edition available for download again so one could start testing kernels >= 2.6.16. With initfs from IT2006 you won't get too far when booting such kernel, dsme crashes and device reboots immediately. >> We're close to releasing a new version of the hacker edition, at >> that point let's talk about this again. With that newer version >> working (userspace updated to the latest release for the N800 >> as much as possible) we can reconsider the use of the old initfs. OK, thanks. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Compiling GNU Utilities on Scratchbox
You may also try compiling with thumb intruction set. This is how most stuff in firmware is compiled. Try export DEB_BUILD_OPTIONS=thumb before building the deb or use compiler options directly (-mthumb -mthumb-interwork) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Obtaining flash memory serial numbers on Nokia N800
David Hazel wrote: > On Fri, 2007-08-10 at 22:52 +0300, Igor Stoppa wrote: >> I don't know about MMC/SD (isn't that something that is not public >> available?) > > I would hope that the serial number of an SD card can be read on the > Nokia. It can certainly be read from an SD card that is installed on a > Windows Mobile device. cat /sys/devices/platform/mmci-omap.1/*/cid * is there because the path contains card model name which is variable. In my case for Transcend 150x 4GB SD the name is 'b368' and card is in internal slot Nokia-N800-26:~# echo /sys/devices/platform/mmci-omap.1/*/cid /sys/devices/platform/mmci-omap.1/mmc0:b368/cid Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N800 is USB Host mode (Compiling kernel with CONFIG_USB_MUSB_HOST)
Michael Lapinski wrote: > Does anyone have any ideas why this would happen? Also can anyone tell > me what the USB chipset is on the 800? > Was discussed here in the list few times. Search list archives for details [1] or check this http://muru.com/linux/n800-usb-host/ Frantisek 1. http://www.gossamer-threads.com/lists/maemo/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Webkit based browser on N800
Oliver Dole wrote: > We also plan to start a GTK port in order to get OWB running on > GTK/Hildon but I don't really have a timeframe about that, so if some > people are willing to see webkit on N800 / GTK, please show up, any > help is greatly encouraged :) Hi, You may also look how Gecko engine integration is done. The advantage for user is same UI and switchable engines. The advantages for porting is that most integration code may be already written. See http://browser.garage.maemo.org/ or directly http://browser.garage.maemo.org/docs/browser_paper.html Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Virtual keyboards
Tomas Junnonen wrote: > But I'm not sure that approach is so useful in the end. For example, the > applications on the tablet are designed to not need modifier and > function keys, and the VKB is designed around these assumptions. Yes, that's a problem. Would be nice to solve it by adding those keys to VKB, I'm missing them a lot :-) > When > you use remote X applications that's no longer the case. In such use a > full keyboard emulator like matchbox-keyboard might make more sense, and > the effort involved could be better spent improving matchbox-keyboard > instead. Well, one keyboard would be better of course. If those two could be integrated at some level it would be great. It seems similar to me like the (non-standard) way of maemo-desktop and displaying icons in taskbar in current IT200x system. I think hildon-desktop fixed this and you no longer need the shortcut file (?) like it is normal on desktop linux. VKB shoud be next step in this way (to run non-hildonized stuff). Let's hope this will be fixed too. If not Nokia then maybe Intel or people behind Ubuntu Mobile will fix it. I guess it is unreasonable to disallow other GUI toolkits on x86 hardware. People expect to run everything there. It could be tolerated on low performance ARM device targeted to some specific use (i.e. Internet Tablet :-) but not for generic linux mobile computer. But let's go back to practical issues, can those two keyboards (gtk based Hildon VKB and other X API based) be somehow integrated together so they could 'just work' based on what window is active? Is the Hildon one still closed source? Where should one start - Matchbox? Or maybe some status bar applet doing some trickery could bring up such X based vkbd based on active window and hide it when the gtk one becomes active. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Virtual keyboards
Tomas Junnonen wrote: > A VKB implemented using a toolkit on the other hand allows the keyboard > to instrument with the running application through the API of that > toolkit. This means communication is bi-directional between the > application and the VKB, allowing a different set of features and > "smart" behavior So is it possible to extend VKB to be even smarter about client windows and use toolkit methods for gtk window but fall back to generate X events for other windows (i.e implement both approaches)? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: hacker edition status and future?
Joni Valtanen wrote: > > Next version is coming as rootfs. There is no kernel updates. OK, this means hacking 2.6.16 kernel and backporting something makes sense. Alternatively time could be spent in making dual kernel booting situation working (IT2006 vs 2007 with newer kernel) so this answer helps to prioritize things, thanks :-) > Same components are used as in n800 version, but the kernel is older > 2.6.16. There is lot of work if n800 version of the kernel is used. Yes but I hope you are not completely ditching n800 kernel for future hacker edition releases (if any). If you are not planning this it would be nice to say so and also publish binary stuff needed to use newer kernels. First HE version had initfs that worked with newer kernels but it is not availabe anymore at http://tablets-dev.nokia.com/os2007_hacker_edition.php The IT2006 one crashes in dsme early on boot with 2.6.18 which makes things really hard since the unstoppable (retu?) watchdog reboots device and also reading flags (like root device) from config partition with cal-tool is impossible without dsme running. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
hacker edition status and future?
Hello, since now the project is revived and some work is going on, I'd like to raise this again. It would be nice if someone involved in this project could comment this http://lists.maemo.org/pipermail/maemo-developers/2007-May/010280.html I guess this project is not exactly top secret like regular firmwares so more open process would be nice. I have also raised it here https://garage.maemo.org/forum/forum.php?forum_id=612 , feel free to answer where it is appropriate. Opinions can differ but I still think this list would be better for such discussion due to bigger audience http://lists.maemo.org/pipermail/maemo-developers/2007-May/010283.html Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Internet Tablet Power Management presentation from linux-pm summit 2007
Igor Stoppa wrote: > I certainly will run my tablet at higher speed and/or lower voltage; > finland makes it unlikely to incur in heating problems ;-) CPU temperature sensor might be useful to guess the limit and cut the speed down in case one is not in Finland :-) Is there one? > >> Does it mean the arm core in current N800 can run at >> 400Mhz? > > Yes, the data is for stock N800 (we have this SpeedSorted OMAP2 that can > run with ARM @ 400MHz). Cool :-) Well, maybe 'Hot' actually :-) >> Do you plan to have user selectable power/speed profiles to let people >> choose whether they want slower system or shorter battery life? > > My personal belief is that the user should not have to care about this: > something is broken if the user has to be involved. The system should > have all the info (and means) to run at good enough speed when needed. Well, I'm not sure but maybe when being conservative with power saving and when some hints are applied (i.e some API) it could work. I'm mainly thinking about CPU spikes when applications are starting. I fear the system will not react quickly enough with 'overclocking' when application starts since otherwise the device does nothing before and after. But this specific problem could be solved with some hints done from application launcher or maybe kernel or libc (exec/fork call) itself. I'm not sure how linux currently does it on x86 (shame on me, using XP on laptop and linux only in vmware) but my experience with RMClock on XP (http://cpu.rightmark.org/products/rmclock.shtml) is that it is hard/impossible to tune it in such way that application startup is not slower and you still save some power. > > It's a similar case to sleep while idle vs user-controlled suspend: just > because old devices were doing suspend that doesn't make it desirable. Yes, this is old discussion. I still think proper suspend is useful. While current implementation is great and is mostly what users expect or can tolerate, sometimes you simply want to 'pause' or 'hibernate' the device no matter what, throw it in the bag and 8 hours (or 10 days) later resume exactly where you left off with minimum energy lost. Without stopping applications or thinking about anything. This is what proper suspend can give you. This is how notebooks and PDAs work. This is what would be sometimes useful even on internet tablets (no matter how 'always connected' they are supposed to be). But I agree current power management on Nokia tablets is great so this is not critical. Still I can't resist when this is brought up :-) I'm not saying this needs to be definitely implemented by freezing everything in user and/or kernel space. I'm saying that apart from current power saving when idle there should be easy way of telling the device to go to sleep completely (pausing audio, disconecting from network,...) >> Or do you consider some API so apps can suggest how fast system >> they want (i.e. media players, games, emulators vs book readers)? > > You mean QoS. Yes, that seems to be the general understanding. Yes that's it. Didn't know this term is used also in power management, though. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Internet Tablet Power Management presentation from linux-pm summit 2007
Igor Stoppa wrote: > Hi, > this is the presentation we gave last week in Ottawa at the pm summit. > It is the first step in improving our communication process with the > community and give a preview of what we are working on. > > http://maemo.org/midcom-permalink-0c828d202f2011dc9945e502835830f130f1 > > It contains a brief overview of what is already shipping in the 770 and > the n800, but the main focus is about our work in progress. > > Comments and questions are welcomed. Thanks Igor, it is quite interesting. Maybe there is a bug on page 15 with DSP frequency for OP 0, shouldn't the 133 be 233 or 333 (unless you need to slow it down because of speeding up the arm core to meet some power requirement)? Does it mean the arm core in current N800 can run at 400Mhz? As for dynamic voltage and frequency scaling did I understood it correctly that even if lower voltage means considerable saving (even if task runs longer) it is almost not worth the hassle due to other issues (latency of voltage/frequency change, static power consumption of other parts, hard prediction of future)? Or how big savings do you expect overall from voltage/frequency scaling when the device is mostly idle (i.e being mostly waken up by inefficient system or apps waiting for something and not hogging the CPU). Or maybe the question is how efficient is the system currently, is there something like http://www.linuxpowertop.org/ for omap to see what can be improved or what cannot and could benefit from lower frequency/voltage? Do you plan to have user selectable power/speed profiles to let people choose whether they want slower system or shorter battery life? Or do you suppose there will be good enough cpufreq governor so it is not needed. Or do you consider some API so apps can suggest how fast system they want (i.e. media players, games, emulators vs book readers)? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Firmware 4.2007.26-8 has inferior SDHC performance than 3.2007.10-7 - why?
Here are relevant parts of kernel changelog kernel-source-rx-34 (2.6.18-osso42) unstable; urgency=low * week200713-1 release * MMC: Add support for mmc v4 high speed mode * mmc: Support for high speed SD cards * mmc: Add support for SDHC cards * mmc: Graceful fallback for fancy features * mmc: MMC sector based cards -- Yauheni Kaliuta <[EMAIL PROTECTED]> Tue, 27 Mar 2007 15:15:01 +0300 ... kernel-source-rx-34 (2.6.18-osso47) unstable; urgency=low * week200721-1 release * MMC: Limit the mmc clock to 24MHz. Fixes: NB#54313 -- Yauheni Kaliuta <[EMAIL PROTECTED]> Mon, 21 May 2007 16:33:49 +0300 It may be that MMC speed is limited to 24Mhz (wonder what NB#54313 is about) for similar reason like N770 MMC speed being limited to 12Mhz - better compatibility by sacrificing speed. Sadly this makes perfect sense for Nokia. While this was real pain with N770 (approx 1.4MB/s read speed, 300KB/s write speed) with N800 it is not that bad. After all 7 or 11MB/s is not such big difference in real life. I'm far more concerned about device physically corrupting cards (like someone reported in ITT forum and bugzilla). Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo wiki survey
Quim Gil wrote: > Dear maemo contributors, can you please answer these questions? > > - What do you think about the current wiki tool at > http://maemo.org/community/wiki (leaving content aside) ? http://lists.maemo.org/pipermail//maemo-users/2007-June/005538.html > > - Are you using it? Did you use the previous one? I am using it far less then previous one both for reading and editing. > - Mention good things / bad things of the current wiki (and what would > you do). I understand the need for better CMS system for whole site but still feature-wise the new wiki is IMO big step back from old one in all aspects. Please add recent changes for whole wiki and also wiki search. Both features are invaluable for examining wiki content. Without those two features I am completely lost. Now the only way how to examine the wiki is the worst one - traversing links from front page. Yuck! This is not ideal for wiki at all due to its chaotic nature and notoriously bad structure. Please add anonymous editing. There was discussion about this in the list, I think at that time there was general consensus that anonymous editing is quite important and then you took this feature away. http://www.gossamer-threads.com/lists/maemo/developers/11259#11259 Please make wiki easier to edit (less steps, less fancy stuff). The old way with preview and textbox on same page was easy, fast and was even usable from the device itself. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Features to improve the platform
Koen Kooi wrote: > 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). > Still this may not be very practical. How it works when you want to stop using usb storage and access your card from the device but want to continue to use usbnet (i.e. you do not want to remove the cable)? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 3d chipset...
Guard][an wrote: > there are bus and memory bandwidth considerations > that somehow make the use of the 3d chipset useless on the current hardware > can someone confirm this ? Well the problem is in pushing full frames from internal framebuffer in SRAM to external memory on video chip. This means you won't have best framerate when doing fullscreen updates in 800x480. But with scaled down output it shouldn't be so bad. Also this limitation is not related to suggested usage. It would be nice to have e.g. translucent virtual keyboard overlaying original window instead of shrinking it. It is perhaps not useful everytimes but there are usecases where constantly resizing main window on each text entry is annoying, hurts performance or is even not possible (like fullscreen SDL game). So the quick answer is - no it is not useless. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Wish list request for DSP EAP_* function header/information
Simon Pickering wrote: > This would allow us to write code to use the audio output (input?) > capabilities > of the N800 (and probably 770) and allow people to hack at writing more dsp > sinks for various music/sound formats (e.g. OGG, DTMF, G.729, etc.) Just FYI, Vorbis/Tremor is ported to TI DSP so this audio API is one remaining piece of the puzzle. True that we could return decoded data back to arm and then play it over pcm (i.e. push back to DSP) but real ogg audio sink would be better. For tremor on dsp check http://www.google.cz/search?q=sandvall+dsp one copy is also here http://fanoush.wz.cz/maemo/sandvall-thesis.pdf http://fanoush.wz.cz/maemo/sandvall-tremor.patch It was already mentioned here few times, I'm repeating it just in case someone wants to play with it. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 770 Java HW Acceleration (and JVM support)
Sebastian Mancke wrote: > You can find a small example in my jalimo slides from linuxtag2007 > (slide 33ff). > > http://www.jalimo.org/wiki/doku.php?id=news:linuxtag2007 Yes, that was it, thanks. I've seen the pdf version http://www.jalimo.org/documents/jalimo-slides_english_linuxtag2007.pdf > > To use the jazelle extension, we would need *much* more knowledge about it. > Yes, definitely. But still this shows a way and someone can start playing with it. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Features to improve the platform
Kalle Valo wrote: > Yeah, we do that also in-house sometimes. It's just pain to setup > (remove and insert kernel modules etc.), I wish that there would be an > easier way to do that. > Never tried usbnet but with bluetooth PAN it is really painless once you have it set up once (see http://www.internettablettalk.com/forums/showthread.php?p=52174#post52174 except the dummy_wlan_down part and default gateway and dns setup). No messing with modules except inserting bnep.ko once on N770. I guess usb can be more problematic if you need usb storage too. Bluetooth is ideal for this if you have BT on PC (unless you perhaps care about the WLAN radio part which may be affected by bluetooth). Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: 770 Java HW Acceleration (and JVM support)
Jason Mills wrote: > ...and before I forget it... these two links are very tempting: > > http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedPlatformsNokia > 770 > > http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedPlatformsNokia > 800 Can't find it now but there is some beginning of jazelle reverse engineering effort documented somewhere (maemo wiki?). Nothing big, just switching CPU to java mode and back but still this is one option for future. Official jazelle support would be closed and shipped with some proprietary JVM anyway which is not very interesting. > > > Now I wish I'd taken advantage of the Woot.com deal on '770 units a few days > back! > there is still the buy.com deal http://www.buy.com/retail/Product.asp?sku=204081472 For such price I would buy one spare N770 too so I could try some N770 modding (like hacking rs-mmc slot and fiting SD card inside - when booting from mmc I don't remove the card anyway), unfortunately they don't ship to my country. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Features to improve the platform
Murray Cumming wrote: > Debugging connection requests and disconnects is incredibly awkward on > the device only. You have to use an xterm because you can't ssh in, > because the whole point is that the connection is going up and down and > changing to different Access Points. You don't need Connection manager and maemo IAP connections for ssh. You can easily bypass it and connect to device over bluetooth PAN or usbnet and then play with wi-fi and Connection manager to your heart's content while your ssh connection is still running. Works fine, I have tried this many times. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N800 experimental host mode patches available
Frantisek Dufka wrote: > I was thinking about > building short usb female to female adapter so it could work together > with normal mini-usb cable. Also the alternative is one of gender changers (example here http://usbfirewire.com/uconverters.html) The female to female can be used with two cables. There is also A Female to B Male which could be used with one cable (i.e you can attach digital camera with its own cable and this adapter only). Also this one can be modified to shortcut that fifth pin. But maybe this one can be too heavy and put more pressure on n800 usb connector. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 experimental host mode patches available
Kees Jongenburger wrote: > On a side note I followed the HowTo EASILY Boot From MMC card > and I now have "boot from usb disk" should that work with the same patch? In theory yes but you need to have correct modules and root device name set for the bootmenu item in bootmenu.conf, it won't work out of box. linuxrc script in initfs on N800 doesn't have any special suppport for this (n770 one has so there is 'usb' root device). But it should still work if the device automatically switches itself to host mode and detects usb device correctly. Maybe there can be also timing problem if you set usb as default boot device and skip the menu. Anyway, if you make it working, let me know your bootmenu.conf settings so I can add it to the n800 bootmenu.conf example configuration. Also if you need to set host mode by hand on boot it can be solved too in bootmenu.sh (see how poweroff is done). I'd like to try it too but don't have cable yet. I was thinking about building short usb female to female adapter so it could work together with normal mini-usb cable. Slight disadvantage is that probably that fifth pin for host mode autodetection doesn't have wire in the cable so I cannot shortcut it in the short adapter I want to build => software switching must be used. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Java applet on the Nokia N800 with a web browser.
magda chelly wrote: > Hello everybody, > > I would like to ask you if it's possible to visualize > an applet in JAVA, using a web browser on the Nokia > N800. In fact, I tried it, but it doesn't start. > Should I install something. How is this related to maemo-developers? The list is described as "Strictly for maemo development related discussions.", see https://maemo.org/mailman/listinfo/maemo-developers > Thank you for any suggestion. One suggestion for you is to read this http://www.catb.org/~esr/faqs/smart-questions.html and especially chapter "Before You Ask" and "When You Ask" In your posts you repeatedly break many rules mentioned there. Please stop doing this. Searchable list archives are here: http://www.gossamer-threads.com/lists/maemo/ Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Identifying platform in Python code
Daniel Stone wrote: > On Mon, Jun 04, 2007 at 09:49:39PM +0200, ext Frantisek Dufka wrote: >> Jeffrey Barish wrote: >>> How do I determine in my code that I am running on the N800? Neither >>> os.name nor sys.platform gets the job done. The former returns "posix", >>> the latter "linux2", and I get the same strings when I run on Ubuntu. >> Check /etc/osso_software_version file. This is the firmware version. >> RX-34 on the beginning means N800. Of course this is not very portable >> and may fail in future but currently it work for both N770 and N800. > > If you're going to check the filesystem, hit up /proc/component_version. > Right, forgot about that one. /proc/component_version is better for knowing specific hardware, osso_software_version is better if you are interested in which specific firmware is installed (and in fact for N770 hacker edition it contains RX-34 by mistake so component_version is safer bet). But the real question is why you want to know it in the first place. Maybe there is better way to check some specific feature instead of checking hardware version. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Identifying platform in Python code
Jeffrey Barish wrote: > How do I determine in my code that I am running on the N800? Neither > os.name nor sys.platform gets the job done. The former returns "posix", > the latter "linux2", and I get the same strings when I run on Ubuntu. Check /etc/osso_software_version file. This is the firmware version. RX-34 on the beginning means N800. Of course this is not very portable and may fail in future but currently it work for both N770 and N800. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: What's wrong with folder browsing?
Gustavo Sverzut Barbieri wrote: > > I don't like the "timer" thing, but yes, it can help and I've already > considered it. > > As for reboot, remember that on reboot, it's not re-parsed (files are > not opened), just re-scanned (stat and compare mtimes). We must do > this stat in order to check for files that changed elsewhere. Not sure how Canola works. Maybe metalayer-crawler does it. We don't have sources, right? For both we can only guess what you guys do in the code. > > keep db in mmc is problematic, since users want a unified view of > every data and this requires us to merge selects from every db, either > by creating a virtual db with data or doing that with code (our own > virtual db). That creates more problems than it saves. Maybe. Don't know implementation. I just know that if some media is not accessible there is no point of keeping the metadata so having them together with data seems to make sense. Even if it is moderately complex it may be worth the effort since it seems like the right thing (to have more metadata databases). This may even allow you to share the index with some desktop application when you use the card with usb reader and even create index on PC to save tablet power (which is how itunes may work). > >> You can also do MD5 sum of directory listing (even output of ls -R or >> -lR) and do not scan files at all if listing hash is same. > > this is easy, but not much faster than the stats... Sure if you stat directories recursively it is same. The idea was just to avoid reading the file data as much as possible. At least metalayerc-crawler seems to be very dumb at this and recreates whole database (haven't seen sources but it takes ages and does a lot of write i/o after reboot or card reinsert whne there is no change in data on the card). Another hint could be to check free available space, if it is same like before it is unlikely there was some change and even recursive scan can be skipped. > and you still may > have inconsistencies, imagine you noticed incorrect id3 and then you > plugged in your device using USB cable (your media get unmounted), use > some app on your pc to fix those incorrect id3 and then remove the > cable, you want your data to be updated. I think you (not just Canola, metalayer-crawler too) are penalizing user for many scenarios that are very unlikely causing the most frequent use case to be slow up to the point of being unusable. In such unlikely situation user should always have option to manually do the rescan from control panel applet (possibly also with selecting subtree with the change). So the idea is not to have perfect implementation but fast one solving most frequent cases (1. no change, 2. just files added/removed) with possibility to do manual rescan. There could be even some slider in control panel applet with fast-slower-accurate choice. > I hope in future we can just use device-wide db and do no scanning at > all. If metalayer-crawler export its data somehow, I'd be really glad > to remove the scanning from Canola, it no benefit having it on our > side. Definitely, you guys should talk together and do one best implementation :-) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: What's wrong with folder browsing?
Gustavo Sverzut Barbieri wrote: > > Just hack scripts (both init.d and dbus/service) and launch it with > lower priority, it should be the default in next release. This still puts big stress on memory subsystem and slows device by flushing caches. > - data is deleted when SD is removed in order to avoid DB growing > indefinitely, maybe you'll not see the same card again (it was a > friend's SD, for example) or data there will not be present anytime > soon (you just deleted those files using PC or other device) You could have option to purge old data when card was not seen for some time (like few days). It is much better then scanning card again when rebooting or quick removal and reinsert (can be quite frequent with some use cases). Also if you fear of huge DB size you may consider to optionally keep DB directly on card with media files if it is writable and there is free space and also user sets it in preferences (or even if user moves it by hand there if canola is smart enough to keep one DB per scanned card, why not?). You can also do MD5 sum of directory listing (even output of ls -R or -lR) and do not scan files at all if listing hash is same. Same applies to metalayer-crawler of course. > > it's always a trade off Well, sometimes it can be also sloppy coding ;-) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: IT OS 2007 Hacker edition
Daniel Stone wrote: > On Thu, May 17, 2007 at 04:08:53PM +0200, ext Frantisek Dufka wrote: >> As for kernel few examples are >> >> - proper YUV420 support in framebuffer update ioctl, stock N770 kernel >> has this broken, fix is easy, would be useful for mplayer > > Sure, I have no problem with this; I guess the best way would be to list > all the patches somewhere as part of a submission (e.g. on a wiki, not > on the list). Ok, will attach to OS2007on700 tracker https://garage.maemo.org/tracker/?atid=683&group_id=164 and send you a link. BTW I have also added waiting for yyc converter to yuv modes which is not there for N770 kernel with Tornado despite being documented in specs while N800 has the code when the very same bit of NDISP_CTRL_STATUS register tested there is documented as reserved and having default value 0 in my copy of S1D13745 specs (i.e no longer having yyc converter finished bit there). > >> - HW rotation support in framebuffer update ioctl > > As I've said, this patch is conceptually broken. Fixing it so that it > uses the stock standard fbdev API instead of rolling our own is possible > for Hailstorm, at least, but I don't know about Tornado. I'd have to > check. I'm not sure which patch you mean. Do you mean patch that could do this http://lemody.blogspot.com/2005/11/xrandr-o-2.html i.e. fullscreen 180 degree rotation transparent to rest of the system? This should perhaps be really hooked somehow to standard fbdev rotation API but I was thinking about something different. I was thinking about rotation of specific updated rectangle/square i.e. conceptually same thing like turning on pixel doubling flag for specific rectangle update or choosing different pixel color format for specific update. Such rotation feature could be useful and would IMO fit to same place in framebuffer code like the pixel doubling flag and is not related to fb rotation API. Or is there support for specific rectangle rotation while rest of framebuffer stays non-rotated? I guess not because even the manual update mode with rectangle updates is there because of having external video chip with own RAM which is not very common. But anyway, does this mean that N770 kernel is still maintained inside Nokia so there is someone (you) who will accept patches? Of course I can submit it to linux-omap (and I probably will) but current omap tree is not very useful for us, mere mortals, who prefer initfs/rootfs with all its proprietary bits working. > > I'm not sure about this; guess we'd have to dig up the schematics to > find out for sure. I guess getting wider testing would be the easiest > way at this point. You mean someone with different/newer N770 hardware? This would be interesting. I know there are two firmwares for wlan chips, newer N770 kernel supports two differnt LCD display panels and there is even code that suggests some devices have mmc slot capable of 4bit mode. So is there someone in this list with newer HW build than 1602 (see /proc/component_version) who would share dmesg output of boot sequence and would be willing to test kernel and mplayer with tearsync feature? Good candidate is N770 device that loads 3826.arm wlan firmware on boot or have ls041y3 LCD panel (mine loads 3825.arm firmware and have lph8923 panel). > > You might want to just port the whole omapfb back to .16, as there have > been a ton of changes. That's what I was trying to avoid. Are those features (framebuffer in SRAM, more planes) useful for N770 device? I guess not very much. Perhaps best for verifying that it is not my bug is booting 2.6.18 with custom rootfs instead. Regards, Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: IT OS 2007 Hacker edition
[EMAIL PROTECTED] wrote: > >> is there any progress? Where should we discuss >> issues/suggestions related to this? > > https://garage.maemo.org/projects/os2007on770/ > > You don't need to ask permission to push there. :) > Right, so correct place for discussion should be here https://garage.maemo.org/forum/forum.php?forum_id=612 and not this list? Well I'm not sure Daniel would find my mail over there :-) It is good place to attach patches but I'd prefer some discussion first and this list seems to me like the best place. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
IT OS 2007 Hacker edition
Carlos Guerreiro wrote: > >> We will keep working on the IT OS 2007 Hacker edition for the 770. We >> will go through IT OS 2006 bugs submitted in maemo’s Bugzilla, trying to >> solve at least the most relevant and the ones already fixed in the >> official IT OS 2007. We will release the fixes in updated images, all of >> them unofficial and to be used at your own risk. We can’t make any >> promise on performance levels or specific bug fixes, but hopefully you >> will be happier than now with the results. >> > Hi, > > Time to get back to work on this. > > Work on the OS 2007 / 770 hacker edition happens in the OS2007on770 > Garage project [1] Hi Carlos, is there any progress? Where should we discuss issues/suggestions related to this? I have one question/suggestion. Since the hacker edition is unsupported can we as a community push some changes to hacker edition firmware hosted on maemo site (i.e. kernel,initfs,rootfs)? I know this is not possible for supported releases for many reasons but hacker edition is different so maybe some tweaks can be applied and we could affect what is there by default? Maybe there are some useful tweaks that are cumbersome to install for some less advanced users but good enough to be in the firmware by default. As for kernel few examples are - proper YUV420 support in framebuffer update ioctl, stock N770 kernel has this broken, fix is easy, would be useful for mplayer - HW rotation support in framebuffer update ioctl - maybe some things taken from newer N800 kernel, tearsync support would be nice as one example but this is currently not working for me, sadly I got no reply to http://maemo.org/pipermail/maemo-developers/2007-May/010156.html As for initfs maybe bootmenu could be useful. As for rootfs maybe we could add some packages by default (like ogg support etc) or in future tweak some packages (SDL, X server). So what is the idea, is Hacker Edition made exclusively by Nokia (perhaps blessed by its lawyers or something) or can this be community thing so such tweaks are possible? Also I'd like to know where are you heading with next OS2007 HE release. Do you plan to switch to newer kernel or stick with old 2.6.16 and initfs? Would be nice to know if backporting things to 2.6.16 is waste of time or not. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 experimental host mode patches available
Hello, any tips how to make custom mini-B to female A cable so that N800 switches mode automatically? Which two wires I need to shortcut in the cable? I can see the pinout here http://pinouts.ru/Slots/USB_pinout.shtml but don't see USB ID pin. Is it the fifth pin on mini-b connector (which may have no wire in the cable)? Thanks. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 experimental host mode patches available
Marcell Lengyel wrote: > Hi, > > I tried the usb host mode on my N800, but I did not get it working. Here's > what I did: > - In scratchbox SDK_ARMEL I downloaded the kernel-source-rx-34_2.6.18-osso40 > sources, > - Applied the patches-tusb-n800-2007-05-04.tar.gz patch set from muru.com (it > did apply cleanly) > - make n800_defconfig Unless those patches modify default config you need to enable usb host mode drivers in kernel configuration. You also need drivers for peripherials - for usb harddrive you need scsi and usb storage drivers. If you want to use 'make menuconfig', check also this http://www.gossamer-threads.com/lists/maemo/developers/20850#20850 Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
N770 tearsync problems
Hello, last week I tried to backport tearsync support from n800 kernel source to latest 2.6.16 released for n770. The result compiles fine and boots on device and works great until one actually tries to use the tearsync feature. It doesn't work correctly. First framebuffer update with tearsync flag hangs. All the tearsync setup and enable code for hwa742 and sossi seems to be called but in the end the update hangs waiting for sossi interrupt that never comes. 'cat /proc/interrupts | grep sossi' has zero for sossi_match interrupt. 51: 0 sossi_match So my questions are: Does the hardware support it? I have one of the first developer devices (hw build 1602), is it possible that tearsync pins between epson chip and sossi are simply not connected? Kernel source suggests that it is always connected (unlike some other features that are conditionally checked at runtime). If it is connected do I need to enable the interrupt line or something else except acquiring the interrupt in sossi.c? The backport was not simple copy/paste since the omapfb code changed a lot (more planes, support for fb in sram) and even sossi.c and hwa742.c had some changes. First I did line by line merge to get only the code that looked related to tearsync (files sossi.c, hwa742.c omapfb_main.c and some headers to have missing definitions). Later I also tried to do more changes so in the end the hwa742.c and sossi.c are exact copies of those files in n800 tree but there is no change and it still doesn't work (i.e hangs possibly waiting for interrupt). I also tried to compile 2.6.18 source with abandoned kernel patch for hacker edition and also current omap git source. Both compile and boot fine (i.e display works) but the initfs is confused and does not even start dsme and then reboots. This is also mentioned in http://maemo.org/community/wiki/Os2007HackerEditionArchives "linuxrc from old OS2006 initfs starts, but gets confused because of different kernel and reboots. This was expected behaviour" So before trying to make my own root filesystem for verifying newer kernels I'd like to know whether there is any chance this tearsync code will actually work. Or is there any other gotcha in 2.6.16? Maybe the interrupt code is different between 2.6.16 and 2.6.18? I had to replace include linux/irq.h for linux/interrupt.h since irq.h in 2.6.16 had some errors and other code (mmc driver) included linux/interrupt.h. Thanks for any tips. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Xsp pixel-doubling solutions for Nokia 770?
Eero Tamminen wrote: ext Markku Vire wrote: If we need one fullscreen app, why not to launch a new X-session that uses this lower, pixel-doubled resolution and then run our SDL game there? Other applications would not recognize anything. Same problem as using framebuffer directly. How user switches to another application? How to invoke power menu properly etc. So to sum it up - for this to be workable solution, not hack with various nasty side effects it should: 1. not crash due to pixeldoubling mode left turned on by mistake 2. allow system dialogs and infoprints to overlay active window and have normal density (i.e. 800x480) 3. allow SDL apps to use half resolution(s) easily 4. optionally allow to intermix updates both resolutions at it suits developer (not portable, maemo specific port) 4. needs to work anyway due to 2. and also 3. can be written by using 4. Still this leads me to original suggestion of having pixel doubling to be not persinsten flag but property of rectangle update. If this is not possible to do in X the most sane solution IMO is to hack direct framebuffer access it into SDL to do such updates possibly together with emulating different resolutions in SDL too. Since we have sources there can be community volunteers to do it (including myself). The question is, does it have any chance to be merged to official firmware? Expecting people to update SDL just for your game is not good. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Toolchain upgrade? (Was: Instructions cache flush on ARM)
Siarhei Siamashka wrote: I'm not going to statically link with glibc, but only with libstdc++ (standard c++ library). There are a few known tricks to make gcc link with libstdc++ statically, but dynamically with all the rest of libraries. One of them is creating a symlink to libstdc++.a in some empty directory and specify this directory with -L option in gcc command line. When gcc will start linking, it will be fooled to link with a static libstdc++ library. But I guess just killing libstdc++.so in scratchbox will do the the job. After that, the compiler theoretically should create binaries which should run with no problems on the device even for c++ applications. I used this trick for scummvm for IT2005. It works as long as your program does not load dynamically (directly or indirectly) some other c++ code compiled with stdc++ too e.g. when using some plugins in your application or other libraries written in C++. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 & Video playback
Siarhei Siamashka wrote: If decoding time for each frame will never exceed 28-29ms (which is a tough limitation, cpu usage is not uniform), video playback without dropping any frames will be possible even with tearsync enabled. Would a double or multiple buffering help with this? Does mplayer use different threads for displaying and decoding and decode frames in advance? ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Fwd: Compiling latest kernel (from kernel.org, linux-omap git version) in n800
Leandro Melo de Sales wrote: Guillerm, thanks for your reply. So, about the use of --force-vermagic with busybox modprobe... What should I have to do to make busybox modprobe support --force-vermagic? get modprobe source code, and...? How about to use n770? There is slightly quicker/easier but more hackish and definitely wrong way which may or may not work. You can set kernel version in main kernel Makefile to be what you want (i.e. the older one, see /proc/version on device) and then recompile kernel. Modules will load without changing insmod/modprobe but some may crash. Those that will crash need recompiling. The proprietary umac could works since in theory it should not use kernel API. The WLAN interface driver source code is available or it is like n800? Hopefully yes, in Maemo garage. So if this one will crash you could recompile it. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Documenting maemo pearls (was Re: N800 & Video playback)
Daniel Stone wrote: If there's anything you want to know directly, just ask on the list. I tend to deal with email when I'm not actively coding/building/etc, which is how I justify it. A wiki would require me to sit down for a while and really think about stuff, and I don't really have huge blocks of time available to me. But yeah, always happy to answer direct questions. Disadvantage is that it becomes lost in the list archive. Even when you do search the archive it is hard to know proper keywords and it is very likely your brilliant answer will not be found. Many times I am 100% sure the answer is in the list since I remember someone answered it some time ago but even then it is hard or impossible to find. Gustavo Sverzut Barbieri wrote: Quim, while "formal" documents as those maemo.org provides are cool, it consumes a lot of resources... doing simple but correct/consistent wiki is good enough. Maybe we could setup a "techday" that we'd meet on IRC and document some topics on Wiki. It would be great to get some people with deep knowledge on hw issues, like Daniel, Siarhei and Eero... I could help with writing and organization, as I never dig on hw that much (but I'll need to do so really soon). If you can manage the timezones, that would probably be okay. America/Europe is doable if you guys get up early, just as long as no-one from Asia-Pacific wants to join in ... This techday is good idea. Sadly it depends on people being available at that time and most probably most people providing interesting answers may be the most busy ones. I tend to avoid IRC because it is big waste of time. There are few gems too found in the archives (thanks Marius G. ;-) but 98% is just babble and FAQs repeated again and again. However I would try to join such techday on IRC (not that I expect my presence to be useful to others). It would be nice to have such tech days regulary preferably with few topics set in advance. But still I don't know how real it is to achieve this and whether wiki or mailing list is not better suited for this after all. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 & Video playback
Kalle Vahlman wrote: I put the deb up at: http://iki.fi/zuh/xserver-xomap_1.1.99.3-0.zuh2_armel.deb until I get it to the repository. This version also has the composite extension enabled, but AFAIK it does not depend on the libs or change server behaviour if composite is not specifically used. The server *should* be compiled with '-mcpu=arm1136j-s -mfpu=vfp -mfloat-abi=softfp -O2', but as I had troubles with the SBOX_EXTRA_COMPILER_ARGS env var being honored some time ago I'm not guaranteeing it at the moment ;) I also succeeded in making the deb: http://fanoush.wz.cz/maemo/xserver-xomap_1.1.99.3-0osso31_armel.deb This one is compiled as thumb (except the ASM code) and no special CPU flags so it can be verified if there is any slowdown. Thumb mode saves approx. 300kb of executable size. It seems to be used by default in firmware images. Kalle, did it link properly for you? With the patch the final Xomap link did not add the ASM code, I had to do it by hand. I didn't find proper place in Makefile for it to be added to libomap.a, the place patched by Siarhei was ignored by the build process for me. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 & Video playback
Frantisek Dufka wrote: [sbox-SDK_ARMEL: ~/x/xorg-server-1.1.99.3] > patch -p1 <../xomap_yuv420patch.diff patching file hw/kdrive/omap/Makefile.am Hunk #1 FAILED at 1. Hunk #2 FAILED at 34. 2 out of 2 hunks FAILED -- saving rejects to file hw/kdrive/omap/Makefile.am.rej patching file hw/kdrive/omap/omap_colorconv.h patching file hw/kdrive/omap/omap_colorconv.S patching file hw/kdrive/omap/omap_video.c Hunk #1 FAILED at 39. Hunk #2 FAILED at 468. Hunk #3 FAILED at 491. 3 out of 3 hunks FAILED -- saving rejects to file hw/kdrive/omap/omap_video.c.rej Sorry, my fault, mystery solved. Saved attachement in Thunderbird in Windows XP, then moved to Ubuntu inside VMware. The problem was caused by DOS CR+LF line endings, patch doesn't like it. Recoded to unix linefeeds and now it applies cleanly. I'm using Windows a lot, it is strange this never happened to me yet. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 & Video playback
Siarhei Siamashka wrote: OK, here is this untested a patch for xserver to add ARMv6 optimized YUV420 color format conversion. Theoretically it should compile (I did not try to build xserver myself though) and work. If it refuses to compile, fixing the patch should be not too difficult. It does not apply for me but should be trivial to fix. [sbox-SDK_ARMEL: ~/x/xorg-server-1.1.99.3] > patch -p1 <../xomap_yuv420patch.diff patching file hw/kdrive/omap/Makefile.am Hunk #1 FAILED at 1. Hunk #2 FAILED at 34. 2 out of 2 hunks FAILED -- saving rejects to file hw/kdrive/omap/Makefile.am.rej patching file hw/kdrive/omap/omap_colorconv.h patching file hw/kdrive/omap/omap_colorconv.S patching file hw/kdrive/omap/omap_video.c Hunk #1 FAILED at 39. Hunk #2 FAILED at 468. Hunk #3 FAILED at 491. 3 out of 3 hunks FAILED -- saving rejects to file hw/kdrive/omap/omap_video.c.rej Will try this evening. I wonder who has older x server version. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Next steps in the future of our beloved Nokia 770
Quim Gil wrote: We will keep working on the IT OS 2007 Hacker edition for the 770. Excellent decision. Thank you. This could help close the gap between N770 and N800 users and avoid platform fragmentation and maybe even make life easier for developers. But maybe not, see below. So what is the future, do you want just fix bugs or can this be used as a test bed of future device vs OS independence? As there are probably more devices in the pipeline and some will definitely run same major version of OS but have different hardware this problem must be solved in future anyway. How we can reflect this with maemo SDK and repository structure? Looks like there are such things as subarchitecture and flavors in Debian. http://www.debian.org/releases/stable/powerpc/ch02s01.html.en I have reported the top of the iceberg as a bug here https://garage.maemo.org/tracker/index.php?func=detail&aid=804&group_id=164&atid=681 But it needs some thinking. How can developers target specific devices with same OS but different hardware? Some developers may already take eqaution Bora = N800 as granted which means some packages will not run on n770 due to compiler flags and other hw specific assumptions. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: recompiling x server
Daniel Stone wrote: On Mon, Apr 30, 2007 at 06:13:48PM +0200, ext Frantisek Dufka wrote: Then x-server builds fine and produce debs. What is strange that /usr/bin/Xomap on device with latest IT2006 firmware has ~600kb but my executable in debian/xserver-xomap/usr/bin/Xomap has 1.2MB. When setting export DEB_BUILD_OPTIONS=thumb before build the result has ~900kb. Tried strip just to be sure and size did not change. What other options are needed to reproduce device size? Did the strip succeed? file should tell you whether or not it's stripped. Aside from that, I can't think of anything else, as I build in a Scratchbox target myself, and it seems to work okay. Sorry, I was using Bora arm target. I should name them properly, forgot that SDK_ARM is Bora now :-) So in fact I have build xorg-server_1.1.99.3-0osso31 which is in IT2007. Size on device is approx 1.2MB too. In IT2006 it is xserver-kdrive_6.6.3-28 and package is not named xorg-server but xserver-xomap. For 2.2 unmet dependencies are dpkg-checkbuilddeps: Unmet build dependencies: flex libxproto-composite libxproto-damage libxproto-colorkey libxproto-resource libxres-dev libxkbfile-dev libxdmcp-dev This is worse and indeed does not build at all. I have only following repositories in /etc/apt/sources.list deb http://repository.maemo.org/ gregale free non-free deb-src http://repository.maemo.org/ gregale free non-free I guess adding older 2.1 or 2.0 ones is not good idea. So this looks much harder then in Bora. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
recompiling x server
Daniel Stone wrote: It's completely safe to upgrade from a deb if it's not broken. If you set up a standard Maemo build environment and run apt-get source xorg-server and apt-get build-dep xorg-server, it should work just fine, in theory. In reality in 2.2 arm target there are unmet dependencies for flex and quilt. Flex is available in scratchbox, quilt not. I have downloaded quilt sources from http://packages.debian.org/unstable/source/quilt It needs other stuff when building. With -d the build breaks on missing hevea. Luckily make install in quilt build directory installs quilt executable. Then x-server builds fine and produce debs. What is strange that /usr/bin/Xomap on device with latest IT2006 firmware has ~600kb but my executable in debian/xserver-xomap/usr/bin/Xomap has 1.2MB. When setting export DEB_BUILD_OPTIONS=thumb before build the result has ~900kb. Tried strip just to be sure and size did not change. What other options are needed to reproduce device size? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Xsp pixel-doubling solutions for Nokia 770?
Daniel Stone wrote: On Mon, Apr 30, 2007 at 09:34:38AM +0200, ext Frantisek Dufka wrote: You mean, modify every single drawing X request in the X protocol so it contains flags, meaning that we have to change every drawing-related function in -- on average -- ten (at least) places in the server codebase, rendering us incompatible with the standard X server codebase, as well as the X protocol? Well, what I meant is instead of having XSPSetPixelDoubling call in Xsp we would have XSPBlitRectangle with addition flags - i.e. something still non-standard but easier to use. If this cannot be done then it is bad luck. If hardware has useful feature which does not fit the design, using extension is not that bad. The entire concept is a hack around games not running quickly enough in full resolution. Yes, if you think different lower resolutions implemented in graphics cards are hacks around games not running quickly then yes. Why not run everything in highest resolution and true color. That will solve all those problems. Well, except the speed. But this is temporary until hardware catches up :-) Specifying that pixels must be exactly _doubled_ is a hack around both the performance issues and a lack of resolution independence. Apparently an important one, if you happen to like SDL games, but a hack nonetheless. Yes limiting ourselves to doubling is bad. Why not to add custom ratio if N800 can do that. This all leads to request to have some more advanced gaming API. Sadly this is probably not what internet tablets are currently designed for. Gamers are big target group and this device is meant for entertainment so maybe extending target audience to gamers in not that bad idea. Gaming devices are moving online too so this is direct competition. Why to buy internet tablet if better Sony or Nintendo device in future will do this too plus gaming. Unfortunately gaming business has complicated rules similar in complexity to devices with GSM radio. BTW are internet tablets in same Nokia multimedia division as N-Gage? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Xsp pixel-doubling solutions for Nokia 770?
Eero Tamminen wrote: And if the game doesn't disable the double pixeling properly (e.g. if it crashes or freezes), user needs to reboot the device. Not very nice either... So what happened to idea mentioned here year ago to modify Xsp (or whatever) API so that pixel doubling is flag of each display update separately? I.e. every update would be not pixel doubled unless told so by flag with each update. This is how it works on kernel framebuffer level anyway. It is bad to turn in on and off because any other display update (infoprint) can mess it up. If we had blitting API in Xsp with pixel doubling flag settable per update this problem would go away. Well in fact we have this api - framebuffer ioctl but it is not very nice solution. Daniel Stone wrote: > > I don't like it as it's far too ITOS-specific (I won't be satisfied > until XSP no longer exists). It'll probably be replaced with RandR some > time in the future, even if the fixed resolution choices are only > 800x480 and 400x240. > Pixel doubled resolutions would be nice and would be improvement over current situation indeed. What we will miss with this solution is having some parts of screen pixel doubled and some not like nice control area with nice static graphics and main pixel doubled game area. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Boot Screen and Start App at Boot up
J B wrote: First, I have been unable to replace the first of the 3 boot up screens. Which is the second one you have replaced? AFAIK the first one is stored directly in bootloader since it is shown before kernel boots. The second one is in initfs in /mnt/initfs/usr/share/images/logo-nokia This is the big blue "NOKIA" word. Can be verified via # chroot /mnt/initfs /usr/bin/show_image -i /usr/share/images/logo-nokia Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Continuous reboot problem with the N770 hacker edition
Eero Tamminen wrote: That shouldn't happen. Happened to me with N770 and IT2006. Just one solid hangup while web browsing, watchdog reboot and I had infinite reboot loop. Also I have lost some gconf preferences more times when device rebooted randomly. Missing preference may cause crash for some system application that expects some setting to be always present. JFFS2 keeps the internal filesystem in consistent state although the filesystem hadn't be properly unmounted (unlike the VFAT on MMC cards). Yes that is not a problem. Some individual files could get only partially written, but all applications should be doing such writes safely (write to temp file and rename once writing is finished). This is the problem. It is not common at all to write to files in such way. In case you want to apppend some data to existing file it is not optimal to create new temporary file, copy all data and add few bytes. You seriously can't expect people writing code in such way. I still think this watchdog thing is another legacy we have from Nokia as a phone company. It makes perfect sense for dumb phone. It makes less sense for computer. Yes when device locks up you need a way to reset it. That is why you have reset button on computer and also reset hole on every PDA. I know it is internet tablet not computer or PDA but also Nokia should know that *this is not a phone* ;-) With reset hole one can reset device when (s)he wants. Watchdog may not make things worse when device locks up solid (i.e. kernel bug or feature) but rebooting device when some process dies of when things take too long can make more damage than benefit. I know this is hard to detect so my solution is to provide reset hole and do not try to guess. User probably can notice this situation and act accordingly. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Continuous reboot problem with the N770 hacker edition
Rainer Dorsch wrote: Hi Markku, I have no idea how I can replace the binary when the N770 is rebooting itself before the desktop is up :-( Is that possible? http://maemo.org/maemowiki/HowTo_EASILY_Boot_From_MMC_card If you haven't this installed then it is almost impossible to recover now but you may consider it for future. With this installed you may boot working system and mount and fix the broken one. Also if you really have some important data there you may prepare bootable mmc card on desktop PC with linux but it is harder. You need to format card as ext2 and extract rootfs.jffs2 from firmware image to it (try Google for instructions how to mount jffs2 image) and set root device via flasher. Are there any plans to update the N770 hacker edition image in near future to fix bugs like this? If your reboot loop is caused by rss applet then upgrading could help but reboot loop in general has more causes and is not specific to IT2007. It may happen sooner or later on any Nokia tablet with any IT 200x system so far. If you have bad luck even first device crash and watchdog reboot can cause infinite reboot loop if the device was in the middle of some 'sensitive' write. If yes, I would probably wait for a few days and test the updated image (and would be happy to pick up the other improvements;-) I have already asked here in the list two or three times about future of hacker edition but got no reply. It is possible to update some packages from Bora 3.1 repository and it should be also possible to recreate deb files on n800 with upgraded firmware and upgrade them on N770 hacker edition via dpkg (except those which are modified for hacker edition and there are no sources). I'm planning to do it when I hit some bug on n770 which is not on my N800. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Fwd: Compiling latest kernel (from kernel.org, linux-omap git version) in n800
Andreas Orfanos wrote: It is against Open Source Software ethics to keep kernel modules proprietary. True Definitely there is a GPL violation here. False Nokia's tables exist today because people kept those GPL moral obligations. True but the opposite may be also true i.e. there would be no Nokia tablet if they could not use proprietary parts. Let's hope things will improve in future and we will have more completely open devices from other manufacturers. Or even from Nokia :-) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Request: Please consider open-sourcing more of the applications
Hanno Zulla wrote: Quim Gil schrieb: On Mon, 2007-04-23 at 12:18 +0200, ext Hanno Zulla wrote: Or is there anything else next to this source-dump on an external developer's website? http://www.bleb.org/software/n800/os2007-src/ Is something like http://repository.maemo.org/pool/bora/free/source/ what you are looking for? Boy, do I feel stupid, once again. It is not the same. Stuff at http://www.bleb.org/software/n800/os2007-src/ contains also sources for osso-pdf-viewer, rss-reader, calculator, SDL games etc. Where are those in bora repository? Should they be here http://repository.maemo.org/pool/bora/non-free/source/ or somewhere else? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 experimental host mode patches available
Larry Battraw wrote: This will of course affect battery life, but your average USB key, keyboard, or mouse shouldn't draw too much. Not sure how you can get it in linux but at least in XP you can check usb hub properties in device manager and see power requirements reported by connected devices. My usb key reports 100mA, sd/mmc card reader 250mA. Don't have usb keyboard around to check. The values should be maximal, i.e. device may in fact consume less. I hope it should not consume more. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 & Video playback
Daniel Stone wrote: Which Epson docs? fanoush.wz.cz/maemo/S1D13745A01SpecRev1.0.gm.zip Got it from Epson Electronics like the one mentioned here http://maemo.org/pipermail/maemo-developers/2006-December/006638.html ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: getty over serial is running
Riku Voipio wrote: This script is unmodified from older releases. What has changed is that kernel has been fixed not to create ttyS0 if serial port is not enabled. This is different problem. Kernel does not create it. dd utility creates is as a regular file since it is told to do so by mistake. The check should now be if [ -c /dev/ttyS0 ] ; then to have the intended effect. Yes, and maybe then for older kernel there should be dd test inside this 'if' block. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: getty over serial is running
Eero Tamminen wrote: Hi, ext Kalle Vahlman wrote: Mystery solved. There is clear bug in the script. While the comment above dd talks about reading it writes to /dev/ttyS0 creating 1 byte regular file in /dev. #test if we can read ttyS0, we have serial console if dd of=/dev/ttyS0 count=1 bs=1 if=/dev/zero ; then So everybody should have getty running in latest FW. Or did I change the script while sleeping? If you did, you did it on my device too. :-) -> Bug to Bugzilla? Reported as https://maemo.org/bugzilla/show_bug.cgi?id=1222 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
getty over serial is running
Frantisek Dufka wrote: Eero Tamminen wrote: Are you building your own kernel which is newer than the one coming with the latest release?I heard that with some of the newer versions /etc/init.d/ttyusb0 could start getty and the script needs to be updated for newer kernel. Well, I do have /dev/ttyS0 device file. dd read test for serial in /etc/init.d/ttyusb0 does not fail Nokia-N800-10:~# /etc/init.d/ttyusb0 start 1+0 records in 1+0 records out so the scripts uncomments line #T0:12345:respawn:/sbin/getty -L ttyS0 115200 vt100 and I see Nokia-N800-10:~# ps -ef | grep getty 1550 root460 S /sbin/getty -L ttyS0 115200 vt100 Workaround is to comment inittab line with two #'s. How is this supposed to work in theory? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: wtmp, getty over serial running, Re: n800 - most libraries compiled witout -fPIC, intentional?
Eero Tamminen wrote: Are you building your own kernel which is newer than the one coming with the latest release?I heard that with some of the newer versions /etc/init.d/ttyusb0 could start getty and the script needs to be updated for newer kernel. Own kernel from bora 3.1 repository with mmc patches from http://intr.overt.org/n800-sdhc-kernel/ and some small (non-invasive) custom hacks. The mmc patches are fairly invasive but just to the mmc layer. I don't have the device now but I'll check details. I definitely remember about having to disable it in inittab more times but that may be because I have more copies of rootfs (1 in flash + 3 on mmc) so it is sometimes hard to track changes :-) But still, getty over ttyS0 should not be enabled at all. I never played with various flasher flags on my N800 yet. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: wtmp
Kemal Hadimli wrote: On 4/18/07, Eero Tamminen <[EMAIL PROTECTED]> wrote: > Sorry, it is in /var/log That I have, but it's only 6kB after several days of device being on/online. mine was 62-megs (of course what i did immediately is ln -sf /dev/null /var/log/wtmp) (latest firmware) OK, so I reopened https://maemo.org/bugzilla/show_bug.cgi?id=448 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: wtmp, getty over serial running, Re: n800 - most libraries compiled witout -fPIC, intentional?
Eero Tamminen wrote: Also there are other issues with the firmware. It looks like /var/run/wtmp growing problem is back (was in some n770 firmware but was solved if I remember correctly). Sorry, it is in /var/log ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
wtmp, getty over serial running, Re: n800 - most libraries compiled witout -fPIC, intentional?
Eero Tamminen wrote: It was a (new) bug noticed too little time before the latest release so there was not enough time to find the root cause & fix & re-build everything needed. The effect is a couple of secs lost at bootup and a couple of MB of RAM lost after device is up (compared to system that would be fully prelinked). I see, thanks. I was thinking that perhaps I missed something and prelink in not that useful or something. Should I bother to create bugzilla entry for this? Also there are other issues with the firmware. It looks like /var/run/wtmp growing problem is back (was in some n770 firmware but was solved if I remember correctly). On n800 it is even created again if deleted so I had to make softlink to /dev/null. Anyone else see this too? I'm not sure if it is caused by something I installed. This should go to bugzilla, right? Another thing is getty running on /dev/ttyS0, I think I removed it from inittab and it appeared again. R&D mode is disabled. Does this cause higher power consumption or is harmless? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
n800 - most libraries compiled witout -fPIC, intentional?
Hello, I tried prelink on latest N800 firmware and it looks like most libraries (gtk,dbus,SDL,..) are not compiled with -fPIC. I see "Cannot prelink against non-PIC shared library" error message for most libraries. Is this a bug or is there a reason? In previous version it was just libSDL, now it is almost everything. Is this some sort of optimization? It may not matter much when using the maemo-invoker but it may cause higher memory consumption and slower dynamic linking for normal cases. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Boot bora as root
Paul Klapperich wrote: By nature of it being a wiki, IMHO you should go ahead and do whatever you want. I'm still now sure what benefit this gives you on an embedded device that doesn't ask for authentication anyway. Yes, some rationale in such wiki page would be nice. I admit I'm baffled by this and would like to achieve enlightenment. How is this useful? Perhaps next step is running everything in kernel mode? ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Kernel compilation (Bora 3.1)
Leandro Melo de Sales wrote: Hi all, I'm trying to compile kernel to n800. I followed the instructions in http://www.maemo.org/platform/docs/howtos/howto_kernel_guide_bora.html, but I can't. After create MaemoKernel target, update the apt repository, I tried to install kernel-source-rx-34 as described in the manual NOt sure what is the problem but try to compile it in normal bora SDK_ARM target if you have one. It may be easier and even save some disk space. From the howto: "It is not mandatory to set up a separate target for kernel compilation but in this example we do it in case you have modified your default armel target in some special way." Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
gtk-server quick test
Hello, I guess I need to create blog, this is typical material for it :-) After the discussion about language bindings here in the list I finally tried gtk-server. It compiles fine in scratchbox but needs ffcall (available in debian). Good news is that it runs fine (at least on os2007on770) and startup speed is quite good even on n770. Both the simple demo with one button and a bit more complex calculator example using glade starts in approx. 1 second :-) This is perfectly usable for small shell hacks that don't need full python and pygtk. In fact it can be used in python without pygtk too. Startup speed is worse then from shell but still better than with pygtk. Here is quick hack including compiled libffcall deb an few examples. http://fanoush.wz.cz/maemo/gtk-server.tgz Binaries were build in bora taget so probably you need device with IT2007 too. For quick test extract it, install the deb and go to gtk-server directory at try to run the demo and calculator scripts. Demo in python obviously needs python :-) Yo can also install menu shortcut for demo calculator via ./install_shortcut.sh (sudo gainroot needed) and try it from menu. Startup speed is similar/same to default calculator tool. Unless there is some major problem with gtk-server (like inability to use methods with pointers) this looks pretty usable and worth packaging. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
scummvm, Re: N770 OS2007 hacker edition made it to the title page of Linux Weekly News
Hanno Zulla wrote: There are three different developers who independently ported ScummVM to Maemo by now. Also, I fear that soon there will be apps that run on previous IT OS distributions but never make it to the current release. Who is the third one? First was Tomas Junnonen who started with 0.8.0. http://770.fs-security.com/scummvm/ He also enabled only scummvm suggesting that others should compile it themselves if they want another engines. Then I continued where he left and enabled more engines and updated it from 0.8.1 to current stable 0.9.1. See http://fanoush.wz.cz/maemo/#scummvm The same package is also in extras repository (from the time when there was only one). This was later renamed to mistral one and others appeared. In fact same .deb package works in all IT2006 and 2007 releases and so far I was lazy to upload same package to all repositories that appered later (2.1,2.2,3.x). There is problem with making source package that could be uploaded and automatically build since currently scummvm does not compile completely out of box. One file in Kyrandia engine causes internal compiler error so it must be compiled with different flags (-O3 works, -O2 and -Os not) and I do it by hand (copy/paste/change) when building the package. So is there anyone else porting scummvm too? Let me know so we don't waste time doing same work. Frantisek ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
closed stuff Re: 0xFFFF: GPL-licensed flasher for n770 and n800
Daniel Stone wrote: On Thu, Apr 12, 2007 at 06:59:55PM -0700, ext Carl Worth wrote: On Sat, 7 Apr 2007 12:07:33 +0200, pancake wrote: The past week I released a gpl-licensed flasher for both Nokia Internet Tablets. Fantastic! I've been very much looking forward to the time where there would be instructions for downloading an entirely Free flasher and Free image to flash to bring the unit into a bootable state from scratch. So this addresses an essential missing piece in that. What else might be missing? Depends on what you mean by 'from scratch'. If the unit does not have a bootloader _at all_, then you need to flash a bootloader via JTAG. But that's mildly convoluted. What elements go into the Nokia fiasco image that cannot be built from Free source? The bootloaders (xloader, 2nd, secondary). And the initfs too. Without it it is hard to initialize wi-fi nad bt chips properly. Of those, which must not be left out in order to have a bootable device? For beginning the most practical and easiest thing is to start with completely free rootfs and go down (initfs,bootloader) when you hit problems or have plenty of time. Kernel is free to modify too but (closed) wi-fi modules depend on it so you can't deviate too much. It looks like you also need to have bme running in your free solution for charging to work. At boot time you also need dsme but I guess/hope it can be killed once it does its job of letting initfs stuff work and you have replacement for the dsme part that keeps the HW watchdog happy. Killing it gives you control of display brightness and blanking. What dsme manages can be guessed from names of libraries in /mnt/initfs/usr/lib/dsme/ For list of critical closed stuff and some explanations check also discussion below http://lwn.net/SubscriberLink/229838/6d98406660425a0e/ When you solve the practical problem of having the system running you will also have redistribution problem for closed parts which you still need. Frantisek ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
Re: Failing to connect with flasher
pancake wrote: > BTW If you are able to boot Maemo but you're not able to connect to NOLO you should probably think on reflashing nolo from the device (using mtdtools). Did you try? Maybe this is not a good idea. I'm not sure bootloader (mtd0) partition is safe to write with mtdutils. So far in every n770 kernel log I've seen on the net is something like this [93032.218597] omap-hw-nand: OMAP NAND Controller rev. 1.1 [93032.218780] NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1 (Samsung NAND 128MiB 1,8V 8-bit) [93032.218994] omap-hw-nand: using PSC values 2, 2, 3 [93032.219116] Scanning device for bad blocks [93032.219238] Bad eraseblock 0 at 0x [93032.253875] 5 cmdlinepart partitions found on MTD device omap-nand [93032.253997] Creating 5 MTD partitions on "omap-nand": [93032.254119] 0x-0x0002 : "bootloader" What makes me nervous is the "Bad eraseblock 0 at 0x" line. This may mean there is really a bad block but most likely it means the oob data has different format than with normal block so writing it with mtdutils would in theory repair/destroy the oob data. Also in reality it means this block cannot be written from linux kernel at all since it cannot write to bad blocks -> mtd utils will not write to first block. This may be good and may be not. Also when I tried nanddump on /dev/mtd0 I got file with all FF and no errors. Maybe first bad block confuses it (-b does not help) maybe there is other problem (dd if=/dev/mtdblock0 works fine however). This means I wouldn't trust nandwrite for writing correct data too. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Failing to connect with flasher
Jeffrey Barish wrote: ioctl(3, USBDEVFS_IOCTL, 0xbfd27320)= -1 ENOTTY (Inappropriate ioctl for device) I have no such line when trying flasher-3.0 in ubuntu 6.10. Attached is gzipped output of strace -o flasher.out ./flasher-3.0 --query-root-device It was run as root. flasher.out.gz Description: Unix tar archive ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Language bindings and priorities
Hi, this is just a theory since I haven't written anything with GUI for Maemo platform yet but my priority would be python -> mono/java -> c++ -> c The last one - c - is pure theory for me for anything bigger. My life is too short and too busy for coding GUIs in C :-) So to sum it up I'd like to see Python and C#/Mono bindings supported. Python for fast prototyping, mono when it grows bigger/slower/hard to maintain. Also Java (with SWT?) would be a nice bonus. Also I'd like to see pure bourne shell 'bindings' for GUI i.e. something like dialog or gtk-server, but these are not real bindings of course so it is a bit off topic. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: libimlayout package
Tomas Junnonen wrote: ext Kimitake Abe wrote: Hi, I'm searching libimlayout package that is mentioned "How to extend Hildon Input Methods" document page. Where can I get it? The document is slightly wrong, what you actually want is the libimlayouts-generator package. If you used the installer script to setup the SDK you should be all set, otherwise you need to run the Nokia binaries installer, see http://repository.maemo.org/stable/3.1/INSTALL.txt Have same problem. There is no such package as libimlayouts-generator for bora (3.0 or 3.1) even with nokia binaries. However there is such package in 2.2 rootstrap. This is interesting since the tutorial http://www.maemo.org/platform/docs/howtos/howto_him_bora.html was added recently and is bora specific. I tried to install anything that seems to be input method related including: hildon-input-method_2.0.23-2_armel.deb libhildon-input-method-framework-sdk2_2.2.8-2_armel.deb libhildon-input-method-plugins-sdk-western_0.0.1-6_armel.deb libhildon-input-method-ui-sdk2_2.0.23-2_armel.deb libimengines3_3.0.8-1_armel.deb but still dont have gen_vkb in bora target. Any further tip where this tool for creating vkb layout may be? Can I use same tool from 2.2 for vkb targeted for N800? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: IT2007 Hacker Edition - First impression
Kees Jongenburger wrote: I was just disappointed that simple but nice sdl games don't work because of the sounds configuration.(the missing mp3 dsp thing). I This can be fixed by simple configuration change, see os2007on770 tracker https://garage.maemo.org/tracker/?atid=681&group_id=164&func=browse ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Installing NFS
Jeffrey Barish wrote: According to the directions in http://maemo.org/maemowiki/HowToNFS_06?highlight=%28NFS%29 I need to install a kernel with NFS support to enable NFS. This seems to be the right one as I have an N800: In fact you don't need another kernel. You just need nfs kernel modules. I think they are in bora repository so you can apt-get them on device [sbox-SDK_ARMEL: ~] > apt-cache search nfs rx-34-kernel-nfs-modules - NFS modules for rx-34 kernel nfs-common - NFS support files common to client and server portmap - The RPC portmapper Or you can compile your own kernel including those modules and copy them to device. When compiling kernel, relevant modules are here CC fs/lockd/lockd.mod.o LD [M] fs/lockd/lockd.ko CC fs/nfs/nfs.mod.o LD [M] fs/nfs/nfs.ko CC net/sunrpc/sunrpc.mod.o LD [M] net/sunrpc/sunrpc.ko ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Kernel for Maemo N800 and dual boot
Kalle Vahlman wrote: - tweak the config with 'make menuconfig HOSTCC=host-gcc' - build the image with 'make HOSTCC=host-gcc' I'm not sure if the HOSTCC is needed for 'make', but make menuconfig most likely needs it (to find ncurses). Tried the trick with host-gcc but it doesn't work for me in vmware maemo appliance upgraded to bora 3.1. Tried both in arm and x86 targets. I wonder what is broken with host-gcc here [sbox-SDK_X86: ~/kernel-source-rx-34-2.6.18] > host-gcc /scratchbox/compilers/bin/host-gcc: Too many open files [sbox-SDK_ARMEL: ~] > host-gcc /scratchbox/compilers/bin/host-gcc: Too many open files [sbox-SDK_ARMEL: ~] > ls -l /scratchbox/compilers/bin/host-gcc lrwxrwxrwx 1 root root 14 Jan 19 19:59 /scratchbox/compilers/bin/host-gcc -> sb_gcc_wrapper What works for me for 'make menuconfig' is commenting three lines in scripts/kconfig/lxdialog/check-lxdialog.sh to echo -lncurses always # $cc -print-file-name=libncurses.so | grep -q / # if [ $? -eq 0 ]; then echo '-lncurses' exit # fi This allows make menuconfig to run inside arm target. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Kernel for Maemo N800 and dual boot
Kalle Vahlman wrote: Is it possible to setup n800 to boot from a menu list like grub on something similar? Yes, see http://maemo.org/maemowiki/HowTo_EASILY_Boot_From_MMC_card One difference from desktop PC is that there is only one kernel (stored in one kernel partition /dev/mtd2, see /proc/mtd) To boot more kernels you either need to hack closed bootloader (not fun for most sane people) or be able to boot one kernel from another. Hopefully the latter can be done via kexec or armboot module in LAB (Linux As Bootloader) but both will probably need some work. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
wiki spam Re: OT: Re: No more 770 bug activity?
Neil MacLeod wrote: Off topic: "Interesting" links have been added to the end of this page (which is linked by the HowTo above): http://maemo.org/maemowiki/ModifyingRootImage Looks like the page has been hacked on 27 March. I've lost track of what's going on with Wiki, Midgard etc. so have no idea who or how to report this, other than mention it here. Yes, spam is there again. Apart from reporting it (but I guess admins alrady know it), it is easy to fix. 1. 'get info' link 2. diff button to find latest good version 3. view raw 4. copy to clipboard 5. 'edit' link 6. paste + save Good page to keep track on what's going on with wiki is http://maemo.org/maemowiki/RecentChanges ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: No more 770 bug activity?
Dave Neuer wrote: I am talking about the open source code they used in the product and their modifications to it which they are LEGALLY obligated to provide, just all gathered up in one repo. Umm, that's already available but it doesn't solve problems with closed stuff. And we won't get the rest in reasonable time if I understood Quim correctly. It'd only be old and dead to the extent that existing n770 owners who are also developers don't have any interest in maintaining it. I guess some/most those users which are also developers will check out OS2007 'hacker edition' and find this is the better one worth of interest and maintaining. I never had any interest in running Opera on the device, or any other proprietary component, so there is at least one. And I suspect I'm not the only one. This means you are already no help to many end users who *do* have interest in having closed components running. do we have all of the source for that gathered in one place? Yes, search the list for the links. It is either big tar.gz on maemo site or extracted source on other sites. Similar archive is both for OS2006 and 2007. Nokia has indicated that this is "unsupported" by them, so even if the community tried to support the open bits, it'd be less supported than an initially-incomplete, _all_ open source community edition based on what they are already legally obligated to provide! My understanding is that currently "unsupported" means that they don't want end-users to phone Nokia support with problems with OS2007. It also means they can stop updating the http://os2007on770.garage.maemo.org/ project anytime. Again, this 2006 release would not be unsupported, it would be community-supported. Still it would be different to current OS2006 to the point it will not help much to big part of current end-users. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: How to detect that connectivity is lost
Kalle Valo wrote: "Frantisek Dufka" <[EMAIL PROTECTED]> writes: What about the connection strength from ConIc StatisticsEvent [1]? Maybe he can use it after some experimentation to find the lowest acceptable level. Or maybe simple shell script pinging your default gateway in regular intervals could bring the connection down via dbus-send if no packet got through. This should be more failproof than guessing from signal strenght. Please do not do that, it would drain the battery in no time. For devices like 770 and N800 data transmission has to be kept in minimum in order to preserve energy. These kind of issues need to be fixed in lower levels, where it's much more energy efficient. What I suggested was a workaround not solution, that's true. By pinging in regular intervals I mean using ping to send let's say 5 or 10 packets (ping -c 10) and then sleep e.g. 15 seconds. I did not mean pinging default gateway continuously. I'm not sure you can solve this on lower levels completely without doing the same i.e. sending data to check they got through and back. If you don't do this it will be too late for some situations. When you actually send data that matter and find the connection is dead, you need to reconnect and retry, which is not ideal. So it is compromise between battery power and comfort (i.e. high chance of having connection ready when you really need it). Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: No more 770 bug activity?
Dave Neuer wrote: The current hacker edition looks like the best candidate to become a more continued solution. Some people here have got a deep look at it. What do you think? No, that's totally bogus: a binary-only distro that's supported by a community which doesn't have access to the source? Give me a break. Instead, how about Nokia get every bit of source used to build the last IT 2006 release which it has permission (both internal and external) to release in source form together in _one_ _repository_ and then let the community maintain that. That also looks like 'binary-only distro that's supported by a community which doesn't have access to the source' if you really understood what Quim said about opensourcing stuff. How it is better? The only difference is old/dead codebase (and more current end-users without any support). I guess more community members will help maintaining something not completely dead (i.e. os2007 for n770) then os2006, check http://www.fedoralegacy.org/ for example. The same push for opensourcing stuff can be targeted at os2007 codebase too and may have similar chances but better result. Additionally, keeping it compatible with N800 OS releases would be challenging to say the least (maybe Nokia employees could help w/ that little bit, like backporting fixes to bugs in the public source). That's where os2007 codebase would be better ;-) Anything else, from both a end-user and a non-Nokia developer perspective, IMO, is just crap. Yes, but as it is, end users have no supported choice anyway. Unsupported community maintained OS2006 or OS2007 is almost same to them. OS2007 has advantage of newer codebase with some useful features and bridging the gap i.e. more stuff intended for n800 running on their n770. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: metalayer-crawler - good idea?
Eero Tamminen wrote: Hi, ext Frantisek Dufka wrote: When rootfs is on mmc I can see frantic activity of mmcqd kernel deamon (doing writes?) for couple of minutes when booting or inserting the card (2 GB of mp3 files). Crawler doesn't write to the MMC, it only reads it (it writes to sqlite database in /home/user). I think part of the badness is due to libid3. You can see this with strace. It does when rootfs is on mmc. Together with scanning same card (but different partition) it is lot of I/O on same device. Luckily there are no heads in the card :-) This also means maybe the metalayer-crawler is not very healhy for internal flash wear too. Oh, yes we finally have strace for arm in bora 3.1, right? Will try. Ditto. I personally liked the 770 player more. Well, perhaps the library idea is a bit flawed for removable devices and does not scale well with bigger media? Or can it fly in limited device like this? How does ipod and other players solve this? Perhaps doing it in desktop software I guess. As for improvement, maybe you can scan just the filenames and do some hash (for card or whole directories) and if there is nothing new do not parse files inside at all? Will try strace before firing random ideas. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
metalayer-crawler - good idea?
Eero Tamminen wrote: > Search Maemo Bugzilla, there's some env variable which controls what > directories it searches. Maybe automatic media scanning is not such great idea after all? Do you plan to have this optional and perhaps have some explicit method of invoking it preferably even on specific directory? Most often I know what exactly changed on my card and would pick specific directory for refresh. I think lowering metalayer-crawler priority is not a solution to the problem. Still you get flushed most of useful data from RAM just because you insert card (mostly with no change) and it takes some time anyway so when inserting the card and trying to play something immediatelly, you must wait. Also it seems to do lot of diskwrites. When rootfs is on mmc I can see frantic activity of mmcqd kernel deamon (doing writes?) for couple of minutes when booting or inserting the card (2 GB of mp3 files). > Without crawler you wouldn't see anything in > the media player. > Yes, another bug :-) Would be nice to have this marvellous metadata idea optional. I keep my files structured and mostly I just want to play specific directory recursively (even with more levels). This simple (and maybe often used) use case seems to be not supported very well in current media player. The only way I found is to open one directory in filemanager and mark all files and select open. I will try to search bugzilla and add this opinion somewhere when it is up again but I guess this could be first discussed here too since maybe the whole idea need some thoughts? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: No more 770 bug activity?
Rainer Dorsch wrote: Is there any chance to have a community maintained release? If I remember correctly some drivers are missing to get there, Yoe can get clear picture of current state (i.e. what are those closed parts) from http://maemo.org/maemowiki/Os2007On770 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: No more 770 bug activity?
[EMAIL PROTECTED] wrote: Or in other words: what 770 users are *really* missing today and how this could be brought to the device. I'm really missing *stable* device. I know this is hard to achieve but the OS2007 hacker edition seems to fix at least one [1] annoying bug for me and feels more stable as a whole. It would be really nice if we could at least backport bugfixes in newer N800 firmwares to os2007 hacker edition and keep it living as long as possible. For this it would help if we had more detailed changelog for each release with the bugfix references. True that we could still examine listing [2], extract each source and see debian changelog and search for fixed bugs. This is what I tried when looking for fix for [3]. I blindly upgraded libSDL and osso-dsp-plugin-alsa from 3.1 bora release. Found that it does not solve the problem but luckily it didn't hurt. libSDL was good candidate since -14 version in 3.1 release enabled back esd for audio but it didn't work (even when trying to set SDL_AUDIODRIVER=esd). In future it would be nice to have some hints what packages are worth upgrading (= having bugfixes cross referenced with packages). This of course does not solve bugs in closed parts. It would still need someone to do same job like Markku did for first two OS2007 hacker releases. Hopefully current version is in good shape. It would also need some caution when developing future code to not hardcode things for n800 if not strictly needed and branch if this is needed. Is there some outcome from the device independance plan Ari mentioned? Is there some chance the OS2007 code could be structured in a way that makes maintaining n770 branch easier? As for existing binary packages, is there is a plan to break binary compatibility for n800's own good (like using armv6 or VFP code in some/all packages)? I hope it is not worth the price of making n770 incompatible :-) Frantisek 1. https://maemo.org/bugzilla/show_bug.cgi?id=743 2. http://repository.maemo.org/stable/3.1/content_comparison.html 3. https://garage.maemo.org/tracker/index.php?func=detail&aid=702&group_id=164&atid=681 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
hacker edition, Re: No more 770 bug activity?
Quim Gil wrote: There is the IT OS hacker edition, but it's not official and the official development in Nokia is currently focused in the maemo 3.x, IT OS 2007 and what is coming next. Hello Quim, any word about future of os2007on770? Would be nice to get answers to questions asked here http://maemo.org/pipermail/maemo-developers/2007-March/008813.html What is status of the project? Did you made some internal conclusions? Was it success or failure? How many downloads you got so far? Is Markku stil hired to continue on this? In my opinion this experiment was clear success from the functionality point of view i.e it is quite usable and IMO better that any official IT2006 release. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Modifying the Root Filesystem [NOKIA 770]
ludovic arnold wrote: i want save/modify my current root fs. When thinking about your goal again it is possible to skip this rsync/tar part completely and make jffs2 image from you modified filesystem directly on your device. The 'remount somhere else' trick is still needed to get rid of /proc /dev/ and /sys filesystems. But slightly better and safer way is to clone it to mmc and boot from it prior to some advanced modifications. Also when using live system directly you may include some temporary unneded files or even have bad luck and include some files partly written by running system (like gconf xml files). BTW, sumtool arm binary is now included in the initfs flasher archive. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Modifying the Root Filesystem [NOKIA 770]
ludovic arnold wrote: I think use rsync (cf /Frantisek Dufka/ <http://arcknowledge.com/cgi-bin/namazu.cgi?query=%2Bfrom%3Adufkaf%40seznam.cz&idxname=gmane.comp.handhelds.maemo.devel&sort=date%3Alate> ) : # rsync -e ssh -avHx --delete n770:/ rootfs/ While the basic idea is good there are two issues with this. 1. syncing / of live system cause reboot loop because of /dev/ mount point. It contains hidden /dev/entries needed early on boot before /dev is remounted. rsync simply skips it because of -x and leaves empty /dev which causes the loop. Solution is to remount rootfs to different place and synchronize it from there 2. using rsync seems to have problems see the mystery here https://maemo.org/bugzilla/show_bug.cgi?id=838 solution is to use tar which preserves filesystem layout including ordering of files (rsync sorts them and also creates temporary files which inflates directory size) The best is probably to read this http://maemo.org/maemowiki/HowTo_EASILY_Boot_From_MMC_card mkfs.jffs2 binary for arm is inside bootmenu initfs flasher, sumtool is not there because it is optional. It speeds up mounting but enlarges the image a bit so it is not very useful for initfs which is small and almost full. I'll add sumtool to the archive too just in case. It is useful when making flashable/recoverable backups of root filesystem directly on the device. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Using the external bugzilla
Tommi Komulainen wrote: On Wed, 2007-03-28 at 11:41 +0200, ext Sebastian Spaeth wrote: Daniel Stone wrote: You got it. The majority of the bug work happens before product release: going by what's in the changelogs, the external database has roughly 2% of the bugs as the internal one. That might well be because I (and others) have given up on using the external bug database as it seems next to useless. I guess it is still better than nothing. At least we have a list of known bugs for future reference. Please use it at least for reporting bugs in the open source components (https://maemo.org/bugzilla/describecomponents.cgi?product=haf) -- we are trying to use it. I hope you are also trying to use it (at least passively) for the rest too :-) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Opera draws fonts as blocks on specific pages when booting from mmc
Frantisek Dufka wrote: Could be something with filesystem layout (i.e. order in which the files are created in directories)? True that tar and mkfs.jffs2 create files is specific/same order but rsync makes it more random so the directory enumeration when not sorted is different? This old issue discussed here http://www.gossamer-threads.com/lists/maemo/developers/12107#12107 and also reported as https://maemo.org/bugzilla/show_bug.cgi?id=838 is still relevant on N800 with latest two firmwares. Now it looks like it really depends only on directory enumeration. Just creating ext3/ext2 filesystem with dir_index breaks it. Not using dir_index attribute works fine. Previously there was some doubt whether this is caused by corrupted filesystem or by not cloning the filesystem completely, now it is more clear. As it will probably just rot in bugzilla without anyone noticing it I'm posting it here too FYI. It is not very important issue but there are two conclusions 1. it is a bug 2. for workaround when cloning the filesystem use GNU tar which preserves on-disk order, avoid rsync or dir_index flag or anything else that may change ordering of files in directory Would be interesting to know which exact directory need to be preserved like this, probably the one with fonts. It should be possible to use tar once and then rsync the rest (even multiple times if you keep one root system as a backup and sync it regulary to the main one). Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: How to detect that connectivity is lost
Lauro wrote: On 3/28/07, Patrik Flykt <[EMAIL PROTECTED]> wrote: Hi, On Wed, 2007-03-28 at 00:39 +0200, ext Tomas wrote: > corresponding dbus signal) from the current IAP when WIFI signal is so low > that data transmission becomes impossible? What about the connection strength from ConIc StatisticsEvent [1]? Maybe he can use it after some experimentation to find the lowest acceptable level. Or maybe simple shell script pinging your default gateway in regular intervals could bring the connection down via dbus-send if no packet got through. This should be more failproof than guessing from signal strenght. I don't remember correct message but you can monitor dbus messages via dbus-monitor and bring down the connection by hand to see it. At least I hope there is such method call for closing connections :-) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: How to get application icons in task navigator
Alessandro Pasotti wrote: Is the wrapper script mandatory? Don't know. Never tried without it. I find setting variable inside executable to be not very elegant solution, but that's just me :-) Also maybe setting it in your code may be too late and has no effect since SDL reads this variable and sets window properties in its intialization. Make sure to set is before calling SDL_Init. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: How to get application icons in task navigator
Frantisek Dufka wrote: As for the shortcut file, make sure there are no extra spaces in the line with application name (just in case). I mean the 'StartupWMClass=app' line. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: How to get application icons in task navigator
Alessandro Pasotti wrote: I tried several times (with OS2005, 2006, 2007 and 2007 hackers edition) to get rid of this without success. This howto don't work: http://maemo.org/maemowiki/GameDevelopment#head-c91f345718121fbd009c639728f9de0104308789 It does work for me since IT2005 days and with all systems you listed. I use the wrapper script option since it does not need any change in SDL application source. There were some bugs related to this in first IT2006 beta and maybe even first IT2006 release (workaround in your application is possible, search this list) but it should be fixed since then. Post your shortcut file and wrapper script or source. As for the shortcut file, make sure there are no extra spaces in the line with application name (just in case). Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Support for frame buffer in N800
Sampath Goud wrote: Hi, I want to know if there is frame buffer support in N800. Yes. No support for console on framebuffer but generic framebuffer support shoud be there. Check /proc/fb. Maybe you are using wrong device? There are three on N800 (one on N770). Not sure why it is like this and why there is difference between N770 and N800 but try the one with higher number (2?). I have written a simple application (drawing a pixel) on frame buffer and tried to execute it on N800 in root mode. But it prompts the message "permission denied". It should work but there is one small problem, see below :-) Please let me know if there is support for frame buffer in N800. If there is support then how can I use it? Problem is that the videochip is external so you won't see any output until you either issue proper update ioctl to update rectangle after you write your pixels or set the update mode to automatic (which is waste of resources, default is manual). Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Launch maemo browser in fullscreen mode
Tomàs Jiménez Lozano wrote: There is really no way to maximize an application in general (and maemo browser in particular) emulating the HW Key press? Yes this brute force approach could work too. You could use uinput kernel driver (used with serial bluetooth keyboards) to feed proper F-key to the kernel input subsystem to emulate such key press. Could be quite easy but you need kernel module not present by default on the device. Maybe there is better way - using window manager to make the application full screen via something else than just keypress. Or write something that does this directly - set X window properties of browser window to be fullscreen. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Requesting addition to HowTo_EASILY_Boot_From_MMC_card wiki page
मयंक जैन (makuchaku) wrote: Since this page deals with modifying the initfs, the method to undo this should also be mentioned... (Thanks to on #maemo to help me out with this) 1) Unpack the flasher image ./flasher-3.0 -F blah.bin --unpack 2) Flash with the initfs image ./flasher-3.0 --initfs initfs.jffs -f -R 3) Reboot This will bring your N800 to the original initfs image. Yes, this is the most safe choice. Alternatively you can flash the backup jffs2 image created by the bootmenu initfs flasher before it modifies the initfs. And you can use the initfs_flash script to flash it directly from the device. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
wiki locked? Re: Requesting addition to HowTo_EASILY_Boot_From_MMC_card wiki page
मयंक जैन (makuchaku) wrote: > But I cannot find the "Edit page" link or something similar... > Oh, maybe someone changed wiki edit settings due to spam recently? It wasn't like this some time ago. Then you need to create user (i.e. the 'Login' link on left). I'm already logged into the Wiki :) Oh, maybe it is related to this? http://www.gossamer-threads.com/lists/maemo/developers/17683#17683 I can't edit pages now too. Last change was 2 days ago by Ferenc. Looks like we should now use test.maemo.org? Did I miss any announcement? This page is here http://test.maemo.org/support/wiki/howto-easily-boot-from-mmc-card/ However it looks like I cannot login with my garage account, time to ask Ferenc? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Requesting addition to HowTo_EASILY_Boot_From_MMC_card wiki page
मयंक जैन (makuchaku) wrote: Hi, I was playing around with the dual boot options & it works perfectly. I then gave it a shot with ext3 partition, instead of ext2 as mentioned in the page. Initially, I wasnt able to mount the ext3 partition but was able to do so after insmod'ing jbd.ko and then mbcache.ko Yes, there are example bootmenu configurations with proper modules for ext3 in initfs flasher archive. There is also README mentioning this. I'm using ext3 for few months and did not see any problems. It is handy when device crashes and reboots. See also http://www.internettablettalk.com/forums/showthread.php?p=35742#post35742 So can someone (with editing rights) please add this information to http://maemo.org/maemowiki/HowTo_EASILY_Boot_From_MMC_card page. PS: Who can edit the Maemo wiki page? Anyone or someone with specific rights? Anyone including you :-) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
