Re: [maemo-developers] non-maemo apps in toolbar
Hi, On Tue, Jan 10, 2006 at 11:00:09PM -0200, Gustavo Sverzut Barbieri wrote: > > Battery is affected more how often CPU is used than the "height" > > of CPU usage spike. As input method comes & resizes application > > window only on user input, it's not significant from the battery > > usage point of view. > > I'm not taking battery in account, just the perceived slowness to > resize/re-render the whole screen. I still don't have the device, but > from what I've read, it takes some time to open the vkb for the first > time due Opera's slow -rendering... or I misunderstood? Further resizes of browser window are not slow (nor any of the resizes on any other applications), so the slowness has to be something else that Browser does when its window size decreases significantly for the first time. (Btw. I've also noticed that the first time you launch browser after bootup, freezes the desktop for several seconds. This doesn't happen with any other application.) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] dpkg blues
Hi, I am trying to build arm debian package of libsigc++ installable on nokia 770. dpkg-buildpackage builds it just fine: % dpkg-buildpackage -rfakeroot -uc -us -sa -D % ls libsigc++-2.0-0c2a_2.0.16-2_arm.deb However, in order for me to use AppInstaller, I have to make it dependable on pseudo-package maemo: "... instead, it uses a database of its own that only contains the installed application packages and a fake maemo package that represents the rest of the system. This means that your package can not usefully depend on libgtk2.0-0, say. You should only depend on other application packages that are installed with the Application Installer. You should also depend on the fake maemo package to ensure that your package is only installable by the Application Installer." So, I made it dependable on maemo: debian/control: - Source: libsigc++-2.0 Section: devel Priority: optional Maintainer: Daniel Burrows <[EMAIL PROTECTED]> Standards-Version: 3.6.2.0 Build-Depends: debhelper (>=4.0.0), m4, g++ (>= 3:3.2.0) Package: libsigc++-2.0-0c2a Section: libs Depends: maemo Architecture: any Description: type-safe Signal Framework for C++ - runtime This library implements a full callback system for use in widget libraries, abstract interfaces, and general programming. It provides the ability to connect an abstract callback to a class method, function, or function object, and contains adaptor classes for connection of dissimilar callbacks. . These are the runtime files for libsigc++, needed only if you wish to run software which depends on it. - However, installing it both on 770 and in scratchbox SDK_ARM fails bitterly: % fakeroot # app-installer-tool install libsigc++-2.0-0c2a_2.0.16-2_arm.deb Selecting previously deselected package libsigc++-2.0-0c2a. (Reading database ... 27 files and directories currently installed.) Preparing to replace libsigc++-2.0-0c2a 2.0.16-2 (using libsigc++-2.0-0c2a_2.0.16-2_arm.deb) ... Unpacking replacement libsigc++-2.0-0c2a ... dpkg (subprocess): failed to chroot to `/var/lib/install': Operation not permitted dpkg: warning - old post-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg (subprocess): failed to chroot to `/var/lib/install': Operation not permitted dpkg: error processing libsigc++-2.0-0c2a_2.0.16-2_arm.deb (--install): subprocess new post-removal script returned error exit status 2 dpkg (subprocess): failed to chroot to `/var/lib/install': Operation not permitted dpkg: error while cleaning up: subprocess post-removal script returned error exit status 2 Errors were encountered while processing: libsigc++-2.0-0c2a_2.0.16-2_arm.deb failed Installation of libsigc++-2.0-0c2a_2.0.16-2_arm.deb failed, removing package libsigc++-2.0-0c2a. dpkg: error processing libsigc++-2.0-0c2a (--purge): Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. Errors were encountered while processing: libsigc++-2.0-0c2a Removing failed! --- Can someone explain to me why I get this error? failed to chroot to `/var/lib/install' thanks in advance, -Vlad -- _ Vladislav Grinchenko http://home.comcast.net/~3rdshift/ e-mail: [EMAIL PROTECTED] Focus on quality, and productivity will follow. _ ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] non-maemo apps in toolbar
On 1/10/06, Eero Tamminen <[EMAIL PROTECTED]> wrote: > On Mon, Jan 09, 2006 at 09:37:25AM -0200, Gustavo Sverzut Barbieri wrote: > > > > To make an input window work in maemo env ( this is different to > > > > defualt mb input win handling ) you need to have it set its transiency > > > > to the window its entering data for. > > > > > > I think this would be undesirable as then the application window > > > would be resized. This discussion was mostly about stuff like > > > SDL games which don't handle window resizes. Therefore the > > > input method should be above the "application" window, not > > > make it to resize. > > > > seconded. > > > > Also, if I am right, this could avoid CPU usage in complex programs > > like web browser. > > Battery is affected more how often CPU is used than the "height" > of CPU usage spike. As input method comes & resizes application > window only on user input, it's not significant from the battery > usage point of view. I'm not taking battery in account, just the perceived slowness to resize/re-render the whole screen. I still don't have the device, but from what I've read, it takes some time to open the vkb for the first time due Opera's slow -rendering... or I misunderstood? -- Gustavo Sverzut Barbieri -- Computer Engineer 2001 - UNICAMP Mobile: +55 (19) 9165 8010 Phone: +1 (347) 624 6296; [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] ICQ#: 17249123 MSN: [EMAIL PROTECTED] GPG: 0xB640E1A2 @ wwwkeys.pgp.net ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Wavemon or other monitoring application forWLAN
Thanks everyone for the info. Extra information about EAP-TTLS or VPN: - EAP-TTLS is used by larger organizations like Universities to support cross-domain authentication: the user is authenticated via RADIUS based on his username ([EMAIL PROTECTED]), where the RADIUS server queries the RADIUS server of the appropriate domain if it is trusted. This works very good and will become (or is ?) the standard for wireless student roaming across Europe. See http://aaa.surfnet.nl/info/eduroam/wlan.jsp or google eduroam. - WEP is not that insecure if you enable temporary keys with RADIUS, which expire within 10 minutes. Plus you can enable TKIP or just use WPA on modern Access Points. I will use the /etc/udhcpcd/udhcpcd.script should be enough for now. Thanks. Greetings, Dirk. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Missing control panel
On 1/10/06, Matti Reijonen <[EMAIL PROTECTED]> wrote: > > Hello, > > I installed Maemo 1.1RC5 a while ago, then I noticed the odd application names > control panel and application installer names were copa_ap_cp_name and > ai_ap_applicatio... > found the sollution into that from these mailing lists and run unset LC_ALL > Now the names are fine, except that the whole control panel is missing and > with > that the application installer too.. > I can only see the X-Terminal in applications list. > > So what's wrong here? The menu items are loaded from .desktop files in /etc/others-menu/ The .desktop file for control panel is 1200_Control Panel.desktop, maybe it's gone missing or damaged. -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Open URL with 770's browser
On Mon, 2006-01-09 at 19:01 -0500, Roland Krikava wrote: > Can anyone suggest a way to open a URL using the native browser on the > 770? I noticed that someone posted earlier about attempting to use > dbus to accomplish this.. I just hacked up a shell script to make this work for viewing images and URLs from pine (http://david.woodhou.se/maemo-pine.html) ... #!/bin/sh if ! dbus-send --system --type=method_call --dest="com.nokia.osso_browser" --print-reply /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"$1" ; then DISPLAY=:0 run-standalone.sh /usr/bin/browser &>/dev/null & sleep 5 dbus-send --system --type=method_call --dest="com.nokia.osso_browser" --print-reply /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"$1" fi # give it a while to access local files before they're deleted if echo "$1" | grep ^/ ; then sleep 10 fi (Btw, please could we have the Subject line mangling on this mailing list removed or at _least_ reduced to a sane number of characters. Removing it completely would be best -- there are much better ways to filter mail, and people who really want it there can always _add_ it for themselves; adding it locally is much easier than trying to remove it again once it's been added). -- dwmw2 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brad Midgley schrieb: > Razvan >>[4.046356] Bluetooth: SCO (Voice Link) ver 0.4 >>[4.051147] Bluetooth: SCO socket layer initialized > this will be printed both for adapters with and without sco support. The > driver does not detect and disable the interface on unsupported > hardware. (Although it should--we get questions all the time about > everything working right up to the point that they get silence on the > connection instead of audio) Umm... to be more precise this is just the output from the SCO kernel driver not from the HCI driver. So the Bluetooth stack, according to this message, now supports handling of SCO traffic (kernel modules sco.ko). But this does not mean that the HCI driver for the specific Bluetooth module in use can handle it (kernel modules hci_* and friends). Those are two distinct things... > Brad Cheers nils faerber - -- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen Mob: +49-176-21024535 - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDw+nrJXeIURG1qHgRAvEOAJ92LOph0Rm6YjwPtgROcFCC6SW9GwCgvKeK mKcAe1fz3cWaWYiNw46IvnA= =gEpd -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
Johannes >>The two types of bluetooth audio are very different. You linked to a >>discussion about the other type. > And the answer to that in > http://article.gmane.org/gmane.linux.bluez.devel/6748 by Ville Tervo > from Nokia: > > "I'll try to arrange something." Ok. I see it. It does sound encouraging (either Nokia will do it themselves or they will also involve Marcel). BTW, Marcel is brilliant with this stuff. They'd be doing themselves a real favor to get him on board. [a2dp] > So that is used for bluetooth stereo earphones to listen to e.g. CD > music? yes. That's what I've been tinkering with mostly. I like the gstreamer architecture... I want to put our audio encoder that runs on the cpu in a gstreamer plugin and Nokia could snap in a replacement that runs on the dsp. Brad ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
Razvan > [4.046356] Bluetooth: SCO (Voice Link) ver 0.4 > [4.051147] Bluetooth: SCO socket layer initialized this will be printed both for adapters with and without sco support. The driver does not detect and disable the interface on unsupported hardware. (Although it should--we get questions all the time about everything working right up to the point that they get silence on the connection instead of audio) Brad ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
On Tue, 2006-01-10 at 15:24 +0100, Timo Steuerwald wrote: > Razvan Dragomirescu wrote: > > >BTW, did anyone notice the following lines in the "dmesg" output on > >the 770 in the 51-13 firmware? No I didn't - thx. > >[4.037261] Bluetooth: L2CAP ver 2.7 > >[4.041015] Bluetooth: L2CAP socket layer initialized > >[4.046356] Bluetooth: SCO (Voice Link) ver 0.4 > >[4.051147] Bluetooth: SCO socket layer initialized > >[4.056365] Bluetooth: RFCOMM ver 1.5 > >[4.060272] Bluetooth: RFCOMM socket layer initialized > >[4.065704] Bluetooth: RFCOMM TTY layer initialized > >[4.070861] Bluetooth: BNEP (Ethernet Emulation) ver 1.2 > >[4.076477] Bluetooth: HIDP (Human Interface Emulation) ver 1.1 > > > >It mentions SCO. I'm not sure if that means anything or if this was > >present in the older versions of the firmware, I just thought it was > >interesting. I think that's only what is already included in bluez. What is missing is the driver that is realising this functionality on the bluetooth chip. SCO is part of the top interface of bluez, the driver is in bluezs bottom. Is that correct Brad? > >Anyway, I sort of get the feeling that Nokia is keeping so quiet about > >this mostly because this is something they want to release in the 2006 > >firmware and they most probably don't want anyone "stealing their > >thunder" and releasing a fully-working VoIP package for the 770 before > >that. With Asterisk and chan_bluetooth ported to the device, the 770 > >could become the ultimate VoIP phone. > > full ACK! I hope you are wrong and Nokia has a real interest in making the maemo platform more open (or isn't driver development part of that open platform?) > >Any clues yet from Nokia? :). > > I suppose: no! :-( Stop this anticipatory obedience. It's counterproductive ;-). Greets, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
On Mon, 2006-01-09 at 20:04 -0700, Brad Midgley wrote: > Johannes > > The two types of bluetooth audio are very different. You linked to a > discussion about the other type. Sorry, I didn't made that clear enough. I was refering to the following said in http://article.gmane.org/gmane.linux.bluez.devel/6729 by Marcel Holtmann: "The Nokia 770 is using a TI chip and basically nobody of us has real experiences with these chips. I have seen them in an iPAQ and now the 770, but that's it. Do you think Nokia is willing to donate some of the TI development kits to BlueZ? Especially the SCO and eSCO stuff needs a lot of testing and I would prefer to do it with an i386 or x86_86 based system." And the answer to that in http://article.gmane.org/gmane.linux.bluez.devel/6748 by Ville Tervo from Nokia: "I'll try to arrange something." > low-latency voice-quality mono audio uses a special transport (SCO) and > is delivered from the bluetooth chip either over the regular data > connection to the cpu (HCI) or it is connected to dedicated audio/analog > hardware (PCM). The HCI formatting and negotiation differs from chip to > chip and the linux driver is only complete for CSR chipsets. Thanks for the explanation - SCO is exectly what I need then. > a2dp specifies one-way high-quality, traditionally stereo, audio. It is > delivered over an L2CAP socket so linux can send and receive this audio > with any bluetooth chip that has even the most basic support. So that is used for bluetooth stereo earphones to listen to e.g. CD music? > We know what has to be done for a2dp. The SCO stuff is what I would like > to see help from Nokia on. I would hope they can help us with the HCI > interaction with the SCO transport since that gives us the most generic > control over the audio stream. Thanks for that details! Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Missing control panel
Hello, I installed Maemo 1.1RC5 a while ago, then I noticed the odd application names control panel and application installer names were copa_ap_cp_name and ai_ap_applicatio... found the sollution into that from these mailing lists and run unset LC_ALL Now the names are fine, except that the whole control panel is missing and with that the application installer too.. I can only see the X-Terminal in applications list. So what's wrong here? Thanks for any answers.. - Matti ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
Razvan Dragomirescu wrote: BTW, did anyone notice the following lines in the "dmesg" output on the 770 in the 51-13 firmware? [4.037261] Bluetooth: L2CAP ver 2.7 [4.041015] Bluetooth: L2CAP socket layer initialized [4.046356] Bluetooth: SCO (Voice Link) ver 0.4 [4.051147] Bluetooth: SCO socket layer initialized [4.056365] Bluetooth: RFCOMM ver 1.5 [4.060272] Bluetooth: RFCOMM socket layer initialized [4.065704] Bluetooth: RFCOMM TTY layer initialized [4.070861] Bluetooth: BNEP (Ethernet Emulation) ver 1.2 [4.076477] Bluetooth: HIDP (Human Interface Emulation) ver 1.1 It mentions SCO. I'm not sure if that means anything or if this was present in the older versions of the firmware, I just thought it was interesting. Also, a few lines above the Bluetooth stuff, you can find: [3.814697] Advanced Linux Sound Architecture Driver Version 1.0.9rc2 (Thu Mar 24 10:33:39 2005 UTC). [3.828033] usbcore: registered new driver snd-usb-audio [3.833709] ALSA device list: [3.836822] #0: Dummy 1 USB Audio? Hmmh, interesting... may be anyone out there who has a usb headset can check if it is possible to use it. BTW: The same output already appears on .45-8 Anyway, I sort of get the feeling that Nokia is keeping so quiet about this mostly because this is something they want to release in the 2006 firmware and they most probably don't want anyone "stealing their thunder" and releasing a fully-working VoIP package for the 770 before that. With Asterisk and chan_bluetooth ported to the device, the 770 could become the ultimate VoIP phone. full ACK! Any clues yet from Nokia? :). I suppose: no! :-( Cheers, Timo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
BTW, did anyone notice the following lines in the "dmesg" output on the 770 in the 51-13 firmware? [4.037261] Bluetooth: L2CAP ver 2.7 [4.041015] Bluetooth: L2CAP socket layer initialized [4.046356] Bluetooth: SCO (Voice Link) ver 0.4 [4.051147] Bluetooth: SCO socket layer initialized [4.056365] Bluetooth: RFCOMM ver 1.5 [4.060272] Bluetooth: RFCOMM socket layer initialized [4.065704] Bluetooth: RFCOMM TTY layer initialized [4.070861] Bluetooth: BNEP (Ethernet Emulation) ver 1.2 [4.076477] Bluetooth: HIDP (Human Interface Emulation) ver 1.1 It mentions SCO. I'm not sure if that means anything or if this was present in the older versions of the firmware, I just thought it was interesting. Also, a few lines above the Bluetooth stuff, you can find: [3.814697] Advanced Linux Sound Architecture Driver Version 1.0.9rc2 (Thu Mar 24 10:33:39 2005 UTC). [3.828033] usbcore: registered new driver snd-usb-audio [3.833709] ALSA device list: [3.836822] #0: Dummy 1 USB Audio? Anyway, I sort of get the feeling that Nokia is keeping so quiet about this mostly because this is something they want to release in the 2006 firmware and they most probably don't want anyone "stealing their thunder" and releasing a fully-working VoIP package for the 770 before that. With Asterisk and chan_bluetooth ported to the device, the 770 could become the ultimate VoIP phone. Any clues yet from Nokia? :). Razvan -- Razvan Dragomirescu Chief Technology Officer Cayenne Graphics SRL On 1/10/06, Johannes Eickhold <[EMAIL PROTECTED]> wrote: > On Tue, 2005-12-20 at 10:16 -0700, Brad Midgley wrote: > > I'm overseeing the bluetooth audio on linux project... > > > > Linux only supports SCO transfers for CSR chips. To use the current > > btsco stuff, Nokia is going to have to contribute a SCO driver to the > > kernel for whatever bluetooth chip they put in the 770. > > I found some further info at: > http://thread.gmane.org/gmane.linux.bluez.devel/6713 > > Can anyone of the Nokia developers give us some more hints on the head > set topic please? Can we only expect that to work when the 2006 software > edition will be released or will the head set support be included in an > earlier firmware update? > > This missing feature is very much appreciated! > > Greets, Jonek. > > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] New wiki page (IMprovementIdeasForOssoMail)
New wiki page. Don't take what I've already mentioned on the wiki page personal. As a software developer myself I know how things in a software development project go. http://maemo.org/maemowiki/ImprovementIdeasForOssoEmail And of course, feel free to improve the wiki page. -- Philip Van Hoof, software developer at x-tend home: me at pvanhoof dot be gnome: pvanhoof at gnome dot org work: vanhoof at x-tend dot be http://www.pvanhoof.be - http://www.x-tend.be ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Wavemon or other monitoring application for WLAN
I've started with a little application which listenes on dbus for certain messages and should then be able to execute a defined script. BUT is stopped it again. A more simpler solution is to get root and edit the /etc/udhcpcd/udhcpcd.script. In there you will find a line that is something like /usr/bin/dbus-send --system blabla string:DHCP string:CONNECTED Before this line I added my script which does some post connection checking. Like logging into university network and/or starting vpn services. Hope this helps you out. Regards Matthias On Tuesday 10 January 2006 02:57, Johannes Eickhold wrote: > On Mon, 2006-01-09 at 15:22 +0100, Dirk Kuijsten wrote: > > I wanted to make an application that can connect to a hotspot and test > > the connection and/or do an automatic weblogin (my hotspot provider here > > in the Netherlands doesn't support EAP). Or start scripts to test the > > connection. > > If I understand you correctly you want some actions executed > automatically if you choose a connection from within the connection > manager? That has been discussed on #maemo. I think the solution is to > listen for the dbus messages that are generated upon establishment of a > WLAN connection and use them to trigger scripts that do further work > after a connection is established. > > Personally I don't like this kind of solution very much, because this > had to be done by some kind of daemon listening on the dbus all the > time. > > *think out loud* something like the options in > debians /etc/network/interfaces stanzas should be used. Like "post-up > [command]". But there are no config files there on the 770 for interface > configuration. Events (dbus messages) are way cooler (modern), but are > they the easiest way to go for such things? > > > The problem is: is there a way to interface with the connection manager? > > That is definately needed. One should be able to hook post-up scripts > for the APs connection settings that are already saved on the 770! > Everybody knows that WEP and WAP are insecure. To overcome that, many > institutions use differnt kinds of VPN connections that should be > integrated in the connection manager through script hooks. > > > According to the Maemo package reference the packages osso-wlan and > > osso-wlan-security (EAP deamon) are from Nokia. But my question is: will > > the sources be available? > > http://repository.maemo.org/unstable/1.1rc5/package_reference.html > > Good question. > > > I would also like it if the EAP daemon supported EAP-TTLS, which it > > doesn't yet. My university only supports ttls or cisco-vpn. > > My university uses cisco-vpn too and therefor I use VPNC on the 770 > which works fine except that I would like to have it executed > automatically when I connect to one of my universities APs. > > http://maemo.org/maemowiki/InstallVPNC > > > 2. > > > > Thus I looked at the current modules loaded: cx3110x (lsmod). > > They are in /mnt/initfs/lib/modules/2.6.12.3-omap1/ > > It seems the license for the cx3110x module is GPL version 2 (do a > > strings on it). Thus Nokia should provide the source of the module. > > With it we could write the osso-wlan package ourselves. > > > > Note: I know this is a Conexant cx3110x wlan chip with a lower mac > > (umac), which is probably in the wlan-firmware package. I don't need > > those sources. The strings of this module also do give "Proprietary" as > > it should. > > Is the firmware integrated into that kernel module or does the module > load it onto the hardware from a different file? > > Greets, Jonek. > > PS: Wavemon would be nice to have. Timo: it depends on ncurses! > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Info on FIASCO components/hackers' guide to the N770
ext Dave Neuer wrote: >Hi all, and thank you Nokia for finally getting my lovely new 770 to me. > >I'm still in the process of familiarizing myself w/ the device and the >Maemo/N770 environment. Let me first complement all of the people who >have made this impressive little device so usable and compelling >already. Great job. > >One of the first things I generally do when I get a new Linux-capable >device is remove all proprietary software, and replace it with Free >Software or Open Source alternatives if possible (or otherwise do >without). > >I'm still running the stock image on the 770, but I've been >investigating over the last week what it would take to rip out all of >the proprietary stuff, and how much customization of the device is >possible. > > > developer rootfs is the place to start, as it contains no propreitary applications. It do require a binary blob under nokia license, containing device specific and closed software from nokia. >One thing I've noticed is there seems to be lack of a comprehensive >set of documentation for the device at the "how it all works" level, >from "processor beings executing code at location 0x" to "this >is how you assemble a FIASCO image." > > > flasher is capable of flashing independently the kernel, initfs, rootfs. So its not necessary to have a FIASCO file. >I can kind of understand why this information might not be available. >Nokia no doubt wants us to concentrate on developing useful end-user >applications which enhance rather than replace the existing >functionality and environment. > >However, given the existence of the information at [1] and [2], it >seems that the djinn is already half out of the bottle. For instance, >I've already been able, using the resources cited above on the >maemo.org website, to unpack a FIASCO image and determine that the >initfs and rootfs are JFFS2 images, and that the remaining components >aren't. So, I was wondering if it would be possible to have such a >"Hacker's Guide to the N770 and Maemo." Something which describes the >function of the various FIASCO components and the recipe for creating >a valid custom FIASCO image (obviously certain components couldn't be >replaced). > >I'm most interested in creating my own kernel, initfs and rootfs >images and sewing them back together, and flashing them to the device >without breaking anything. > > > with resources available on maemo.org, you should be able to compile your own kernel and rootfs. There are issues with initfs [so that piece is not possible, as it contains some software like wlan drivers etc, which are closed] look at http://maemo.org/platform/docs/howtos/howto_use_flasher_rootfs.html Br, Devesh >I'd love to know what Nokia's position is on this as well as what >other developers here think about it. > >Also, is flasher a supported way to upgrade to the latest system image >from Nokia's support site? > >Thanks in advance. > >Dave > >[1] http://maemo.org/maemowiki/HowDoiBecomeRoot (section entitled "The Hard >Way" >[2] http://maemo.org/maemowiki/Flasher_tool_usage >___ >maemo-developers mailing list >maemo-developers@maemo.org >https://maemo.org/mailman/listinfo/maemo-developers > > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Wavemon or other monitoring application for WLAN
Johannes Eickhold wrote: PS: Wavemon would be nice to have. Timo: it depends on ncurses! This is already installed on the device. Cheers, Timo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Wavemon or other monitoring application for WLAN
On Tue, 10 Jan 2006, ext Johannes Eickhold wrote: > > The problem is: is there a way to interface with the connection manager? > > That is definately needed. One should be able to hook post-up scripts > for the APs connection settings that are already saved on the 770! > Everybody knows that WEP and WAP are insecure. To overcome that, many > institutions use differnt kinds of VPN connections that should be > integrated in the connection manager through script hooks. WEP is known to be really insecure, but WPA and WPA2 are much stronger. > Is the firmware integrated into that kernel module or does the module > load it onto the hardware from a different file? The module loads the firmware from /usr/lib/hotplug/firmware/3825.arm to the chip. The firmware runs on the target (the CX3110x chipset) while the UMAC runs on the host (OMAP). The UMAC is actually loaded when umac.ko is insmoded. > PS: Wavemon would be nice to have. Timo: it depends on ncurses! I agree, but wavemon also needs WLAN monitor mode support and this is now included in 51-13. I only tested it with tcpdump, and it seems to reports the correct 802.11 frames. Cheers, Samuel. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Maemo Alarm/Notifier Interface
I am currently looking for what developer requirements would be from such an Alarm/Notifier interface. Specially lot of developers working on applications which need to schedule events and notifications like PIM aplications need this functionality, and it is just not there yet in the Maemo Development Platform. Some starters 1. API to - enable notifier/alarm events - cancel previously scheduled events - ability to specify sound file to be played for events [I guess this can be done by the application handling the notifier event, so maybe not relevant] 2. Alarm/Notifier sub system features - ability to schedule multiple notifier alarm event - ability to wake up device on events Devesh ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
Ralph > Is there a bandwidth problem, or just people being silly with the > design? There is a bandwidth problem. High-quality audio is compressed on the fly before transmission. We will probably be able to build in the delay to the video player so it slips the video stream a bit. gstreamer may even have a way to specify in the codec plugin how much latency it introduces. Some of these problems could be fixed if a new audio spec was written that required the extended data rate of bluetooth 2.0 and left out compression. The a2dp spec says nothing about duplex high-quality audio, but there's no reason a headset couldn't try to connect back to the source node on an independent connection when it starts receiving audio. That's basically how the AVRCP connection works. Brad ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
