Re: Crash in maemo-launcher

[Tapani Pälli]

ext Matt Hoosier wrote:
> [This message is the same as one that I posted, probably
> inappropriately, to maemo-users a few days ago. One responder there
> suggested that the crash seen below is from application-specific bugs,
> but I'm not so sure. A wide variety of very simple programs all fail
> with the same symptom.]
>
> Hi,
>
> I'm attempting to use maemo-launcher on some generic ARM embedded
> hardware which doesn't run the full Maemo library stack, and I've run
> into a couple of problems.
>
> First, there's the bug about gdk_display_close() which is mentioned in
> the README file, which results in the daemon process crashing as it
> tries to run the Gtk booster. The underlying GDK bug is fixed in
> upstream Gtk+ >= 2.10.
>
> There's also something strange happening to the forked child
> processes. The symptom when one executes the 'gtk-demo' program
> (relinked to export its 'main' symbol):
>
> ---8<---
>
> maemo-launcher: FcInit() took 0.006259 seconds
> maemo-launcher: gtk_parse_args() took 0.013969 seconds
> maemo-launcher: gtk_foo_get_type() functions took 0.027256 seconds
> maemo-launcher: init_gquarks() took 0.029781 seconds
> maemo-launcher: gtk_style_new() took 0.043788 seconds
> maemo-launcher: gtk_settings_get_default() took 0.044009 seconds
> maemo-launcher: gdk_display_close() took 0.044827 seconds
> maemo-launcher: invoke_recv_msg: b0070301
> maemo-launcher: invoke_send_msg: 600d
> maemo-launcher: invoke_recv_msg: 5a5e
> maemo-launcher: invoke_recv_msg: 001f
> maemo-launcher: invoke_recv_str: '/usr/local/bin/gtk-demo.launch'
> maemo-launcher: invoke_send_msg: 600d
> maemo-launcher: invoke_recv_msg: e8ec
> maemo-launcher: invoke_recv_msg: 001f
> maemo-launcher: invoke_recv_str: '/usr/local/bin/gtk-demo.launch'
> maemo-launcher: invoke_send_msg: 600d
> maemo-launcher: invoke_recv_msg: a465
> maemo-launcher: invoke_recv_msg: 0001
> maemo-launcher: invoke_recv_msg: 001f
> maemo-launcher: invoke_recv_str: '/usr/local/bin/gtk-demo.launch'
> maemo-launcher: invoke_send_msg: 600d
> maemo-launcher: invoke_recv_msg: a1ce
> maemo-launcher: invoke_recv_msg: 
> maemo-launcher: invoke_send_msg: 600d
> maemo-launcher: invoke_recv_msg: dead
> maemo-launcher: invoke_send_msg: 600d
> maemo-launcher: invoke_send_msg: 1d1d
> maemo-launcher: invoke_send_msg: 2ba7
> maemo-launcher: invoking '/usr/local/bin/gtk-demo.launch'
> maemo-launcher: env[0]='MANPATH=/usr/local/bin'
> maemo-launcher: env[1]='SBOX_DPKG_BUILDDEPS=yes'
> maemo-launcher: env[2]='_SBOX_USER_GROUPNAME=matt'
> maemo-launcher: env[3]='_SBOX_DIR=/scratchbox'
> maemo-launcher: env[4]='SHELL=/bin/sh'
> maemo-launcher: env[5]='TERM=xterm'
> maemo-launcher:
> env[6]='SBOX_REDIRECT_BINARIES=,/scratchbox/devkits/doctools/bin/install-info:/scratchbox/devkits/debian/bin/install-info,/usr/lib/dpkg/enoent:/scratchbox/devkits/debian/lib/dpkg/enoent'
>
> maemo-launcher: env[7]='TMPDIR=/var/tmp'
> maemo-launcher: env[8]='SBOX_PRELOAD=/scratchbox/tools/lib/libsb.so.0'
> maemo-launcher: env[9]='SBOX_LD_FAKE_NATIVE=yes'
> maemo-launcher: env[10]='SBRSH_RLIMIT_CORE=unlimited'
> maemo-launcher: env[11]='OLDPWD=/'
> maemo-launcher: env[12]='SBOX_READLINK_HACK=yes'
> maemo-launcher: env[13]='LC_ALL=C'
> maemo-launcher: env[14]='SBOX_UNAME_MACHINE=i686'
> maemo-launcher: env[15]='USER=matt'
> maemo-launcher:
> env[16]='LD_LIBRARY_PATH=/usr/local/lib:/lib:/usr/lib:/usr/local/lib:/usr/X11R6/lib'
>
> maemo-launcher: env[17]='LIBTOOL=/targets/links/arch_tools/bin/libtool'
> maemo-launcher: env[18]='CCACHE_DIR=/scratchbox/ccache/'
> maemo-launcher: env[19]='CXXFLAGS=-g'
> maemo-launcher: env[20]='_SBOX_SHELL_PID=11140'
> maemo-launcher: env[21]='SBOX_USE_CCACHE=yes'
> maemo-launcher:
> env[22]='PATH=/usr/local/bin:/scratchbox/devkits/perl/bin:/scratchbox/devkits/debian/bin:/scratchbox/devkits/doctools/bin:/scratchbox/tools/bin:/targets/links/arch_tools/bin:/host_usr/bin:/scratchbox/compilers/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/sbin:/usr/sbin'
>
> maemo-launcher: env[23]='PWD=/home/matt'
> maemo-launcher: env[24]='TZ=:/scratchbox/etc/localtime'
> maemo-launcher: env[25]='SBOX_DPKG_INST_ARCH=i386'
> maemo-launcher: env[26]='SHLVL=1'
> maemo-launcher: env[27]='HOME=/home/matt'
> maemo-launcher: env[28]='CFLAGS=-g'
> maemo-launcher:
> env[29]='SBOX_CPUTRANSPARENCY_LOG=/tmp/cputransp_matt.log'
> maemo-launcher: env[30]='LS_OPTIONS=--color=auto'
> maemo-launcher: env[31]='TMP=/var/tmp'
> maemo-launcher:
> env[32]='PYTHONPATH=/scratchbox/devkits/perl/lib/site-python:/scratchbox/devkits/debian/lib/site-python:/scratchbox/devkits/doctools/lib/site-python:'
>
> maemo-launcher: env[33]='LOGNAME=matt'
> maemo-launcher:
> env[34]='SBOX_REDIRECT_FROM_DIRS=/bin:/usr/bin:/usr/local/bin'
> maemo-launcher: env[35]='_SBOX_RESTART_FILE=/tmp/scratchbox-restart.matt'
> maemo-launcher:
> env[36]='SBOX_REDIRECT_TO_DIRS=/scratchbox/devkits/perl/bin:/scratchbox/devkits/debian/bin:/scratchbox/devkits/doctool

Re: Maemo roadmap, SDK improvements...

[Quim Gil]

On Tue, 2007-03-06 at 09:35 +0200, ext Henri Bergius wrote:

> See the editing view in http://www.nehmer.net/~bergie/maemo_wiki_edit_rfe.png

This looks good enough to be implemented. Thanks!

I only have comments about little details, let's continue this
conversation in https://garage.maemo.org/projects/maemo2midgard/ mailing
list.

Tommi, I will carry your suggestion about new fields there.

-- 
Quim Gil - http://maemo.org

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: N800 and USB host mode

[Quim Gil]

Please avoid crossposting between lists.

> On 3/5/07, Michael Wiktowy <[EMAIL PROTECTED]> wrote:
> > I didn't see USB host support on the roadmap so I don't hold out much
> > hope for the fixing of what I would consider a major regression of the

On Tue, 2007-03-06 at 16:26 -0500, ext Larry Battraw wrote:
> A
> roadmap/wishlist for changes to the platform is being created so this
> would definitely be a candidate for the list.

Just to clarify:

http://test.maemo.org/community/roadmap.html is far from reflecting
everything planned that could be public and also all the RFE well
argumented in the maemo community. It would have taken additional weeks
(months?) to release something like complete.

Hitting the Wishlist is almost only a matter of writing down a sensible
rationale. You can do it. In fact the community is the main source of
input for the Wishlist. 

Items appearing in the Wishlist are challenged internally against our
plans. Some wished features might be already in our plans and we will
move them to Roadmap unless we have a good reason to keep it in
Wishlist. Some wished features might get into our plans, or might be
pushed to short term releases. Some wished features might be totally out
of our current and mid-term plans, the idea is to identify them so the
community knows that they can take the lead on those without risk of
overlapping.

I will put "USB host mode" in the Wishlist. I plan to update the roadmap
page on Fridays (if we have stuff to update).  

-- 

Quim Gil - http://maemo.org

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: N800 and USB host mode

[Larry Battraw]

 I believe what you're looking for is here:
http://test.maemo.org/community/roadmap.html  There's a _huge_ list of
wishes for improvements elsewhere, but the roadmap is closer to
reality in terms of what might be implemented.  I believe the plan is
to flesh it out as far as who's running any particular project,
whether they're Nokia or not, current status, etc.  Searching the dev
list for roadmap will get you the details.

Larry

On 3/6/07, Michael Wiktowy <[EMAIL PROTECTED]> wrote:

On 3/6/07, Larry Battraw <[EMAIL PROTECTED]> wrote:
>   There was never a removal of the functionality since this is a new
> chipset and support for it was not available for it (AFAIK) in the
> kernel until recently.  I tried it out and it's pretty rough in (the
> current kernel version) 2.6.18; it would crash very quickly after
> booting up and I couldn't get it to actually do anything as far as
> host-mode is concerned.  So no conspiracy, just no working code :-)  I
> expect as support firms up we'll see it made available on the n800,
> particularly if people are interested enough to help out.  A
> roadmap/wishlist for changes to the platform is being created so this
> would definitely be a candidate for the list.

That makes complete sense, thanks for the info. I did notice another
related thread after I posted this giving me some hope.

The absence of facts invites speculation. I wasn't speculating that
there was a great Nokia conspiracy to deny us USB-hosting. I was
speculating that one of the reasons could have been legitimate
aversion to liability.

One thing that should go on this wishlist is a link from every item to
a separate page where there are reasons why a particular wishlist item
isn't implemented yet and specific requests for community help. I
think there is a lot of FOSS people not knowing what Nokia is already
doing in-house and not knowing what to sink their teeth into that will
end up being made redundant before they are done. A little note for
each item saying something like "Nokia internal is not working on this
currently" or " this work is being done upstream at this URL" or "this
work is waiting on x project to get their act in gear and support
function y".

I saw this new roadmap at one point but lost the link to it (the old
Maemo roadmap link is horribly outdated). Can someone point the way to
me?

/Mike

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: Bluetooth mouse.

[Larry Battraw]

On 3/5/07, Daniel Stone <[EMAIL PROTECTED]> wrote:

Try -mouse ps2,/dev/input/mice.  Of course, you still won't get a
cursor.

(OS2007 can find a mouse just fine, in theory, if you tell it to.
OS2006 can't.)

Cheers,
Daniel


 Thanks for the tip.  I've compiled xsetroot so I just use the
cursor_name to set one.  The options  you've given don't seem to work
so I guess there's more to it.  I've verified /dev/input/mice is
receiving mouse data.

Larry
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: N800 and USB host mode

[Michael Wiktowy]

On 3/6/07, Larry Battraw <[EMAIL PROTECTED]> wrote:

  There was never a removal of the functionality since this is a new
chipset and support for it was not available for it (AFAIK) in the
kernel until recently.  I tried it out and it's pretty rough in (the
current kernel version) 2.6.18; it would crash very quickly after
booting up and I couldn't get it to actually do anything as far as
host-mode is concerned.  So no conspiracy, just no working code :-)  I
expect as support firms up we'll see it made available on the n800,
particularly if people are interested enough to help out.  A
roadmap/wishlist for changes to the platform is being created so this
would definitely be a candidate for the list.


That makes complete sense, thanks for the info. I did notice another
related thread after I posted this giving me some hope.

The absence of facts invites speculation. I wasn't speculating that
there was a great Nokia conspiracy to deny us USB-hosting. I was
speculating that one of the reasons could have been legitimate
aversion to liability.

One thing that should go on this wishlist is a link from every item to
a separate page where there are reasons why a particular wishlist item
isn't implemented yet and specific requests for community help. I
think there is a lot of FOSS people not knowing what Nokia is already
doing in-house and not knowing what to sink their teeth into that will
end up being made redundant before they are done. A little note for
each item saying something like "Nokia internal is not working on this
currently" or " this work is being done upstream at this URL" or "this
work is waiting on x project to get their act in gear and support
function y".

I saw this new roadmap at one point but lost the link to it (the old
Maemo roadmap link is horribly outdated). Can someone point the way to
me?

/Mike
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: Bluetooth mouse.

[Anuj Verma (Kevin)]

On Tue, 06 Mar 2007 02:11:33 +0200, Daniel Stone wrote:

> Try -mouse ps2,/dev/input/mice.  Of course, you still won't get a
> cursor.
> 
> (OS2007 can find a mouse just fine, in theory, if you tell it to. OS2006
> can't.)

Would it be nice, an idea to add BT mouse support to OS2007 for future 
updates ? 

This can be just good enough functionality and cheap too for bed time 
browsing having N800 hung on a cradle. 

One other day I decided to "rm -rf /home/user" that exposed the mouse 
cursor on the screen. 

Kevin 

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: Issues with bora's dbus-python

[Henri Bergius]

On 3/2/07, Luciano M. Wolf <[EMAIL PROTECTED]> wrote:

Hi Henri,


Hi!


Thanks for this report. Right now we are migrating pymaemo svn to
garage.maemo.org. After this we will give special attention to all
bugs reported. Could you open a bug on pymaemo bugzilla[1] with a link
or some information about this patch for pyrex?


Here's the bug as reported by Simon McVittie (smcv on #dbus):

https://garage.maemo.org/tracker/index.php?func=detail&aid=561&group_id=40&atid=229


Luciano Wolf


/Henri

--
Henri Bergius
Motorcycle Adventures and Free Software
http://bergie.iki.fi/

Skype: henribergius
Jabber: [EMAIL PROTECTED]
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: N800 and USB host mode

[Larry Battraw]

On 3/5/07, Michael Wiktowy <[EMAIL PROTECTED]> wrote:

On 3/5/07, Larry Battraw <[EMAIL PROTECTED]> wrote:
>I understand
> that better support may be forthcoming, but that would be part of a
> new kernel or a back-port of the fixes.

The Nokia folks seem to be strangely silent on the whole USB host
thing. Maybe they are not wanting to implicate themselves in a power
injection hack that could damage your tablet. That would explain why
they took out the vital bits from the kernel.

I didn't see USB host support on the roadmap so I don't hold out much
hope for the fixing of what I would consider a major regression of the
N800 functionality vs. the 770. Nokia has surprised us with bigger
easter eggs though.

I would appreciate some clarification from Nokia whether this
functionality will return or if it was removed intentionally.

/Mike


 There was never a removal of the functionality since this is a new
chipset and support for it was not available for it (AFAIK) in the
kernel until recently.  I tried it out and it's pretty rough in (the
current kernel version) 2.6.18; it would crash very quickly after
booting up and I couldn't get it to actually do anything as far as
host-mode is concerned.  So no conspiracy, just no working code :-)  I
expect as support firms up we'll see it made available on the n800,
particularly if people are interested enough to help out.  A
roadmap/wishlist for changes to the platform is being created so this
would definitely be a candidate for the list.

Larry
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: GLIBC-2.4

[Amy Sockanathan]

I am building GLIBC-2.5 in the scratchbox and am getting the following
errors. Any idea what needs to be done.

make[3]: Leaving directory `/scratchbox/packages/glibc-2.5/glibc-2.5/elf'
gcc   -nostdlib -nostartfiles -r -o
/scratchbox/packages/glibc-2.5/glibc-build/elf/librtld.os
'-Wl,-(' 
/scratchbox/packages/glibc-2.5/glibc-build/elf/dl-allobjs.os/scratchbox/packages/glibc-
2.5/glibc-build/elf/rtld-libc.a -lgcc '-Wl,-)' \
 -Wl,-Map,/scratchbox/packages/glibc-2.5
/glibc-build/elf/librtld.os.map
gcc   -nostdlib -nostartfiles -shared   \
 -Wl,-z,combreloc -Wl,-z,relro -Wl,-z,defs -Wl,--verbose
2>&1 |\
 LC_ALL=C \
 sed -e '/^=/,/^=/!d;/^=/d'\
 -e 's/\. = 0 + SIZEOF_HEADERS;/& _begin = . -
SIZEOF_HEADERS;/' \
 > /scratchbox/packages/glibc-2.5/glibc-build/elf/ld.so.lds
gcc   -nostdlib -nostartfiles -shared -o
/scratchbox/packages/glibc-2.5/glibc-build/elf/ld.so
\
 -Wl,-z,combreloc -Wl,-z,relro -Wl,-z,defs \
 /scratchbox/packages/glibc-2.5/glibc-build/elf/librtld.os
-Wl,--version-script=/scratchbox/packages/glibc-2.5/glibc-build/ld.map
\
 -Wl,-soname=ld-linux.so.2 -T /scratchbox/packages/glibc-
2.5/glibc-build/elf/ld.so.lds
/scratchbox/packages/glibc-2.5/glibc-build/elf/librtld.os: In function
`print_statistics':
/scratchbox/packages/glibc-2.5/glibc-2.5/elf/rtld.c:2828: undefined
reference to `__stack_chk_fail_local'
/scratchbox/packages/glibc-2.5/glibc-build/elf/librtld.os: In function
`process_dl_debug':
/scratchbox/packages/glibc-2.5/glibc-2.5/elf/rtld.c:2464: undefined
reference to `__stack_chk_fail_local'
/scratchbox/packages/glibc-2.5/glibc-build/elf/librtld.os: In function
`process_envvars':
/scratchbox/packages/glibc-2.5/glibc-2.5/elf/rtld.c:2723: undefined
reference to `__stack_chk_fail_local'
/scratchbox/packages/glibc-2.5/glibc-build/elf/librtld.os: In function
`dl_main':
/scratchbox/packages/glibc-2.5/glibc-2.5/elf/rtld.c:2344: undefined
reference to `__stack_chk_fail_local'
/scratchbox/packages/glibc-2.5/glibc-build/elf/librtld.os: In function
`print_search_path':
/scratchbox/packages/glibc-2.5/glibc-2.5/elf/dl-load.c:1575: undefined
reference to `__stack_chk_fail_local'
/scratchbox/packages/glibc-2.5
/glibc-build/elf/librtld.os:/scratchbox/packages/glibc-2.5/glibc-2.5/elf/dl-
load.c:1795: more undefined references to `__stack_chk_fail_local' follow
collect2: ld returned 1 exit status
make[2]: *** [/scratchbox/packages/glibc-2.5/glibc-build/elf/ld.so] Error 1
make[2]: Leaving directory `/scratchbox/packages/glibc-2.5/glibc-2.5/elf'
make[1]: *** [elf/subdir_lib] Error 2
make[1]: Leaving directory `/scratchbox/packages/glibc-2.5/glibc-2.5'
make: *** [all] Error 2

Thanks
- Amy
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [Java] Mentor wanted for Summer of Code 2007 ;)

[koos vriezen]

Hi,

2007/3/6, Sebastian Mancke <[EMAIL PROTECTED]>:
[..]

I think java-gnome is the way to do java gui's on this small linux
devices, because it is really fast and offers the opportunity to
integrate with special gui extensions (e.g. hildon on maemo or libmokoui
on openmoko). But this may be my special taste and will be exchangeable,
if someone has a different task to solve.


My personal vote goes to SWT, works on top of j2me, gtk GUI implementation,
actively pushed by IBM and has loads of software already.
(likewise for AWT and Swing, but AWT is hardly used and really sucks and Swing
is way too heavy IMO).

Ah yes, that would also be a vote for j2me, also to have a standard commandline
for the jvm.

Koos
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Crash in maemo-launcher

[Matt Hoosier]

[This message is the same as one that I posted, probably
inappropriately, to maemo-users a few days ago. One responder there
suggested that the crash seen below is from application-specific bugs,
but I'm not so sure. A wide variety of very simple programs all fail
with the same symptom.]

Hi,

I'm attempting to use maemo-launcher on some generic ARM embedded
hardware which doesn't run the full Maemo library stack, and I've run
into a couple of problems.

First, there's the bug about gdk_display_close() which is mentioned in
the README file, which results in the daemon process crashing as it
tries to run the Gtk booster. The underlying GDK bug is fixed in
upstream Gtk+ >= 2.10.

There's also something strange happening to the forked child
processes. The symptom when one executes the 'gtk-demo' program
(relinked to export its 'main' symbol):

---8<---

maemo-launcher: FcInit() took 0.006259 seconds
maemo-launcher: gtk_parse_args() took 0.013969 seconds
maemo-launcher: gtk_foo_get_type() functions took 0.027256 seconds
maemo-launcher: init_gquarks() took 0.029781 seconds
maemo-launcher: gtk_style_new() took 0.043788 seconds
maemo-launcher: gtk_settings_get_default() took 0.044009 seconds
maemo-launcher: gdk_display_close() took 0.044827 seconds
maemo-launcher: invoke_recv_msg: b0070301
maemo-launcher: invoke_send_msg: 600d
maemo-launcher: invoke_recv_msg: 5a5e
maemo-launcher: invoke_recv_msg: 001f
maemo-launcher: invoke_recv_str: '/usr/local/bin/gtk-demo.launch'
maemo-launcher: invoke_send_msg: 600d
maemo-launcher: invoke_recv_msg: e8ec
maemo-launcher: invoke_recv_msg: 001f
maemo-launcher: invoke_recv_str: '/usr/local/bin/gtk-demo.launch'
maemo-launcher: invoke_send_msg: 600d
maemo-launcher: invoke_recv_msg: a465
maemo-launcher: invoke_recv_msg: 0001
maemo-launcher: invoke_recv_msg: 001f
maemo-launcher: invoke_recv_str: '/usr/local/bin/gtk-demo.launch'
maemo-launcher: invoke_send_msg: 600d
maemo-launcher: invoke_recv_msg: a1ce
maemo-launcher: invoke_recv_msg: 
maemo-launcher: invoke_send_msg: 600d
maemo-launcher: invoke_recv_msg: dead
maemo-launcher: invoke_send_msg: 600d
maemo-launcher: invoke_send_msg: 1d1d
maemo-launcher: invoke_send_msg: 2ba7
maemo-launcher: invoking '/usr/local/bin/gtk-demo.launch'
maemo-launcher: env[0]='MANPATH=/usr/local/bin'
maemo-launcher: env[1]='SBOX_DPKG_BUILDDEPS=yes'
maemo-launcher: env[2]='_SBOX_USER_GROUPNAME=matt'
maemo-launcher: env[3]='_SBOX_DIR=/scratchbox'
maemo-launcher: env[4]='SHELL=/bin/sh'
maemo-launcher: env[5]='TERM=xterm'
maemo-launcher:
env[6]='SBOX_REDIRECT_BINARIES=,/scratchbox/devkits/doctools/bin/install-info:/scratchbox/devkits/debian/bin/install-info,/usr/lib/dpkg/enoent:/scratchbox/devkits/debian/lib/dpkg/enoent'
maemo-launcher: env[7]='TMPDIR=/var/tmp'
maemo-launcher: env[8]='SBOX_PRELOAD=/scratchbox/tools/lib/libsb.so.0'
maemo-launcher: env[9]='SBOX_LD_FAKE_NATIVE=yes'
maemo-launcher: env[10]='SBRSH_RLIMIT_CORE=unlimited'
maemo-launcher: env[11]='OLDPWD=/'
maemo-launcher: env[12]='SBOX_READLINK_HACK=yes'
maemo-launcher: env[13]='LC_ALL=C'
maemo-launcher: env[14]='SBOX_UNAME_MACHINE=i686'
maemo-launcher: env[15]='USER=matt'
maemo-launcher:
env[16]='LD_LIBRARY_PATH=/usr/local/lib:/lib:/usr/lib:/usr/local/lib:/usr/X11R6/lib'
maemo-launcher: env[17]='LIBTOOL=/targets/links/arch_tools/bin/libtool'
maemo-launcher: env[18]='CCACHE_DIR=/scratchbox/ccache/'
maemo-launcher: env[19]='CXXFLAGS=-g'
maemo-launcher: env[20]='_SBOX_SHELL_PID=11140'
maemo-launcher: env[21]='SBOX_USE_CCACHE=yes'
maemo-launcher:
env[22]='PATH=/usr/local/bin:/scratchbox/devkits/perl/bin:/scratchbox/devkits/debian/bin:/scratchbox/devkits/doctools/bin:/scratchbox/tools/bin:/targets/links/arch_tools/bin:/host_usr/bin:/scratchbox/compilers/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/sbin:/usr/sbin'
maemo-launcher: env[23]='PWD=/home/matt'
maemo-launcher: env[24]='TZ=:/scratchbox/etc/localtime'
maemo-launcher: env[25]='SBOX_DPKG_INST_ARCH=i386'
maemo-launcher: env[26]='SHLVL=1'
maemo-launcher: env[27]='HOME=/home/matt'
maemo-launcher: env[28]='CFLAGS=-g'
maemo-launcher: env[29]='SBOX_CPUTRANSPARENCY_LOG=/tmp/cputransp_matt.log'
maemo-launcher: env[30]='LS_OPTIONS=--color=auto'
maemo-launcher: env[31]='TMP=/var/tmp'
maemo-launcher:
env[32]='PYTHONPATH=/scratchbox/devkits/perl/lib/site-python:/scratchbox/devkits/debian/lib/site-python:/scratchbox/devkits/doctools/lib/site-python:'
maemo-launcher: env[33]='LOGNAME=matt'
maemo-launcher: env[34]='SBOX_REDIRECT_FROM_DIRS=/bin:/usr/bin:/usr/local/bin'
maemo-launcher: env[35]='_SBOX_RESTART_FILE=/tmp/scratchbox-restart.matt'
maemo-launcher:
env[36]='SBOX_REDIRECT_TO_DIRS=/scratchbox/devkits/perl/bin:/scratchbox/devkits/debian/bin:/scratchbox/devkits/doctools/bin::/scratchbox/tools/bin:/targets/links/arch_tools/bin:/scratchbox/compilers/bin'
maemo-launcher: env[37]='PKG_CONFIG_PATH=/usr/local/lib/pkgconfig'
maemo-launcher: env[38]='LESSOPEN=|/scratchbox/tools/bin/lesspipe.

Re: Maemo roadmap, SDK improvements...

[Tommi Komulainen]

On Tue, 2007-03-06 at 08:06 +0200, ext Quim Gil wrote:
> - Full description

> - Discussion (relevant links to mailing list posts and/or wiki-style
> discussion here, not to mess with the previous fields).

I'd like to see Rationale and Use cases, and possibly Scope (what's in,
what's out) somewhere. Thinking of those usually helps to formulate
proposals better than just 'because I want it' handwaving.


-- 
Tommi Komulainen<[EMAIL PROTECTED]>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Detecting N800 camera position

[Edgard Lima]

However how to I flip the video manually using gstreamer?
  


http://webcvs.freedesktop.org/gstreamer/gst-plugins-good/tests/icles/v4l2src-test.c?revision=1.8&view=markup

search in the code for "flip"

BR
Edgard

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

WLAN Scanning problem

[kalle ahokangas]

Hi,

I have problem when I perform WLAN scanning when internet connection is on.
I'm still trying to do an application which scans APs RSSI info and then
send them to server via internet connection.
This requires that I have internet connection on (wlan is associated with
AP) at the same time I'm performing scanning, but when the connection is on
RSSI information doesn't update properly.
Only the associated AP RSSI information is uptated!

I have investigated the driver code and debugged the situation and I get
error code -22 from sm_drv_set_scan method from sm_drv_ioctl_umac.c at line
1135:

/* And finally we send the scan request */
ret = sm_drv_oid_set(dev, DOT11_OID_SCAN, (void*)&scan, sizeof(int16_t));

(Do you know where I can find expanations for those errors?)

I hope you can understand the situation. The question is:

Connection manager scans properly even if the internet connection is on so I
assume that this scenario is doable.
What  I have to do to to get the scanning to work while internet connection
is on? Do I have to give some parameters to the driver or what?

You can see that I'm lost here but I'd appreciate your help very much again.

- Kalle
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Maemo at CeBIT 2007?

[Hanno Zulla]

Hi,

will there be Maemo-related items at the CeBIT in Hannover? I'd like to
make sure I see those exhibits that are there this year.

Regards,

Hanno
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [Java] Mentor wanted for Summer of Code 2007 ;)

[Quim Gil]

On Tue, 2007-03-06 at 08:13 +0100, ext Clemens Eisserer wrote:
> If somebody says "I would do this and that" and somebody else reads
> "yeah, I always wanted to see that happen" I see way better chances.

Well yes, you have your point.

> I wonder a bit whats the problem. 

Me too. This list alone gets so many ideas and requests during the year,
and many of them can be done by skilled people with time available.
Where are they now?

> If only a few ideas are rising,
> maybe only a few slots are assigned to maemo.

Even worse: if only a few ideas are rising Google might not approve us
as attractive SoC organization, or we might even decide not to apply at
all.

>  I think this is a great
> opportunity for maemo, almost without downsides.

This is what I thought when the proposal was made.

I hope it's clear that in this case Nokia cannot have the initiative
providing ideas and mentors. 

-- 
Quim Gil - http://maemo.org

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [Java] Mentor wanted for Summer of Code 2007 ;)

[Sebastian Mancke]

Hi,

Johannes Eickhold schrieb:
> On Mon, 2007-03-05 at 20:26 +0100, Clemens Eisserer wrote:
>> I wonder wether anybody would be willed to mentor me at Google's
>> Summer of Code 2007.
> 
> Hi Clemens,
> 
> I would like to support your effort as a mentor. But currently I don't
> know what is needed to be accepted as a mentor and what the process to
> apply as a mentor would be. If anybody on this list is able to clarify
> the situation, please feel free to do so!
> 
> Would it make sense to ask on sun's Java phoneME forum for support and
> possibly another mentor, too?
> 
> I'm also interested in broader feedback and opinions from the list about
> Java integration into maemo. 
Me too. Based on time, the really work on JaLiMo will start in April, so
this month may be the right time for ideas and wishes.

> It seems at least three possibilities are
> currently considered by different people.
> 
> 1. jamvm + classpath
> 2. cacaovm + classpath + java-gnome (jalimo by Sebastian Mancke)
> 3. sun's phoneME advanced
well, we should try to integrate any efforts.

1. vs. 2.
Between 1. an 2., IMO there is no big difference. The jamvm also runs
out of the box with the JaLiMo libraries. cacao is 3 times faster than
the jamvm, but has a 2.5 sec longer start up time. The classpath version
in 1. is 0.91, matching the gtk libraries of maemo. I, for now, have
tried to get the recent versions running, with the lack of AWT.

I think java-gnome is the way to do java gui's on this small linux
devices, because it is really fast and offers the opportunity to
integrate with special gui extensions (e.g. hildon on maemo or libmokoui
on openmoko). But this may be my special taste and will be exchangeable,
if someone has a different task to solve.

The difference from JaLiMo to 1. is that we try not only to build some
packages once. We have the goal to let a platform evolve, beyond the
runtime, which solves recurring problems every java developer hit when
he/she targets an linux embedded platform. Before n770, I did java on
Yopy and IPAQ/familiar with the same problems:
- Get a fast GUI working
- Desktop integration
- Packaging
- menu integration
- Configuration integration
- Connectivity to back-end-services

So we are trying to: Integrate once, write once, run on every mobile
linux device.

2. vs. 3.
In 3., I see two very different conceptual approaches:
- J2ME CDC (Minimal Java, no reflection, no JNI, MIDP 2.0)
This one is different to JaLiMo.
- J2ME CLDC (Java 1.3.1, AWT)
This second one has the same objective, but a completely other solution.

You should take a look at MIDPath (http://midpath.thenesis.org), which
already has a running MIDP (based on phoneME) on top of GNU Classpath,
Cacao, Kaffe and JamVM with different back end libraries. MIDPath would
perfectly fit with JaLiMo since it uses the same runtime.


-Sebastian


-- 
tarent Gesellschaft für Softwareentwicklung und IT-Beratung mbH

Heilsbachstr. 24, 53123 Bonn| Poststr. 4-5, 10178 Berlin
fon: +49(228) / 52675-0 | fon: +49(30) / 27594853
fax: +49(228) / 52675-25| fax: +49(30) / 78709617
durchwahl: +49(228) / 52675-17  | mobil: +49(171) / 7673249

Geschäftsführer:
Boris Esser, Elmar Geese, Thomas Müller-Ackermann
HRB AG Bonn 5168
Ust-ID: DE122264941
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: Wiki status

[Michael Dominic Kostrzewa]

On Tue, Mar 06, 2007 at 07:45:46AM +0200, Quim Gil wrote:
> The first question to answer is whether official documentation (like I
> assume you are going to publish) should go to the wiki at all. Instead,
> we could have it well sorted in a place intended for stable
> documentation.
> 
> Now with Midgard, creating and editing pages is as easy as with a wiki,
> so it is more a matter of permissions and ability to use HTML directly.
> 
> I would recommend you to request Ferenc editing permissions and create
> pages under the Developers section. We can organize the pages later on,
> if needed. The same would apply to anybody writing official
> documentation in maemo.org.
> 
> Unless Ferenc has a different opinion  :)  since we are still setting
> procedures about how the new website will be maintained. But this topic
> is more on-topic at https://garage.maemo.org/projects/maemo2midgard/

Sounds all good to me.

-- 
MDK

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers