Re: [maemo-developers] bounty program?
This kind of plan wouldn't raise priority on a specific task the way that traditional incentive programs aspire to (and often fail to anyway), but it would reward active development on the project space in general. It also removes the demeaning aspect of traditional incentives (I'll give you $4 to spend 50 hours of your free time working on this!), replacing it with more of a Good job! I appreciate the hard work you put in! feeling. I like that idea very much. The question remains if there are people ready to pay bounties or fulfill them. Don't hesitate to give input things you would like (this can also be to me directly if you don't want to post to on the list) I guess it will be more the end users who will want to get a certain functionality implemented. I see that some of the item in 2006Wishlist where performed. http://maemo.org/maemowiki/ApplicationCatalog2006Wishlist What would it take to change this idea into action? greetings ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] How to extend Hildon Input Methods
Hi, I just tried to create a customized IM so compiled code example, him-plugins-sdk-example-0.0.2.tar.gz. But I got the following error. configure: error: Library requirements (libhildon-input-method-framework-header-sdk-2.0 = 2.0.0 libhildon-input-method-ui-header-sdk-2.0 = 2.0.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. As tutorial, the components are required but how can I get them? - Kimitake Abe http://kimitake.blogdns.net ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] 770 rebooting
Hi, I encountered the similar random reboot on N800. I can get free WiFi access from my home, so I just tried to connect it but N800 couldn't, and it seems to try to connect several times or presence status tried to update the status, and then N800 rebooted suddenly. In addition, I have DELL laptop, Latitude D820. which has embedded wireless and BT. Usually, I disable the functions but when I turned it on, then N800 lost wireless connection (which is different from free WiFi AP), and it seems to try to connect free WiFi. Regards, Kimitake -Original Message- From:Kalle Valo [EMAIL PROTECTED] To: maemo-developers@maemo.org Date:Fri, 12 Jan 2007 18:11:25 +0200 Subject: Re: [maemo-developers] 770 rebooting ext Kalle Valo [EMAIL PROTECTED] writes: Also, there are some bugs left in the 770 OS which only Nokia can fix (like rebooting every 5 minutes when using WPA for wireless). I have never heard about these kind of problems and this gets me really worried, as being a WLAN developer for 770. Please, tell me more about this. Klaasjan pointed me to bug #820 in a private mail: https://maemo.org/bugzilla/show_bug.cgi?id=820 If someone else is also seeing similar crashes with WPA, please report to that bug. Thanks. -- Kalle Valo ___ 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] developing for 770 with IT2006 on Debian testing with 2.6.18 kernel
On Fri, 2007-01-12 at 22:30 +0100, Patrick Ohly wrote: Duh, replying to myself: I now found the hint about Maemo 2.2 in [1]. So hopefully I'll have a working SDK again soonish... [1] http://www.maemo.org/downloads/maemo_3_compatibility.html Why not put this kind of information on [1]? I think it fits in better there. Btw. [1] seems to be outdated. Yes, i know there will be a relaunch of the maemo.org site ;-). Greets, Jonek. [1] http://maemo.org/platform/docs/roadmap.html ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] is it possible to use Xming?
Is it possible to use Xming as a xserver? I try with Xming :0 -screen 0 800x600 -dpi 96 -ac and set the correct DISPLAY other xclient is able to run on Xming, but hildonUI is failed to display? many Thanks, ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] participate in Developer Device Program
Hello, I am very interested in this new device (n800). I have not released open source software yet, but if I can get a n800 for less than 100$, I will try to port my windows shareware (receipe database) to this lovely device! (_www.datanorm-software.de/kochbuch.htm_ (http://www.datanorm-software.de/kochbuch.htm) ) I have experience in programming linux devices (mipsel-linux) but 400 EUR is a little bit to much for me for a hobby project. My native language is german. Bye Uwe ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] kernel modules
(Sorry for the Outlook web damage.) On Friday, Zoran Kolic wrote: I'm sure that not a box should go in the wild naked, without firewall. Maybe this is just me being thick, but why would you want a firewall if you're not running any services? Cheers, Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: gethostbyname() ?? Unable to become root
Hi, I'm just trying to get example_libosso.c to compile and run. Compiling seems fine, but when i run it, the osso_initialize fails. I thought this was because it didn't have the D-Bus service file and the .desktop file so i added those and it still fails. I was hoping someone could point out where i've gone wrong. example_libosso.c is unmodified apart from an error message print out on osso_initialise. Thanks Andrew ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] is it possible to use Xming?
(Sorry again for the Outlook web client.) On Jan 13th, Johny Kadarisman wrote: Is it possible to use Xming as a xserver? Yep. I try with Xming :0 -screen 0 800x600 -dpi 96 -ac and set the correct DISPLAY other xclient is able to run on Xming, but hildonUI is failed to display? Try bind-mounting /tmp inside Scratchbox. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: kernel modules
Maybe this is just me being thick, but why would you want a firewall if you're not running any services? Why not? And, ports are used every time I do something on the net. Statefull firewall would be the perfect filter for in and out packets. I see implemented iptables as stateless, since it does not fulfils netfilter specs. Some modules are missing. Would be nice if nokia could provide us/me/user with those modules and info, what is changed in this instance. I use ipfw on my box and cannot imagine going in the void w/o this. Some says openbsd ip is even better. So, I like to have my 770 as any other machine, for mail, web, ssh, telnet... I really need firewall for this. Making new environment could be fun, but not now. Why not having repository for kernel modules and libraries for (in this example) scirocco? For some time I will for sure remove some files for localisa- tion, some graphical stuff, when I use only console versions etc. On this place could lay modules I like. When you abandon 770 for good I will recompile the kernel et alia, but no need for it now. Why all of people in nokia opose to firewall? You put it on the box. Lets make it fully functional, please. Zoran ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Re: kernel modules
On Jan 13th, Zoran Kolic wrote: Why all of people in nokia opose to firewall? You put it on the box. Lets make it fully functional, please. Because it doesn't make any sense. Even if you are using outbound services, that doesn't magically open a hole in your machine that other people can access, because there's nothing listening. If you install extra services that listen on ports on public interfaces: a) those should be fixed, and b) if they must be open, then a firewall would be useful to _restrict_ access. However, short of that, then there's no point. If there are no open ports (via listening services), then there is nothing for a firewall to protect, period. It would be like erecting an enormous flood barrier in the middle of the Australian desert, or putting traffic lights in the middle of a large park. It just doesn't make sense, full stop. This is exactly the same approach that Ubuntu (used by tens of millions worldwide) takes, because we decided very early on to ship it with zero open ports. Therefore, there was no point in having a firewall, because there was _nothing to protect_. This is the exact same situation as with Internet Tablet OS. Cheers, Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: kernel modules
Daniel, iptables is already on 770. It just works like its not. Zoran ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: gethostbyname() ?? Unable to become root
(sorry about the title, i'll keep it the same so the answer is in the same thread) Looks like you just have to launch it from the menu, you can't just ./example_libosso to execute it. Andrew andrew gatt wrote: Hi, I'm just trying to get example_libosso.c to compile and run. Compiling seems fine, but when i run it, the osso_initialize fails. I thought this was because it didn't have the D-Bus service file and the .desktop file so i added those and it still fails. I was hoping someone could point out where i've gone wrong. example_libosso.c is unmodified apart from an error message print out on osso_initialise. Thanks Andrew ___ 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] Re: kernel modules
Zoran Kolic wrote: Some modules are missing. Would be nice if nokia could provide us/me/user with those modules and info, what is changed in this instance. Why not doing it yourself instead of repeating it many times in the list? ;-) If you really need firewall then go ahead - http://maemo.org/maemowiki/HowTo_KernelCompilation Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: gethostbyname() ?? Unable to become root
andrew gatt wrote: Looks like you just have to launch it from the menu, you can't just ./example_libosso to execute it. You can also use the run-standalone.sh -script to launch it. Without it (or launching from the menu) some environment variables will not be set (most importantly the DBus bus addresses) and osso_initialize will fail. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Is it possible to use maemo 3.0 SDK for 770?
Hey @all, i have a simple question. Is it possible to use maemo 3.0 SDK for nokia 770? thank you! ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] dbus_bus_activate_service
Is there any way to compile and use dbus_bus_service_activate under maemo. https://stage.maemo.org/svn/maemo/projects/email/osso-email/trunk/src/ui/viewcallback.c Seems to suggest you can, however i can't get the function to compile, the compiler flags it as an undefined reference with all the headers i've tried. Doing `grep dbus_bus_activate_service /usr/include/ -R` doesn't bring anything up so does it not exist? Any ideas? Andrew ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Scirocco 2.1 Installer - bad trap
Hello all, i am actually trying to use installer from scirocco 2.1 release: Here you can see what happens under Ubunto - terminal: [EMAIL PROTECTED]:~/Desktop$ chmod 770 installer [EMAIL PROTECTED]:~/Desktop$ ./installer -s trap: 47721: SIGINT: bad trap [EMAIL PROTECTED]:~/Desktop$ What can I do to use installer? Thanks !!! ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] setup error
I'm following the instructions for Scratchbox installation http://www.maemo.org/platform/docs/howtos/Maemo_tutorial.html#Installation I'm running Ubuntu breezy badger. When I get to this step: [sbox-SDK_PC: ~] sbox-config -cc I get this error: cp: cannot overwrite directory `/usr/include/asm' with non-directory I was going to ignore it, but I figure that could bite me in the ass later. Any ideas? TIA Joel ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Aw: [maemo-developers] setup error
every time i installed the scratchbox 2.0 i got this error. It does not matter my installations works fine but i only dev. Python - pygtk br Mathias - Ursprüngliche Mitteilung - Von: Joel Gwynn [EMAIL PROTECTED] An: maemo-developers@maemo.org Gesendet: Sa., 13. Jan. 2007 18:39:41 CET Betreff: [maemo-developers] setup error I'm following the instructions for Scratchbox installation http://www.maemo.org/platform/docs/howtos/Maemo_tutorial.html#Installation I'm running Ubuntu breezy badger. When I get to this step: [sbox-SDK_PC: ~] sbox-config -cc I get this error: cp: cannot overwrite directory `/usr/include/asm' with non-directory I was going to ignore it, but I figure that could bite me in the ass later. Any ideas? TIA Joel ___ 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] Cairo performance comparison, 770 / N800 / PXA-320
Hi! We have all sorts of funny hardware at the office, so I thought I'd make a quick run of cairo-perf with the Cairo 1.3.10 snapshot and see how they relate to each other. There's some funny things I encountered in the results, and I hope people on both lists can offer insights on why. Details at http://syslog.movial.fi but let's just say that the results were predictable in general, with some surprises: N800 is naturally faster than 770, but I didn't expect the xlib backend to have so big differences between the two. For the cairo audience there's the question of the tessellation process, can it really be so fast on the PXA-320 or is there a bug somewhere that twists the results? What could be so good in PXA-320 (or not-good on the other devices) that the results are so drastic? -- 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
[maemo-developers] Bluetooth Headset Support - Status update?
Referring back to this thread: http://www.gossamer-threads.com/lists/maemo/developers/12526?nohighlight=1#12526 Tommi asked that this subject be brought up again after the next release (which I presume to have been OS2007) so it isn't forgotten. Is it possible to get an updated position on Bluetooth Headset support on both 770 and N800? It's crazy that after all this time with VoIP support that these devices still don't have Bluetooth Headset and A2DP support. The 770 and N800 are crying out for BT headset support! :) Neil ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth Headset Support - Status update?
On Jan 13, 2007, at 2:18 PM, Neil MacLeod wrote: Is it possible to get an updated position on Bluetooth Headset support on both 770 and N800? It's crazy that after all this time with VoIP support that these devices still don't have Bluetooth Headset and A2DP support. The 770 and N800 are crying out for BT headset support! :) I'm pretty sure that you could write an A2DP music player that worked on the 770 without any help from Nokia. It wouldn't be nicely integrated, but it should work. I tested an app awhile ago, and got music coming out of my headset, it was just not real time - a second of music, 5 seconds silence, etc. The reason for this is that it needed to transcode the music into a different CODEC, for which there was no integer version available. If you were to, say, just store all your music in that format, transcoding as you uploaded to the 770, then no problem. Headset / handfree support requires SCO sockets, which are a deeper, driver level thing. Many Bluetooth chipsets handle SCO connections in special ways - they do things like feed the audio out a separate interface so you can hook up a microphone and speaker directly, rather than pushing the audio through the CPU. Thus, there's often more config and poking needed to get the chipset into the right mode. Does anybody know if the N800 uses the same Bluetooth chipset as the 770? Thanks, gopi. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Bootmenu updated, experimental n800 support
Hello, I have updated bootmenu initfs flasher. This version comes with slightly newer bootmenu version from garage svn and has experimental support for n800 device. It still works on N770 of course. For N800 only newer 2006-51 firmware (the downloadable one) is supported. As I don't have N800 it is just blind test. Many things can go wrong so please try it only if you don't mind and know how to recover. It has some chance to actually work but who knows :) Recovery is easy, either backup initfs.orig.jffs created by the script or extract original initfs from FIASCO image and flash from PC over USB. No data should be lost. New features: - uses optional bootmenu.conf for easier and safer customization, see included example - new 'off' item for turning device off, doesn't work when on charger download URL http://fanoush.wz.cz/maemo/initfs_flasher.tgz I am very interested how it goes on N800 so please report. Thank you :-) Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Hardware failure
Hello, i have a question for extensive use of the device. I use my device about 14/7 most of that time the device is connect via wlan. Now i got a strange problem. During reading a email the screen went off and on once. After the screen went on the graphic looks like a water paint which is cleand with a wet shirt. i got vertical stipes and the colours are very brightly. First i thought it was a memory problem. But i could not fix the problem neither with turn on / off, take the batt. out of the device nor with flashing. I am not familiar with the Hardware - could it be the graphic ship? This question is only to improve my knowledge because the service from Nokia Germany is really great. Last year i had two problems and i shipped my device in via a local dealer. Both times i got a changed device back. So is there no a developer with magic abilities i will send my device to Nokia Germany changing should not be a problem because the N770 is still availible in Germany. BUT IT WOULD BE A STRANGE WEEKEND Does anybody knows how to turn on a laptop and check emails :-)) br Mathias ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Cairo performance comparison, 770 / N800 / PXA-320
On Saturday 13 January 2007 21:00, Kalle Vahlman wrote:
We have all sorts of funny hardware at the office, so I thought I'd
make a quick run of cairo-perf with the Cairo 1.3.10 snapshot and see
how they relate to each other.
There's some funny things I encountered in the results, and I hope
people on both lists can offer insights on why.
Details at
http://syslog.movial.fi
but let's just say that the results were predictable in general, with
some surprises:
N800 is naturally faster than 770, but I didn't expect the xlib
backend to have so big differences between the two.
Maybe these devices were just running different linux kernels (task
sheduler may be different) and xservers? So quite a lot of code could
be different and these results can't be used to compare these cpus
directly.
For the cairo audience there's the question of the tessellation
process, can it really be so fast on the PXA-320 or is there a bug
somewhere that twists the results? What could be so good in PXA-320
(or not-good on the other devices) that the results are so drastic?
What is the amount of cache on all these devices? If PXA-320 has
more cache and all the necessary code/data for this test fit it but not on
the competing device, that could explain the difference.
By the way, here you can take some code for benchmarking cpu clock frequency:
https://garage.maemo.org/plugins/scmsvn/viewcvs.php/trunk/libavcodec/tests/testfreq.c?root=mplayerview=markup
It performs two test runs, the first run contains a loop with 10 add
instructions, the second run just contains the same loop but empty.
Substracting time of the second run from the time of the first run we get
the time of executing these add instructions only. Number of such
instructions executed per second can be used to measure cpu clock
frequency. For getting best precision you may want to increase
TESTS_COUNT define, it will result in a longer test time though.
This test program can show results a bit lower than the actual clock
frequency (as we have a multitasking OS and other processes also
take some time). But real cpu clock frequency can't be lower than the
result benchmarked :) Even for superscalar cpus, these add
instructions can't be run in parallel as each new instruction depends
on the result of the previous one (hmm, just thought that the last add
instruction in a loop can be run in parallel with subs which decreases
loop counter, maybe some additional tweak will be required).
Also Nokia 770 runs not at 220MHz as stated on your page, but at
something closer to 250MHz as shown by this test code program
(and confirmed to be actually 252MHz by somebody from Nokia
on #maemo about half a year ago).
As for optimizing code for ARM (targeting Nokia 770), there are a few things
that are slow (maybe this list is still incomplete):
1. Floating point math is slow without vfp (cairo contains a lot of fp math)
2. Integer division is slow ('/' and '% operators) as ARM does not have
hardware instruction for it and much less efficient software implementation is
used.
3. write access to noncached memory is slow for read-allocate cache on arm926
core (data is not loaded into cache on write), see more details here:
http://maemo.org/pipermail/maemo-developers/2006-December/006579.html
I have some crude patch for valgrind (callgrind part) to simulate
read-allocate cache behaviour (instead of write-allocate as is simulated
by default), it can show parts of code which have lots of cache misses. If
anybody is interested, I can try to clean it up and submit upstream:
http://ufo2000.xcomufo.com/maemo/vg-read-allocate-cache-patch.diff
I also had a quick look at cairo sources (without benchmarking it, just to
see general coding style). Some parts of code in it are not optimal. For
example this code chunk from cairo-path-stroke.c relies on integer division
(it is unlikely to cause severe performance decrease here, but may become
a real problem for tight loops):
[cut]
for (i=start; i != stop; i = (i+1) % pen-num_vertices) {
tri[2] = f-point;
_translate_point (tri[2], pen-vertices[i].point);
_cairo_traps_tessellate_triangle (stroker-traps, tri);
tri[1] = tri[2];
}
[/cut]
If we go deeper into _cairo_traps_tessellate_triangle, we will notice the
following:
[cut]
memcpy (tsort, t, 3 * sizeof (cairo_point_t));
qsort (tsort, 3, sizeof (cairo_point_t), _compare_point_fixed_by_y);
[/cut]
There is unnecessary memcpy operation, also qsort is called for just three
elements! And such performance bottlenecks are quite easy to spot almost
everywhere. Most likely the code that is performance critical, is optimized a
lot better, but anyway at least this part deserved a comment such as
/* I know that it is slow, but this code is not performance critical and I'm
too lazy to optimize it */ :-)
Anyway, now I see no surprise that such huge improvements were possible
recently :-)
Also this code does
Re: [maemo-developers] Cairo performance comparison, 770 / N800 / PXA-320
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Siarhei Siamashka schreef: On Saturday 13 January 2007 21:00, Kalle Vahlman wrote: As for optimizing code for ARM (targeting Nokia 770), there are a few things that are slow (maybe this list is still incomplete): 1. Floating point math is slow without vfp (cairo contains a lot of fp math) Actually not very much if you build it with --disable-some-floatingpoint regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFqWDBMkyGM64RGpERAs5EAJ9ooyKzO9GbT5aFffpdWKOfvZ31ZgCgt7Tr bOkcruGVr+RNqw2NNPwUjFs= =v9oM -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth Headset Support - Status update?
Hi, On Sat, Jan 13, 2007, Gopi Flaherty wrote: Does anybody know if the N800 uses the same Bluetooth chipset as the 770? 770 has a TI chip while the N800 uses a CSR chip (BlueCore4). To use SCO audio using existing bluez software you need to get the chip into SCO over HCI mode (I think both devices are by default in SCO over PCM mode, i.e. try to transfer audio over a direct HW link between the bluetooth controller and the DSP). You'll probably find the procedure for manipulating the SCO routing on the CSR chip somewhere on bluez related web pages (maybe the available SW even does it automatically) since CSR dongles are quite popular. I don't know the exact procedure my self. AFAIK, the procedure of changing the SCO routing on the TI chip requires a proprietary TI HCI command. I'm not sure we can publish it since it's documented in TI docs which have quite strict publication restrictions. I.e. this still needs some internal investigation. However, even with the command, neither the chip firmware nor the driver have been tested with SCO so there is guarantee that it'd work. We are currently working on integrating SCO support (Headset Profile to be exact) nicely with the new and still experimental D-Bus based service infrastructure of bluez and the rest of the internet tablet software. The plan is to use the DSP routing instead of the HCI routing, which should improve latencies. So, you should see support for this in some SW update in the future. Unfortunately I can't give any exact schedule currently, but you can follow the progress quite well simply by looking at what's going on with bluez (i.e. CVS commits mailing list discussions). You'll probably see some preliminary support in the next release of bluez-utils (version 3.9). Oh, and it's possible that A2DP support will come along at some point too since from the bluez side the plan is to integrate it to the same audio daemon as HSP/HFP. However, from our (Nokia) perspective it hasn't been given the same priority as HSP so in the short term support for it will be very unofficial if it exists at all. Some ideas (a very early draft) for the planed architecture can be found at the bluetooth-alsa pages: http://bluetooth-alsa.sourceforge.net/future.html Johan ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Ideas for unifying the IT OS codebase
Hello, I was delighted to hear that Nokia will be working on at least attempting to unify the codebases running on the 770 and N800 [1]. To help in this work I'd like to offer a few ideas on how you might proceed with the work. In the short-term the main problem is obviously getting the OSS and Nokia-controlled parts of IT OS 2007 running on the 770. To make this as easy as possible I'd suggest that you: - Publicly document all of the current differences between the two codebases - Publicly document all of the differences between the devices to the extent that you can - Open as much of your own code as you can so that others can contribute to it Once the modifiable components (i.e. OSS and Nokia-controlled stuff) have been fixed to run on both the 770 and N800, the next step is to make sure that the commercial components run on the updated unified codebase. To do this, I'd suggest that you: - Preferably work with your suppliers and try to make a single version of each commercial component run on both the 770 and N800. (excluding device drivers, obviously) - If (and only if) that doesn't work: - Write wrapper code so that the single core system can handle two different versions of a commercial component. - Offer frequently updated bleeding-edge releases so that developers and enthusiasts can test the applications/components. When/if the above things are done you should basically be able to release OS2007 for both devices. Going forward from that here are some thoughts: Try to maintain a single API for applications for all supported versions of IT OS by: - Backporting all new parts of the API to older supported IT OS versions - Deprecating old parts of the API with a grace time on one major IT OS version instead of the current grace time of 0. - Completely decoupling the core system and the application API from any commercial components (e.g. by using wrapper code) and thus ensuring that you can control the way the API evolves. To make the commercial components a lesser pain in the ass in the future: - Wherever commercial components are needed, try to encapsulate them into drivers/plugins so that one version of the core system can run separate versions of the commercial components (and so that they can be replaced as easily as possible) - Participate in or sponsor work on porting WebCore to Maemo and thus getting rid of Opera (which, IMHO is one of the biggest problems right now). - Participate in or sponsor open source projects which are trying to implement similar functionalities as one of the other commercial components you currently use (e.g. handwriting recognition). - Try to persuade your hardware suppliers to open source their drivers and/or to open as much documentation as possible, in order to facilitate the development of open source drivers. - When/if that fails, support possible reverse-engineering projects by any legal means you have (e.g. by supplying testing hardware). Now and in the future, to offset the possible costs from relicensing new and updated proprietary components to old devices you might want to consider an upgrade path along the following lines: - Offer free upgrades for the warranty period of a device or a similar timeframe (e.g. 2 years in Finland). - After the warranty has expired, charge a reasonable fee (say 20-40 €) for the latest major version of the IT OS. - If possible, offer the second latest major version of the IT OS free (or for a really, really low price) to all users. - Annually end of life the IT OS major version released two years earlier. So, for example right now IT OS 2006 and 2007 are actively maintained and supported, whereas IT OS 2005 has been EOL'ed. Next year IT OS 2008 would be offered as a free upgrade to everyone whose warranty hasn't expired (and as a purcaseable upgrade to others). IT OS 2007 on the other hand would be offered as a free (or really really cheap) upgrade to everyone and IT OS 2006 would be EOL'ed. This approach would mean that: - At any point in time you'd have to maintain and support just two major versions of the IT OS - Older versions of the IT OS could be truly EOL'ed, since upgrading to a supported version would be free (or really cheap) for all users. - No customer would feel left behind (or at least I would think so) 1. http://jaaksi.blogspot.com/2007/01/were-getting-some-feedback-and-weve-got.html ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth Headset Support - Status update?
Gopi I'm pretty sure that you could write an A2DP music player that worked on the 770 without any help from Nokia. It wouldn't be nicely integrated, but it should work. I tested an app awhile ago, and got music coming out of my headset, it was just not real time - a second of music, 5 seconds silence, etc. The reason for this is that it needed to transcode the music into a different CODEC, for which there was no integer version available. you must have tried our sbc encoder before any optimization. we have a version that runs ok* in 32 bits that should execute in realtime without burning up too much battery life. you were to, say, just store all your music in that format, transcoding as you uploaded to the 770, then no problem. sbc typically takes twice the space of mp3 and then you'd need to build an sbc decoder into gstreamer to play your files through wired audio. fyi, there are headsets out there that have an mp3 decoder. our a2play test app at least recognizes when the mp3 decoder is present even though it doesn't try to use it. Thus, there's often more config and poking needed to get the chipset into the right mode. Does anybody know if the N800 uses the same Bluetooth chipset as the 770? it's a bluecore4. you could use bccmd to route its audio to hci. if you do mess around with bccmd, i'd recommend you make all changes to ram and just don't even bother with the permanent settings. it would be so sad to brick the bluetooth adapter in a new n800. brad * resulting audio is not very loud and occasionally makes a pop sound on high-volume input. 64-bit version runs without these problems. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth Headset Support - Status update?
Hi Brad, Thus, there's often more config and poking needed to get the chipset into the right mode. Does anybody know if the N800 uses the same Bluetooth chipset as the 770? it's a bluecore4. you could use bccmd to route its audio to hci. if you do mess around with bccmd, i'd recommend you make all changes to ram and just don't even bother with the permanent settings. it would be so sad to brick the bluetooth adapter in a new n800. actually it is a ROM chip and so you can't brick it in any way. A reboot will fully restore it. Regards Marcel ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Howto: using two scratchbox environments
The standard maemo 3.0 SDK installation documentation states that it is recommended that previous versions of the SDK be uninstalled before installing the new SDK. But, it seems reasonable that developers will want to maintain both the 2.0/2.1 and 3.0 installations due to the need to build packages for both the 770 and N800. No information is provided for how to do this, but something in the scratchbox installation document alludes to how to make this happen. Move your existing scratchbox installation to another directory and also untar the R4 scratchbox files to a different directory. On my system, I am using /scratchbox_insts/version number/scratchbox for the different versions of scratchbox. At this point, you should no longer have a /scratchbox directory on your system. Whenever you want to use a particular version of scratchbox, create a /scratchbox symbolic link using ln -s that links to the correct scratchbox directory. Make sure to run /scratchbox/sbox_ctl stop (if scratchbox is running) before deleting the symbolic link in order to switch to a different installation. It would be nice to see this mentioned in the maemo 3.0 installation documentation, because until we have maemo 2.2, developers may find themselves needing to switch back and forth between the 2.0/2.1 and 3.0 SDKs. Aaron ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth Headset Support - Status update?
Johan Hedberg [EMAIL PROTECTED] writes: AFAIK, the procedure of changing the SCO routing on the TI chip requires a proprietary TI HCI command. I'm not sure we can publish it since it's documented in TI docs which have quite strict publication restrictions. I.e. this still needs some internal investigation. I know that at least *I* would appreciate even the most minimal information about how this works. That way, even if Nokia never gets around to it, someone else would have the info needed to do so themselves. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Cairo performance comparison, 770 / N800 / PXA-320
2007/1/14, Koen Kooi [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Siarhei Siamashka schreef: On Saturday 13 January 2007 21:00, Kalle Vahlman wrote: As for optimizing code for ARM (targeting Nokia 770), there are a few things that are slow (maybe this list is still incomplete): 1. Floating point math is slow without vfp (cairo contains a lot of fp math) Actually not very much if you build it with --disable-some-floatingpoint I didn't (had forgot about the whole flag :), but will do (should be interesting). -- 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
