Support for frame buffer in N800

2007-03-21 Thread Sampath Goud

Hi,

I want to know if there is frame buffer support in N800.
I have written a simple application (drawing a pixel) on frame buffer and
tried to execute it on N800 in root mode.
But it prompts the message permission denied.
Please let me know if there is support for frame buffer in N800. If there is
support then how can I use it?

Thanks and Regards,
Sampath
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Handling asynchronous events in maemo

2007-02-23 Thread Sampath Goud

Hi,

Can somebody let me know if there are any ways to handle asynchronous events
in Maemo.
I am looking for Event driven mechanism (observer design pattern) and not
polling.
I want to know which libraries support this method.

Thanks and Regards,
Sampath
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


[maemo-developers] Can we launch Xephyr from different clients connected to a server

2007-01-31 Thread Sampath Goud

Hi,

I am working for Nokia, Bangalore.

I have made a linux PC as server and connected to this server using
different logins from different PCs (running windows through Cygwin).

I need clarifications for below two problems:

1:
---
I tried to launch the Xephyr using # ./start-xephyr.sh  command. I am
able to launch for the first login. Keeping this Xephyr active, When I try
to launch it from a different login from a different PC I am getting the
below error:


Fatal server error:
Server is already active for display 2
   If this server is no longer running, remove /tmp/.X2-lock
   and start again.

If I close the first instance of xephyr and try again, I am able to launch
it from the second login.

Is there any way to launch xephyr from different clients at same time?

2:
---
I tried to launch the Xephyr using # ./start-xephyr.sh  command. I am
able to launch for the first login. Then I tried to start the Maemo UI in
the Xephyr window using the command [sbox-SDK_PC: ~] 
af-sb-init.shstart. The Maemo window started without any problems.
I stopped the Maemo UI [sbox-SDK_PC: ~]  af-sb-init.sh stop and closed
the Xephyr window.

From a different client I launched Xephyr and tried to start the Maemo UI

using the command [sbox-SDK_PC: ~]  af-sb-init.sh start. Maemo Ui is not
started and I am getting the below messages:


[sbox-SDK_PC: ~]  af-sb-init.sh start
/usr/bin/af-sb-init.sh: line 1: export: `bus:': not a valid identifier
/usr/bin/af-sb-init.sh: line 1: export: `/tmp/session_bus_socket:': not a
valid identifier
Note: For remote X connections DISPLAY should contain hostname!
Sample files present.
DBUS system bus is already running, doing nothing
Starting D-BUS session bus daemon
/usr/bin/af-sb-init.sh: line 1: export: `bus:': not a valid identifier
/usr/bin/af-sb-init.sh: line 1: export: `/tmp/session_bus_socket:': not a
valid identifier
/etc/init.d/maemo-launcher: line 1: export: `bus:': not a valid identifier
/etc/init.d/maemo-launcher: line 1: export: `/tmp/session_bus_socket:': not
a va lid identifier
Starting Maemo Launcher: maemo-launchermaemo-launcher: died binding to
invoker s ocket
start failed.
Starting Sapwood image server
Starting Matchbox window manager
Starting clipboard-manager
Starting Keyboard
Starting MAEMO AF Desktop
[sbox-SDK_PC: ~]  sapwood-server[24879]: GLIB INFO default - server started


After this I am not able to start maemo UI from the first login also. I have
to restart the Server to start Maemo UI.

Can somebody help me in solving this.

Thanks and Regards,
Sampath
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


Re: [maemo-developers] Can we launch Xephyr from different clients connected to a server

2007-01-31 Thread Sampath Goud

Hi Levi,

Thanks for the reply.
Please see below for my response.

Thanks and Regards,
Sampath

On 1/31/07, Levi Bard  [EMAIL PROTECTED] wrote:


 1:
  ---
  I tried to launch the Xephyr using # ./start- xephyr.sh  command. I
am
 able to launch for the first login. Keeping this Xephyr active, When I
try
 to launch it from a different login from a different PC I am getting the
 below error:

 
 Fatal server error:
 Server is already active for display 2
 If this server is no longer running, remove /tmp/.X2-lock
 and start again.
 
 If I close the first instance of xephyr and try again, I am able to
launch
 it from the second login.

 Is there any way to launch xephyr from different clients at same time?

I would suggest creating another xephyr script that launches xephyr on
a different display ( exec ${prefix}/bin/Xephyr :3 -host-cursor
-screen 800x480x16 0dpi 96 -ac ), or alternatively write a script that
takes the display as a parameter.



Sampath: This works and  I am able to launch Xephyr parallely from different
logins in different PCs.


2:
 ---
 I tried to launch the Xephyr using # ./start- xephyr.sh  command. I
am
 able to launch for the first login. Then I tried to start the Maemo UI
in
 the Xephyr window using the command [sbox-SDK_PC: ~]  af-sb-init.sh
 start. The Maemo window started without any problems.
 I stopped the Maemo UI [sbox-SDK_PC: ~]  af-sb-init.sh stop and
closed
 the Xephyr window.
 From a different client I launched Xephyr and tried to start the Maemo
UI
 using the command [sbox-SDK_PC: ~]  af-sb-init.sh start. Maemo Ui is
not
 started and I am getting the below messages:

After starting xephyr, did you set DISPLAY to :2 in your shell?



Sampath:
Yes, I did set the DISPLAY to :2.
Even with the solution to first problem, this problem still exists. I am
getting the same errors. That is...

When I try to start Maemo UI from the second login, I am getting the below
shown messages:

[sbox-SDK_PCSAM: ~]  af-sb-init.sh start
Note: For remote X connections DISPLAY should contain hostname!
Sample files present.
Starting DBUS system bus
Starting D-BUS session bus daemon
Starting Maemo Launcher: maemo-launchermaemo-launcher: died binding to
invoker socket
start failed.
Starting Sapwood image server
Starting Matchbox window manager
sapwood-server[9332]: GLIB INFO default - server started
Starting clipboard-manager
Starting Keyboard
Starting MAEMO AF Desktop


After that I am not even able to launch Maemo UI on first login also (which
was working initially).
I am getting below messages in the first login when I try to launch Maemo
UI:


[sbox-SDK_PC: ~]  af-sb-init.sh start
/usr/bin/af-sb-init.sh: line 1: export: `bus:': not a valid identifier
/usr/bin/af-sb-init.sh: line 1: export: `/tmp/session_bus_socket:': not a
valid identifier
Note: For remote X connections DISPLAY should contain hostname!
Sample files present.
Starting DBUS system bus
Starting D-BUS session bus daemon
/usr/bin/af-sb-init.sh: line 1: export: `bus:': not a valid identifier
/usr/bin/af-sb-init.sh: line 1: export: `/tmp/session_bus_socket:': not a
valid identifier
/etc/init.d/maemo-launcher: line 1: export: `bus:': not a valid identifier
/etc/init.d/maemo-launcher: line 1: export: `/tmp/session_bus_socket:': not
a valid identifier
Starting Maemo Launcher: maemo-launcher.
Starting Sapwood image server
Starting Matchbox window manager
Starting clipboard-manager
Starting Keyboard
maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'
Starting MAEMO AF Desktop
maemo-launcher: invoking '/usr/bin/maemo_af_desktop.launch'
[sbox-SDK_PC: ~]  sapwood-server[12935]: GLIB INFO default - server started
hildon-input-method[12959]: GLIB WARNING ** default - Could not initialize
osso from hildon-input-method
maemo-launcher: child (pid=12974) exited due to exit()=1
hildon-input-method[12959]: GLIB WARNING ** default - Could not register the
osso_hw_set_event_cb
hildon-input-method[12959]: GLIB MESSAGE default - keyboard up and running


I have to restart the server to make things work for the first login.

Please, let me know if there is any solution.

Thanks and regards,
Sampath


--

Just stop and take your secret journey, you will be a new box. --Leeta
http://www.gnu.org/philosophy/shouldbefree.html

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


[maemo-developers] maemo_af_desktop[7236]: We could not read lowmem page stats.

2007-01-08 Thread Sampath Goud

Hi,

I have created a simple SDL application (hellosdl), compiled and created a
.deb package in scratchbox. I started xephyr, and the GUI window opened
fine. But when I try to open my installed SDL application, I get a revolving
icon message hellosdl - loading and after few seconds it is lost and
nothing happens.
In scratchbox command prompt I get an error as below:
maemo_af_desktop[7236]: We could not read lowmem page stats.

When I run the same application in the 770, I get the same revolving icon
message hellosdl - loading and after few seconds it is lost and nothing
happens.

Please help me.

Thanks and Regards,
Sampath

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