[maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
Hi Pals, Nokia, I would be intersted in leading the development of a LGPL/BSD licensed porting layer of the Qtopia platform for the maemo platform. Why such a layer is good: -Existing applications can be utilized for Maemo by easily migrating them to use osso/hildon technology -More applications will make hildon/osso more attractive -Give developers the choiche to target any platform easily -Maemo is a great piece of Free Software and should be supported How such a port would look like: -We would use Qt2/X11 and make it look like the maemo gui -We would implement libqpe,libqtopia, libqtopia1, libqtopiapim using osso, hildon and Qt2 -In the future we should use Qt4 but that would require more porting of the applications. What we need: -Legal counseling if we can do a clean room implementations and how it should look like. -Sponsors: -People Donating Time to this project -People/Companies Donating Money to this project allowing people to work on it during office hours (not for myself though) -People writing tests and setting up a QA infrastructure -People Testing our Work -People porting/verifying application work -People enjoying using maemo How should we proceed: -We should gather enough people to start this project -We should have enough information to start the clean room implementation. -We should quantify which classes are mostly needed to port most of the apps. if you are interested please email me regards holger ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
ext Holger Freyther wrote: Hi Pals, Nokia, As only my personal viewbased on my prtsonal project I would be intersted in leading the development of a LGPL/BSD licensed porting layer of the Qtopia platform for the maemo platform. Why such a layer is good: -Existing applications can be utilized for Maemo by easily migrating them to use osso/hildon technology -More applications will make hildon/osso more attractive -Give developers the choiche to target any platform easily -Maemo is a great piece of Free Software and should be supported How such a port would look like: -We would use Qt2/X11 and make it look like the maemo gui -We would implement libqpe,libqtopia, libqtopia1, libqtopiapim using osso, hildon and Qt2 -In the future we should use Qt4 but that would require more porting of the applications. I did a minimum porting layer to get qtopia application ( cumulus / www.kflog.org ) to running. I did it based on qt3.3. I get it so far that i get application running in real 770. The most important things missing was support for maemo desktop and input methods. I also did't even try to make it yet as a stand alone layer. I even did not try any clean room but just use modifies qutopia libraries and so resulting stuff will still be GPL (least i think, i am not sppecialist in legal stuff ) Kate What we need: -Legal counseling if we can do a clean room implementations and how it should look like. -Sponsors: -People Donating Time to this project -People/Companies Donating Money to this project allowing people to work on it during office hours (not for myself though) -People writing tests and setting up a QA infrastructure -People Testing our Work -People porting/verifying application work -People enjoying using maemo How should we proceed: -We should gather enough people to start this project -We should have enough information to start the clean room implementation. -We should quantify which classes are mostly needed to port most of the apps. if you are interested please email me regards holger ___ 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] The future of the Application installer
On Monday 07 November 2005 18:35, Marius Vollmer wrote: ext Koen Kooi [EMAIL PROTECTED] writes: I like the idea of extra software being in /var/lib/install so it can't mess up the rootfs is something goes wrongs. Hmm. That is something I have been thinking about, but it would require changes to the way dpkg etc work, no? Isn't that the entire point of free software? :) The cleanest way to get this would probably be to add an option to dpkg that would make it perform the unpacking and configuring of packages as a specified user (instead of as root). I think I would still have it update the package database as root since anything else seems to require too big changes. In an ideal world, most applications would be installed with minimal privileges, but there is a possibility of installing applications requiring more privileges (like vpn applications or device drivers for add-on hardware). Also, I find it quite important that software compilation process does not need to be changed much. Currently you have to configure with --prefix=/var/lib/install and then in debian/rules move the files back around to /. One way of making this possible would be installing normal apps to /var/lib/install, privileged apps in /var/lib/install-trusted, and make an unionfs[1] of these and /. Probably to somewhere else than /, so that stock applications don't get broken if applications install for example a broken gtk. So in the end we would have in fstab something like: none /union/lib dirs=/lib=ro, /var/lib/install-trusted/lib=ro,/var/lib/install/lib=rw none /union/usr dirs=/usr=ro, /var/lib/install-trusted/usr=ro,/var/lib/install/usr=rw ... and all user application are run as chroot /union userapp, where chrooting is automatically done by tasknavigator. unionfs with one leaf being user-writable however has some security implications, so the whole thing needs carefull review. However, the possibility of having the cake (of safe app installation) and eating it (of almost unmodified debs) it seems worth it. Cheers, Riku [1] http://www.fsl.cs.sunysb.edu/project-unionfs.html ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
Hi, I would be intersted in leading the development of a LGPL/BSD licensed porting layer of the Qtopia platform for the maemo platform. Sounds intresting. Do you mean something like this: http://cvs.sourceforge.net/viewcvs.py/gtk-webcore/NRCore/kwiq/KWQButton.cpp?rev=1.1.1.1view=auto It seems that gtk-webcore implements partial QT - GTK+ adaption layer. Br, Sampo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
On 11/7/05, Holger Freyther [EMAIL PROTECTED] wrote: Hi Pals, Nokia, Hi Holger, I'm interested in have Qt/Qtopia/Opie to run on Nokia-770, however I have some points: - If you will spend resources, do it first to port Opie to Qt4, everyone will enjoy it and it will make things faster easier. Porting current code base is a loosing time :-(. Right now, Qtopia doesn't work well with X11 display, wich is bad. Qt4 seems to address this better. - If you want a Qt based GUI, it'll not be maemo's GUI and trying to run the Maemo-WM will just take resources. So you'll probably remove maemo-gui, leaving just maemo core... which is basically linux, so in the end you have something which is _NOT_ maemo compatible anymore. You'll have to use other input method, etc. I like options and I like Qt programming more than Gtk, and think that Qt has more embedded code base and mature software, that's why I'm interested in this port, however it's splitting resources, which are low right now :-( -- Gustavo Sverzut Barbieri -- Computer Engineer 2001 - UNICAMP Mobile: +55 (19) 9165 8010 Phone: +1 (347) 624 6296 @ sip.stanaphone.com 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
[maemo-developers] Playback of MPEG2?
Hi, on the Nokia webpage I saw the hint that the N770 can playback MPEG4, Real Video, H.263, ... (see IceAge trailer) But do we have a change to playback MPEG2 video files? (e.g. DVB-S recordings or DVDs) Is the HW fast enough (with accelerator if any)? If yes: then the 770 is the ideal device to stream DVB recordings (see e.g. VDR), isn't it? Best Regards Olli ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
...which makes these sound a bit funky. If you use *anything* GUI-related that is already implemented, you'll drag Gtk+ in. Which will mean that you need to have both Qt and Gtk+ libraries in memory at the same time, which I think is not too hot on the current hardware. From this point of view I think GTK2 was the completly wrong choice as Maemo's GUI toolkit. Its slow (mameo contains even a hacked version which tries to speed it up a bit) and heavyweight (megs of code splitted in many different shared-libs), but it was choosen for compatibility as the whole Xserver based approach. (fox-toolkit or fltk are much more efficient) I think with this decision in mind a port of QT would not be that bad either since it would allow running apps on your Maemo powered device which would not be able to run otherwise or would not look that good. lg Clemens ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
Hi Holger, If you are going to base this on Qt2 how could it be LGPL/BSD licensed? If you are do to a LGPL/BSD licensed version of Qtopia you need to do it from scratch not using TrollTech's code at all. Also if the goal is to make it a porting layer you should in other words try to implement the Qt API as a binding for GTK+. I know where where a couple of small attempts at doing that starting with the old Harmony codebase (after the main Harmony project had derailed), but none ever went anywhere. Christian On Mon, 2005-11-07 at 22:17 +0100, Holger Freyther wrote: Hi Pals, Nokia, I would be intersted in leading the development of a LGPL/BSD licensed porting layer of the Qtopia platform for the maemo platform. Why such a layer is good: -Existing applications can be utilized for Maemo by easily migrating them to use osso/hildon technology -More applications will make hildon/osso more attractive -Give developers the choiche to target any platform easily -Maemo is a great piece of Free Software and should be supported How such a port would look like: -We would use Qt2/X11 and make it look like the maemo gui -We would implement libqpe,libqtopia, libqtopia1, libqtopiapim using osso, hildon and Qt2 -In the future we should use Qt4 but that would require more porting of the applications. What we need: -Legal counseling if we can do a clean room implementations and how it should look like. -Sponsors: -People Donating Time to this project -People/Companies Donating Money to this project allowing people to work on it during office hours (not for myself though) -People writing tests and setting up a QA infrastructure -People Testing our Work -People porting/verifying application work -People enjoying using maemo How should we proceed: -We should gather enough people to start this project -We should have enough information to start the clean room implementation. -We should quantify which classes are mostly needed to port most of the apps. if you are interested please email me regards holger ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- Christian Fredrik Kalager Schaller Business Development Manager Fluendo S.L. Mobile Phone: +34 678093464 Office Phone: +34 933175153 Fax : +34 934127034 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
Hello, Clemens Eisserer wrote: From this point of view I think GTK2 was the completly wrong choice as Maemo's GUI toolkit. Its slow (mameo contains even a hacked version which tries to speed it up a bit) and heavyweight (megs of code splitted in many different shared-libs), but it was choosen for compatibility as the whole Xserver based approach. (fox-toolkit or fltk are much more efficient) I really don't share this opinion. Compared to fltk and fox GTK is much more powerful and comes with a complete system abstraction layer and - if someone doesn't like C - almost independent from the language used. The performance of the latest maemo software is pretty good having the large display and the slow CPU in mind, i can remember other devices with faster CPUs behave much worse. If you are interested in trying plain GTK in a more comparable environment you might want to try a GPE image you can easily create using OpenEmbedded. There are other reasons to port Qt, but not this one. I think with this decision in mind a port of QT would not be that bad either since it would allow running apps on your Maemo powered device which would not be able to run otherwise or would not look that good. So the argument is to add another huge toolkit because GTK is too big? I can remember someone else explained that situation before... on the other hand you can take the device and run your own Qt based filesystem on it. But then you won't need to port the tookit but port your applications to work with the 770 hardware capabilities. Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
So the argument is to add another huge toolkit because GTK is too big? I can remember someone else explained that situation before... on the other hand you can take the device and run your own Qt based filesystem on it. But then you won't need to port the tookit but port your applications to work with the 770 hardware capabilities. No, the argument is not to blame QT for beeing huge and also using using another bloated toolkit as basis. The real argument for QT would be to allow applications to run on the 770 which wouldn't work otherwise - nobody talks about including it into the default distribution but if you need program x/y I think you'll happily install QT if it allows to do what you want. Maybe linking it statically isn't a bad idea if its just used by one single program Compared to fltk and fox GTK is much more powerful and comes with a complete system abstraction layer and - if someone doesn't like C - almost independent from the language used. Well I could say the same about QT + it has an almost complete class library so I don't need any time wasting with unix broken apis ;) In _my opinion_ QT is even more powerful than GTK+ but who matters, I think this power is not needed on such devices at all and think both toolkits are not really suited for embedded use (so I would not prefer a QT based 770). If I look at the tons of Hildon/GTK based program's I've installed on my 770 I see _none_ of them using any advanced features of GTK - just basic ui like buttons, tables and lists (uhh, slow scrolling) and some images here and there. Exactly the same could be archived with one of those ultra-slim high-performance toolkits available with about 1/10 of size/footprint and 2x the performance. However, peace ;-) lg Clemens ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
Hi, Maybe linking it statically isn't a bad idea if its just used by one single program Yep, but linking QT statically would make the binary probably too big to fit nicely in the N770 flash... It's doable anyway for the ones who really want it (not me ;-) If I look at the tons of Hildon/GTK based program's I've installed on my 770 I see _none_ of them using any advanced features of GTK - just basic ui like buttons, tables and lists (uhh, slow scrolling) and some images here and there. Exactly the same could be archived with one of those ultra-slim high-performance toolkits available with about 1/10 of size/footprint and 2x the performance. Well there is more than just advanced widgets in GTK+ which is not available in all lighter toolkits (full i18n, anti-aliased fonts, glib, rich theming etc.) However, peace ;-) Agreed, let's keep the discussion technical and be open to all opinions! - Kaitsu - ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
Am 7 Nov 2005 um 22:17 hat Holger Freyther geschrieben: How such a port would look like: -We would use Qt2/X11 and make it look like the maemo gui -We would implement libqpe,libqtopia, libqtopia1, libqtopiapim using osso, hildon and Qt2 -In the future we should use Qt4 but that would require more porting of the applications. Why are you trying this? I would recommend porting the whole OPIE to the N770. That would be an alternative to Maemo. I personally feel a little bit home using Qt. Using both Maemo Qt would be a waste of resources. Do you remember the harmony project? Some tried to reimplement Qt 1.x - they never got far. Ok, there where some political problems as well. The OPIE folks seek for volunteers to help them. It would be better to support the OPIE project and provide a clean N770 port rather to implement the same GUI again and again. There are far too many GUIs available for Linux - maybe that's one of the problems Linux has. And far too many GUIs which aren't further developed. We should really stay with gtk+ here, or use OPIE to get Qt programs running. May the better system win :-) _OFF_TOPIC_ON_ An other solution would be to port the couple of programs which are missing on Maemo e.g. KO/Pi (http://www.pi-sync.net/html/ko_pi.html) to Maemo. Of course, that would be a lot of work but maybe less work than a clean room implementation of qt. Qt has other problems: Trolltech made each major release of qt incompatible to its predecessor. This is IMHO a major design fault. A lot of companies which use Qt still use the qt2 release. _ANGRY_MODE_ON_ My programs for Qtopia don't run on OPIE! That sucks! Linux has too may incompatibilities created - Libc5 to glibc, gcc1 to gcc2 to gcc 2.95 to gcc3. Are the gcc4 libs compatible with gcc3? I don't know... BUT I can still run a lot of programs, original written for Win95 on my WinXP box. Try this with linux software written in the years 95-97. No chance to get bin programs to run! And even to compile them is a little bit hard. _ANGRY_MODE_OFF_ Don't get me wrong: I like to have the possiblities with my Linux system. And I also like that the N770 device runs with Linux. But Maemo is still a new, incompatible system (ok there's some compatibility with gtk+) and writing a compatibility layer for Qt makes the situation even worse. Better use OPIE. And if OPIE is the better system, a lot of people will install it on their N770 and use it - if not, stay with Maemo and write the software for it. Keep it small and simple, and may be, a little bit faster that it is now... :-) _OFF_TOPIC_OFF_ Just my two cents, -Klaus -- Klaus Rotter * klaus at rotters dot de * www.rotters.de ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
I've been watching this thread with interest, and I have some feedback for you. Qtopia is about a 3mb footprint, it is pretty small, has its own framebuffer and doesn't rely on X, this is for Qt2x. Qt3 was never made in to an embedded version because of its size. I'm told that Qt4x was modularized better so it could be used for embedded again, I don't think anyone is doing it yet. OPIE is a problem from a licensing and compatibility point of view. OPIE is a fork of the GPL version of Qtopia and as time has gone on it has become less compatible. The other issue is the license, you cannot bundle a non-GPL app with OPIE and it is technically a GPL violation to use a non-GPL app with it because the application is now using the GPL versions of the libraries. The other problem for a commercial software company is that you can't rely on the fact that it is going to be available unless of course you have found some way to static link everything together, it would be like running a Qt app under GNOME basically. I have a huge investment in Qtopia development, nothing I'd like better than to be able to just run them on the device without having to rewrite the UI, but short of Nokia changing their mind and licensing Qtopia, any effort is just going to remain in the realm of the hobbyist IMO. At 11:11 AM 11/8/2005, you wrote: 2005/11/8, Clemens Eisserer [EMAIL PROTECTED]: ...which makes these sound a bit funky. If you use *anything* GUI-related that is already implemented, you'll drag Gtk+ in. Which will mean that you need to have both Qt and Gtk+ libraries in memory at the same time, which I think is not too hot on the current hardware. From this point of view I think GTK2 was the completly wrong choice as Maemo's GUI toolkit. Its slow (mameo contains even a hacked version which tries to speed it up a bit) and heavyweight (megs of code splitted in many different shared-libs), but it was choosen for compatibility as the whole Xserver based approach. (fox-toolkit or fltk are much more efficient) If Maemo would get a hacker every time somebody said that... I assume Qt has not got megs of code then? The Qt site boasts that: The Qt Class Library is a growing library of over 400 C++ classes [..] That doesn't sound lightweight to me ;) Gtk+ is, in my opinion, fast enough for the 770, the bulk of the performance issues come from the limited memory from which the (AFAIK non-gtk) system services occupy a fair share and from the fact that there is virtually no acceleration for the graphics. I think with this decision in mind a port of QT would not be that bad either since it would allow running apps on your Maemo powered device which would not be able to run otherwise or would not look that good. I'm all for a Qt version, diversity is good. It's having both of them in memory at the same time that is bad. Which also means that running programs for both at the same time would be bad too. And as said, most of stuff already done is in Gtk+, so you'd effectively have to write the GUI bits from scratch. But hey, in case you haven't noticed, Maemo is free software ;) -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers Regards, Shawn Gordon President theKompany.com www.thekompany.com www.mindawn.com 949-713-3276 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Alternative platforms ?
Thanks for the response Tommi, On 8 Nov 2005, at 16:23, Tommi Komulainen wrote: The Nokia 770 was the first (and only) device to use the maemo platform and some corners were cut in the process, and things like fixed display size and resolution were assumed. But limiting ourselves to only a very specific hardware configuration would be a pretty stupid thing to do in the longer term, so we are interested in making the platform more flexible. Understandable and often unavoidable at the begininng. I took 10 mins to get started installing it this evening before I'd to run for the bus. But from what I can make out, I can't see why we could have profiles for different hardware setups. Kind of what you have with using Xephyr on x86 host. I guess I'll found out the problems when I try and move from an x86 hosted setup to an x86 target. You're the more lucky ones. With larger display there are only minor cosmetic issues that really need fixing (like the status bar width and TN height) - the rest should stretch pretty much naturally. Changing the font size might bring up more problems about hardcoded assumptions about line heights in pixels. Yeah, GTK is good for that. I guess dealing with assumptions about screen size as you mentioned would be a potential issue. As I said above, my main area of non-understanding would be in how to get the maemo environment running natively on the hardware. I guess everything is setup to target the Nokia 770. Once I get the Xephyr setup running (was almost there before I had to leave today) I'll have a play with the screen sizes and see how it works. Will be an interesting experiment. -- Glen Gray [EMAIL PROTECTED] Digital Depot, Thomas Street Senior Software EngineerDublin 8, Ireland Lincor Solutions Ltd. Ph: +353 (0) 1 4893682 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
On 8. Nov 2005, at 22:28 Uhr, Kalle Vahlman wrote: So is there more candidates for this than Qt?-) Well, Cocoa/GNUstep of course! Na, just kidding ;-) Greets, Helge -- http://docs.opengroupware.org/Members/helge/ OpenGroupware.org ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] bi-di BT-link between two 770s
On Mon, 2005-11-07 at 00:00 +0200, Johan Hedberg wrote: On Sun, Nov 06, 2005, Patrick Ohly wrote: Another use of Bluetooth could be connecting the 770 to a GPS receiver. With its large screen it would make a nice moving map display, although my primary use would be to simply transfer waypoints and track data to and from a Garmin eTrex during cycling trips. I currently use an iPAQ with Familiar Linux for that purpose, but might replace that with the 770 if I can get it to work - currently I still wait for a Bluetooth-RS232 adapter (the eTrex only has a serial port). I'm sure it can be done with root access, but making the same functionality also available to users of the official firmware certainly would be nice. Searching for remote devices and creating outgoing RFCOMM connections (e.g. to serial port profile) doesn't require root privileges, so that should work just fine with the normal firmware. As the wiki states on http://maemo.org/maemowiki/BluetoothGPS root access is requiered to create the needed rfcommX device node. Following that HowTo i successfully read NMEA data from my GPS mouse. I don't know how to do this without such a device node. Jonek -- http://770.hexbox.de/blog ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] bi-di BT-link between two 770s
On Sun, 2005-11-06 at 15:32 +0200, Aleksandr Koltsoff wrote: Hello Since my BT skills are non-existant, I'm asking for help for this project. I'm thinking of implementing a simple util library that would provide two-way stream-communication between games running on two 770s (same game obviously). How should I proceed in this? The following issues come into mind, but I'm looking for someone who would have concrete information on how to solve these problems: 1) When starting the game, how does the end-user see the other 770-device? ie, is pairing necessary, and is there a GUI for this (connection damager?) ^ Hehe, that was a good one :). 2) What do I need to do to make 770 visible to the other 770 (assuming there is a GUI for this on the other side). Can this be done programmatically without requiring user intervention? This is called inquiry scan mode and has to be activated in /etc/bluetooth/hcid.conf on the 770. 3) Is using RFCOMM-sockets between the devices a suitable transport? (I'm looking for something akin to TCP). It can be assumed that only one program will be active on a device at one time that needs this, so I guess BT-MAC address is enough to connect? I just wrote a HowTo for setting up IP connections over bluetooth with the 770. http://maemo.org/maemowiki/HOWTO-BluetoothNetworking 4) Can all of this be done with a normal application installed via the AI on a stock 770? (not requiring the user to reflash from the sales sw version) So, mostly the questions arise from my lacking experience with BT-programming and my lack of experience with the 770 sw. If you know whether the problems above can be solved, I'm interested in hearing from you. I plan to release the utility lib under lgpl if it's possible to implement at all (I know that technically anything is possible, but question 4 might stop this from being possible). I would be interested in hearing from you about any successes. Greets, Jonek. -- http://770.hexbox.de/blog ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] bi-di BT-link between two 770s
2005/11/9, Johannes Eickhold [EMAIL PROTECTED]: I just wrote a HowTo for setting up IP connections over bluetooth with the 770. http://maemo.org/maemowiki/HOWTO-BluetoothNetworking I found another howto sometime ago which works better than what you describe on your howto to connect the 770 to the internet through a desktop gateway - I am typing this email from such a connection... It might be a little redhat specific in the beginning but can easly be adapted to other distros. it's here: http://www.cs.ucla.edu/~cclljj/interest/notes/bluez/pand_dund.html The only issue I have with this is that the nokia doesn't get a default gw, I think I'll need to fix my pppd options, to make it work. Otherwise both devices get an ip address for the bnep0 interface, and the 770 gets its dns entries. Cheers, -Giuseppe ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] bi-di BT-link between two 770s
On Wed, Nov 09, 2005, Johannes Eickhold wrote: Searching for remote devices and creating outgoing RFCOMM connections (e.g. to serial port profile) doesn't require root privileges, so that should work just fine with the normal firmware. As the wiki states on http://maemo.org/maemowiki/BluetoothGPS root access is requiered to create the needed rfcommX device node. Following that HowTo i successfully read NMEA data from my GPS mouse. I don't know how to do this without such a device node. Well, the wiki is wrong :-) You can connect to the device as normal user using e.g. rfcomm connect /dev/rfcomm0 bt addr (the mknod part in the wiki is unecessary because udev should do the job for you). The bind method described in the wiki does indeed require root privileges, but even in that case you can use the rfcomm_bind method of the btcond D-BUS interface [1] which doesn't require root privileges. Actually, if you intend to use gpsd for GPS access I think the bind method is better because gpsd will only open the device when needed (so the BT connection will also only be created when needed). [1] http://www.maemo.org/platform/docs/osso-gwconnect.html Johan ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
