Re: [maemo-developers] sbox-config
2007/2/11, Piotr Pokora [EMAIL PROTECTED]: Hi! Is there any how-to, docs , whatever which describes how to replace sbox-config with sb-conf for fundamental jobs like flashing? Heh, that wording is pretty prone to misunderstandings :) But for the actual issue, simply stating 'sb-conf' will give you the syntax of that command. This won't naturally help since the howto doesn't tell what it tries to do there, so a short run-through: -ct ROOTFS (create target called ROOTFS) -cn cs2005q3.2-glibc-arm (use the issued toolchain) -cm qemu-arm (use qemu-arm as the CPU transparency method) --devkits=debian (use the debian devkit) The same command with sb-conf would be: sb-conf setup ROOTFS -c cs2005q3.2-glibc-arm -d debian:cputransp -t qemu-arm-0.8.1-sb At least it seemed to create the target ok, didn't try to use it though... -- 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] Is this a bug in python-osso ? (osso rpc call with argument)
Hi there.
As a followup of my previous message (problem using dbus rpc call with
argument in python) i decided to give rpc_async_run a try instead of
rpc_run.
Now, not only it 'does not work', but pyhton2.5 segfault as well.
I guess i did something wrong like not having an osso context properly
set or something like this, but i also feel it should be up to libosso
or python-osso to check the argument it use ar ok, shouldnt it ?
I have attached a test cased based on :
http://maemo.org/platform/docs/python-bora/python_maemo_howto.html#Introduction+to+LibOSSO
I also try to catch a backtrace, with 'gdb /usr/bin/python2.5 core' ,
but i m not that familiar with gdb, nor do i know where to get the
python-osso debug symbols.
Anyway, the begining of the backtrace looks like this:
#0 0xb72d068c in _python_to_rpc_t () from
/usr/lib/python2.5/site-packages/osso/rpc.so
#1 0xb72cfc61 in Context_rpc_run_with_defaults () from
/usr/lib/python2.5/site-packages/osso/rpc.so
#2 0xb79f09b9 in osso_rpc_run () from /usr/lib/libosso.so.1
Am i wrong in thinking there is something wrong in python-osso ?
I use python2.5-osso 0.2-1osso1.
_python_to_rpc_t is defined in python-osso/src/osso-helper.c, but this
is where i m stuck at, not understanding what may be wrong there (i
guess one of the 2 argument being sent has not the right type or size or
something, but that s about it).
Any help would be appreciated.
Pierre Amadio
Core was generated by `/usr/bin/python2.5 ./sender.py'.
Program terminated with signal 11, Segmentation fault.
#0 0xb72d068c in _python_to_rpc_t () from
/usr/lib/python2.5/site-packages/osso/rpc.so
(gdb) bt
#0 0xb72d068c in _python_to_rpc_t () from
/usr/lib/python2.5/site-packages/osso/rpc.so
#1 0xb72cfc61 in Context_rpc_run_with_defaults () from
/usr/lib/python2.5/site-packages/osso/rpc.so
#2 0xb79f09b9 in osso_rpc_run () from /usr/lib/libosso.so.1
#3 0xb79b8c3f in dbus_pending_call_get_data () from /usr/lib/libdbus-1.so.2
#4 0xb79a74d9 in dbus_connection_has_messages_to_send () from
/usr/lib/libdbus-1.so.2
#5 0xb79a9bf8 in dbus_connection_dispatch () from /usr/lib/libdbus-1.so.2
#6 0xb75d6f2d in dbus_g_message_get_message () from
/usr/lib/libdbus-glib-1.so.2
#7 0xb79408e7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#8 0xb7942285 in g_main_context_acquire () from /usr/lib/libglib-2.0.so.0
#9 0xb79425aa in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#10 0xb774bb23 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#11 0xb6f32d8b in init_gtkimpl () from
/usr/lib/python2.5/site-packages/gtk-2.0/gtk/_gtkimpl.so
#12 0xb7e973c8 in PyEval_EvalFrameEx () from /usr/lib/libpython2.5.so.1.0
#13 0xb7e98c40 in PyEval_EvalCodeEx () from /usr/lib/libpython2.5.so.1.0
#14 0xb7e98c9b in PyEval_EvalCode () from /usr/lib/libpython2.5.so.1.0
#15 0xb7eabfe0 in PyErr_Display () from /usr/lib/libpython2.5.so.1.0
#16 0xb7eac4be in PyRun_FileExFlags () from /usr/lib/libpython2.5.so.1.0
#17 0xb7eacec7 in PyRun_SimpleFileExFlags () from /usr/lib/libpython2.5.so.1.0
#18 0xb7ead5b3 in PyRun_AnyFileExFlags () from /usr/lib/libpython2.5.so.1.0
#19 0xb7eb4985 in Py_Main () from /usr/lib/libpython2.5.so.1.0
#20 0x0804856e in main ()
[D-BUS Service]
Name=spam.eggs.osso_test_receiver
Exec=/home/melmoth/dev/rapier/receive.py
#!/usr/bin/python2.5
import osso
import gtk
def callback_func(interface, method, arguments, user_data):
print RPC received,user_data
print arg=,arguments
#osso_c = user_data
#osso_sysnote = osso.SystemNote(osso_c)
#osso_sysnote.system_note_infoprint(osso_test_receiver: Received a RPC to %s. % method)
return ok data has been processed
osso_c = osso.Context(osso_test_receiver, 0.0.1, False)
print osso_test_receiver started
osso_rpc = osso.Rpc(osso_c)
osso_rpc.set_rpc_callback(spam.eggs.osso_test_receiver,
/spam/eggs/osso_test_receiver,
spam.eggs.osso_test_receiver, callback_func, 'plop')
gtk.main()
#!/usr/bin/python2.5
import osso
import hildon
import gtk
def process_rpc_answer(retval):
print process_rpc_answer called:,retval
return True
def send_rpc(widget, osso_c):
Cf http://www.maemo.org/platform/docs/pymaemo/pyosso_context.html#rpc_run_with_defaults
osso_rpc = osso.Rpc(osso_c)
test=osso_rpc.rpc_async_run(spam.eggs.osso_test_receiver,
/spam/eggs/osso_test_receiver,
spam.eggs.osso_test_receiver,
do_something,
process_rpc_answer,
'some user data',
('argA','argB')
)
print test=,,test
print RPC sent
osso_c = osso.Context(osso_test_sender, 0.0.1, False)
window = hildon.Window()
window.connect(destroy, gtk.main_quit)
send_button = gtk.Button(Send RPC)
window.add(send_button)
send_button.connect(clicked, send_rpc, osso_c)
Re: [maemo-developers] sbox-config
Hi! But for the actual issue, simply stating 'sb-conf' will give you the syntax of that command. This won't naturally help since the howto doesn't tell what it tries to do there, so a short run-through: -ct ROOTFS (create target called ROOTFS) -cn cs2005q3.2-glibc-arm (use the issued toolchain) -cm qemu-arm (use qemu-arm as the CPU transparency method) --devkits=debian (use the debian devkit) The same command with sb-conf would be: sb-conf setup ROOTFS -c cs2005q3.2-glibc-arm -d debian:cputransp -t qemu-arm-0.8.1-sb OK. Thanks :) At least it seemed to create the target ok, didn't try to use it though... What to do with recommended scripts like make_rootimage ? ./make_rootimage.sh: line 152: sbrsh: command not found Resetting target SDK_X86 sbox-config is obsolete; it has been replaced by these commands: (sb-conf and sb-menu here) Should I read docs provided by maemo which leads to nothing? Or should ask here about every single detail and try to hack everything myself? My point is that maemo.org makes me confused when I want to do anything , so I have no idea what should I follow there. Piotras ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Dillo for N800/770
Hello list, I'll like to know if someone knows if there is a port for N800 or 770 available ? Refer: http://www.dillo.org/ Cheers, Kevin ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] sbox-config
2007/2/11, Piotr Pokora [EMAIL PROTECTED]: [snip] What to do with recommended scripts like make_rootimage ? ./make_rootimage.sh: line 152: sbrsh: command not found Resetting target SDK_X86 sbox-config is obsolete; it has been replaced by these commands: (sb-conf and sb-menu here) Should I read docs provided by maemo which leads to nothing? Or should ask here about every single detail and try to hack everything myself? My point is that maemo.org makes me confused when I want to do anything , so I have no idea what should I follow there. Well, I guess all you can do is ask/request here, file a bug in the bugzilla doing the same and then wait and pray that someone at Nokia or someone from the community picks it up and does an updated howto. So far it's been quite obvious that the SDK is only meant for application development on the provided libraries and infrastructure, not as a do-it-yourself-kit for embedded environments. The bad news is that not even the documents directed at the application developers have been of remarkable quality (containing errors and old information), so there's definitely room for improvement for Nokia... -- 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] Can a USB modem be attached to N800?
On Sun, 2007-02-11 at 14:18 +0530, mayank jain wrote: On 2/11/07, Andrew J. Barr [EMAIL PROTECTED] wrote: On Sun, 2007-02-11 at 00:27 +0530, mayank jain wrote: Hi guys, I recently found that an ISP - Reliance Telecom here provides a USB modem, which uses CDMA technology for establishing a dial-up connection. This modem works perfectly with a Linux based machine. Device details at http://www.reliancecommunications.co.in/Communications/Netconnect/netconnect_hotnew.html Look for Reliance Netconnect USB Modem. Is it possible that this modem can be attached to N800 used for internet? Because if this is so, internet would be available to my device from almost anywhere - Wifi or no Wifi. You would want to find some kind of Bluetooth device for this. This works fine with the Nokia tablets. The 770 had limited support for USB host mode but AFAIK the N800 doesn't seem to have this feature. No one has tried it yet, at least ;) Oh, I just saw the thread mentioning 'injecting power into USB - this modem needs 5V/500ma, from USB - So i dont think this would be possible... It would be horribly unwieldy, you'd need a power injector device as well as a USB hub (or at least some kind of adapter). It would defeat the portable aspect of the Nokia tablets. This is why Bluetooth is ideal for this kind of situation; you'd have your cell phone in your pocket, your tablet in hand...pervasive Internet access almost anywhere. This is what I do, at least. What you describe I believe was at least possible on the 770, however. Right Andrew? :) Makuchaku http://www.makuchaku.info/blog ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] More missing source
Where can I find the source for libgst0.10-dsp 0.63-1 (http://repository.maemo.org/pool/bora/free/binary/libgst0.10-dsp_0.63-1_armel.deb) ? The corresponding source repository only has the 0.62-1 source. Also, this source package build-depends osso-dsp-headers-rx-34 (= 2006.40.1). Where can I find these? Paul ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Speed test with vfp (floating point) on N800
Hi folks, I was very interesseted in the floating point copro in the N800 cpu and did some tests with a progamm which calculates the mandelbrod set and outputs it via SDL. I put this program online on bomberman.garage.maemo.org. No installer, you have to run the benchmarks on xterm or via ssh (so did I). // Results of Mandelbrot set on N800 800x480 pixels, 100 interations // real -1 to 2 // imag -1.3 to 1.2 // dbl - uses doubles // flt - uses floats // vfp - compiled with -mfpu=vfp -mfloat-abi=softfp // All binarys are compiled with -O2 // Results with full PixelDraw and SDL_Update every pixel ./mandel_armel_dbl.bin - Time: 178.284 seconds ./mandel_armel_dbl_vfp.bin - Time: 151.816 seconds ./mandel_armel_flt.bin - Time: 169.486 seconds ./mandel_armel_flt_vfp.bin - Time: 152.148 seconds // Results with full PixelDraw and _NO_ SDL_Update. ./mandel_armel_dbl.bin - Time: 26.377 seconds ./mandel_armel_dbl_vfp.bin - Time: 1.808 seconds ./mandel_armel_flt.bin - Time: 19.813 seconds ./mandel_armel_flt_vfp.bin - Time: 1.709 seconds // Results without any Drawing ./mandel_armel_dbl.bin - Time: 26.525 seconds ./mandel_armel_dbl_vfp.bin - Time: 1.672 seconds ./mandel_armel_flt.bin - Time: 19.647 seconds ./mandel_armel_flt_vfp.bin - Time: 1.601 seconds // Results with full PixelDraw and SDL_Update only every column ./mandel_armel_dbl.bin - Time: 27.512 seconds ./mandel_armel_dbl_vfp.bin - Time: 2.447 seconds ./mandel_armel_flt.bin - Time: 20.689 seconds ./mandel_armel_flt_vfp.bin - Time: 2.451 seconds What could that mean? First, SDL_Update is _very_ expensive. In the first try, I call SDL_Update just for every Pixel (SDL_Update(screen,x,y,1,1) and it slows down execution about six times, the vfp about 80 times. So I think there must be a kind of sync inside the SDL_Update function. If I update only every column, the speed loss is only about 80%. Vfp float can give a speed increase about factor 10 and more. And there is not much difference between vfp float and double. -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] Dillo for N800/770
Anuj Verma (Kevin) wrote: I'll like to know if someone knows if there is a port for N800 or 770 available ? Dillo is (or at least the 0.8.6 source) GTK 1 based. There are some patches to get Dillo running on GTK2, but I think this is not stable yet. But I agree that a small lightweight HTML Browser would be nice. -- 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] Ogg Vorbis and the N800 - Theora encoding
After failing to combine theora and tremor I played with the n800 web cam. Theora encoding can be done by (as example) gst-launch-0.10 v4l2src ! ffmpegcolorspace ! video/x-raw-yuv,width=640,height=480,framerate=30/1 ! theoraenc bitrate=100 ! oggmux ! filesink location=target.ogg Well, playback is in fast forward mode then ;-) Do I need to add some kind of a 'timeoverlay' ? Raw video encoding (I420) is done by gst-launch-0.10 v4l2src ! ffmpegcolorspace ! video/x-raw-yuv,width=352,height=288,framerate=30/1 ! avimux ! filesink location=target.avi Cpu usage is below 45%. Regards Krischan pgp08s1TStqMY.pgp Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Speed test with vfp (floating point) on N800
On Sun, 11 Feb 2007 21:55:52 +0100 Klaus Rotter [EMAIL PROTECTED] wrote: Hi folks, I was very interesseted in the floating point copro in the N800 cpu and did some tests with a progamm which calculates the mandelbrod set and outputs it via SDL. I put this program online on bomberman.garage.maemo.org. No installer, you have to run the benchmarks on xterm or via ssh (so did I). It might interest you to know that I have an integer implementation of the mandelbrot set. It's not quite finished yet but, so its only available though subversion from the N770Demos project // Results of Mandelbrot set on N800 800x480 pixels, 100 interations // real -1 to 2 // imag -1.3 to 1.2 // dbl - uses doubles // flt - uses floats // vfp - compiled with -mfpu=vfp -mfloat-abi=softfp // All binarys are compiled with -O2 // Results with full PixelDraw and SDL_Update every pixel ./mandel_armel_dbl.bin - Time: 178.284 seconds ./mandel_armel_dbl_vfp.bin - Time: 151.816 seconds ./mandel_armel_flt.bin - Time: 169.486 seconds ./mandel_armel_flt_vfp.bin - Time: 152.148 seconds // Results with full PixelDraw and _NO_ SDL_Update. ./mandel_armel_dbl.bin - Time: 26.377 seconds ./mandel_armel_dbl_vfp.bin - Time: 1.808 seconds ./mandel_armel_flt.bin - Time: 19.813 seconds ./mandel_armel_flt_vfp.bin - Time: 1.709 seconds // Results without any Drawing ./mandel_armel_dbl.bin - Time: 26.525 seconds ./mandel_armel_dbl_vfp.bin - Time: 1.672 seconds ./mandel_armel_flt.bin - Time: 19.647 seconds ./mandel_armel_flt_vfp.bin - Time: 1.601 seconds // Results with full PixelDraw and SDL_Update only every column ./mandel_armel_dbl.bin - Time: 27.512 seconds ./mandel_armel_dbl_vfp.bin - Time: 2.447 seconds ./mandel_armel_flt.bin - Time: 20.689 seconds ./mandel_armel_flt_vfp.bin - Time: 2.451 seconds What could that mean? First, SDL_Update is _very_ expensive. In the first try, I call SDL_Update just for every Pixel (SDL_Update(screen,x,y,1,1) and it slows down execution about six times, the vfp about 80 times. So I think there must be a kind of sync inside the SDL_Update function. If I update only every column, the speed loss is only about 80%. When you do an update or flip the surface data is transferred to video memory (a slow and painful operation) This is also true even if SDL tells you that you got a HW surface. Unfortunately there are no sync, to the vertical blank... At least so have I been told. Vfp float can give a speed increase about factor 10 and more. And there is not much difference between vfp float and double. Humm the N800 even has a floating point unit... and its quite fast. I would say roughly as fast as an 770 using a long for the math. Only timed by counting aloud, and with a different setup -1, 1 and -1, 1 with 256 iterations. (The current subversion code uses long long math for that extra resolution, and it costs quite some speed :) -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 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] RFC 2833 (OOB DTMF tones) functionality (Nokia Devs please comment)
Quoting claw on the Gizmo forums thread: We are limited by the platform in this respect. The Nokia 770/N800 operating system is currently not capable of sending RFC 2833 signals. Nokia is aware of this shortcoming, but has not yet released an operating system version that can do this. (Sorry, but all we can do is ask Nokia to add this ability) ref: http://forum.gizmoproject.com/viewtopic.php?t=5451 http://www.faqs.org/rfcs/rfc2833.html This strikes me as kind of odd. The Maemo IM stack seems to allow for mixed video/audio/text, why is it that the Gizmo devs seem to think that the ITOS is incapable of this extra audio stream? I tried to bypass this missing functionality by generating some DTMF tones mp3s and playing them In-Band with the media player while Gizmo was placing a call. Unfortunately, Gizmo blocked the media player from playing the tones (while it did not block the little error tone that accompanied the error message telling me that I couldn't play my files). Even if it did work, I suspect that the iLBC codec would distort the DTMF signal horribly (thus the need for RFC 2833). Is it truly the situation that there is some missing link in the IM infrastructure on the ITOS that won't allow OOB DTMF? Is Gizmo or Media Player misusing the audio device such that they are blocking each other? I really think that this is important functionality for users as it pretty much blocks anyone from retrieving voicemail or using automated attendants. Thanks /Mike ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Some Questions on the N800 OS Imageg
All, does the OS for the N800 have a configurable firewall included in the OS image (e.g. iptables?). If so, are there any instructions on how to get it running? I am familiar with IPtables on Redhat LInux. Also, has anyone written a dynamic dns client to run on the N800 along the lines of the following Microsoft Windows client: http://www.dyndns.com/support/clients/ or the following Linux client: http://www.dyndns.com/support/clients/unix.html ? The above Linux client is written in Perl and I wonder if it is worthwhile to translate the app to Python assuming that is possible? Best Regards, John Holmblad ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Some Questions on the N800 OS Imageg
On Sun, 2007-02-11 at 20:31 -0500, Acadia Secure Networks wrote: All, does the OS for the N800 have a configurable firewall included in the OS image (e.g. iptables?). iptables is _the_ firewall for modern Linux (e.g. 2.4 and later). There isn't anything else that I am aware of. If so, are there any instructions on how to get it running? I am familiar with IPtables on Redhat LInux. If iptables isn't included in the Nokia kernel you can build your own with IPtables. Custom kernels are documented on the Maemo wiki. Also, has anyone written a dynamic dns client to run on the N800 along the lines of the following Microsoft Windows client: http://www.dyndns.com/support/clients/ or the following Linux client: http://www.dyndns.com/support/clients/unix.html ? The above Linux client is written in Perl and I wonder if it is worthwhile to translate the app to Python assuming that is possible? If I were you I'd find a DynDNS client written in C. It would be more easily portable. Any client written for Linux/POSIX in C should have no trouble running on the N800. IIRC I use ez-ipupdate for my personal server. Best Regards, John Holmblad ___ 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] Ogg Vorbis and the N800 - Theora encoding
2007/2/11, Krischan Keitsch [EMAIL PROTECTED]: After failing to combine theora and tremor I played with the n800 web cam. Theora encoding can be done by (as example) gst-launch-0.10 v4l2src ! ffmpegcolorspace ! video/x-raw-yuv,width=640,height=480,framerate=30/1 ! theoraenc bitrate=100 ! oggmux ! filesink location=target.ogg You might want to limit the framerate, at least if you plan on playing it back on the N800... ;) Well, playback is in fast forward mode then ;-) Do I need to add some kind of a 'timeoverlay' ? My guess would be that at that size and framerate the encoding is not keeping up with the stream. Do you see this with say [EMAIL PROTECTED] -- 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
