nanogui: Thread: VNC Server for Nanox

I am looking for a port of VNC server for Nanox. Has anyone come across
a port of VNC server for Nanox?

Pete

Pete Klemm wrote:

> I am looking for a port of VNC server for Nanox. Has anyone come across
> a port of VNC server for Nanox?

Search the archives.  I sent in a patch along with some minimal docs.

--Yan

I now have a TightVNC Client on my PC with the nano-X remote
frame buffer and I can click the mouse in that window and see that
the mouse event is recognized on the remote system, but I just get
a black box in the TightVNC window.

Any thoughts and/or suggestions?

Also, is it possible to make the 320x240 window display larger
using the scaling? I tried 2 to 1 but the window stayed the same
size and 1 to 2 made it half the size.

Pete
yan seiner wrote:

> Pete Klemm wrote:
>
>> I am looking for a port of VNC server for Nanox. Has anyone come across
>> a port of VNC server for Nanox?
>
>
> Search the archives.  I sent in a patch along with some minimal docs.
>

Pete Klemm wrote:

> I now have a TightVNC Client on my PC with the nano-X remote
> frame buffer and I can click the mouse in that window and see that
> the mouse event is recognized on the remote system, but I just get
> a black box in the TightVNC window.
>
> Any thoughts and/or suggestions?

Oh, well, yes...

AFAICT, VNC needs either X running to provide a virtual framebuffer, or 
a physical framebuffer....

I tried using the kernel virtual framebuffer, but basically it is just a 
graphical bitbucket.

If you're a framebuffer hacker I am told it is not difficult to 
implement a full virtual framebuffer in the kernel... But I looked at 
the code and it was not at all obvious to me what was going on.  
Briefly, you have to allocate some real memory, and then set up the 
frambuffer functions accordingly.  We ended up not using nano-X, so I 
dropped the whole thing.

>
> Also, is it possible to make the 320x240 window display larger
> using the scaling? I tried 2 to 1 but the window stayed the same
> size and 1 to 2 made it half the size.

Not sure what you mean.  I don't think VNC allows you to zoom; I could 
be wrong....

--Yan

Hi Yan,
> If you're a framebuffer hacker I am told it is not difficult to 
> implement a full virtual framebuffer in the kernel... But I looked at 
> the code and it was not at all obvious to me what was going on.  
> Briefly, you have to allocate some real memory, and then set up the 
> frambuffer functions accordingly.  We ended up not using nano-X, so I 
> dropped the whole thing.
If you're able to bypass the NanoX Engine and still write to the 
framebuffer - Wouldn't that increase your performance ?

Regards,
Manav

yan seiner wrote:
> Pete Klemm wrote:
>
>> I now have a TightVNC Client on my PC with the nano-X remote
>> frame buffer and I can click the mouse in that window and see that
>> the mouse event is recognized on the remote system, but I just get
>> a black box in the TightVNC window.
>>
>> Any thoughts and/or suggestions?
>
> Oh, well, yes...
>
> AFAICT, VNC needs either X running to provide a virtual framebuffer, 
> or a physical framebuffer....
>
> I tried using the kernel virtual framebuffer, but basically it is just 
> a graphical bitbucket.
>
> If you're a framebuffer hacker I am told it is not difficult to 
> implement a full virtual framebuffer in the kernel... But I looked at 
> the code and it was not at all obvious to me what was going on.  
> Briefly, you have to allocate some real memory, and then set up the 
> frambuffer functions accordingly.  We ended up not using nano-X, so I 
> dropped the whole thing.
>
>>
>> Also, is it possible to make the 320x240 window display larger
>> using the scaling? I tried 2 to 1 but the window stayed the same
>> size and 1 to 2 made it half the size.
>
> Not sure what you mean.  I don't think VNC allows you to zoom; I could 
> be wrong....
>
> --Yan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>

I had the same problem.  With framebuffer you need to change the vncserver.c 
driver.  Here is the patch from my project.  The reason that you get a blank 
screen is that the nano-x screen type is not defined.  This patch may only 
work with the latest cvs of vncserver.

dave

----- Original Message ----- 
From: "Pete Klemm" ####@####.####
To: "yan seiner" ####@####.####
Cc: ####@####.####
Sent: Thursday, February 02, 2006 11:20 AM
Subject: Re: [nanogui] VNC Server for Nanox


>I now have a TightVNC Client on my PC with the nano-X remote
> frame buffer and I can click the mouse in that window and see that
> the mouse event is recognized on the remote system, but I just get
> a black box in the TightVNC window.
>
> Any thoughts and/or suggestions?
>
> Also, is it possible to make the 320x240 window display larger
> using the scaling? I tried 2 to 1 but the window stayed the same
> size and 1 to 2 made it half the size.
>
> Pete
> yan seiner wrote:
>
>> Pete Klemm wrote:
>>
>>> I am looking for a port of VNC server for Nanox. Has anyone come across
>>> a port of VNC server for Nanox?
>>
>>
>> Search the archives.  I sent in a patch along with some minimal docs.
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 

Dave Stuart wrote:

> I had the same problem.  With framebuffer you need to change the 
> vncserver.c driver.  Here is the patch from my project.  The reason 
> that you get a blank screen is that the nano-x screen type is not 
> defined.  This patch may only work with the latest cvs of vncserver.
>
> dave

Dave:

Do you still need a physical framebuffer with your patch?

If not, that would be really neat....  (I see all sorts of embedded app 
uses....)

--Yan

I am using a linux framebuffer device but it may work without one.  It just 
gets the information from nano-x for where the framebuffer is.

dave

----- Original Message ----- 
From: "yan seiner" ####@####.####
To: "Dave Stuart" ####@####.####
Cc: "Pete Klemm" ####@####.#### ####@####.####
Sent: Friday, February 03, 2006 1:39 PM
Subject: Re: [nanogui] VNC Server for Nanox


> Dave Stuart wrote:
>
>> I had the same problem.  With framebuffer you need to change the 
>> vncserver.c driver.  Here is the patch from my project.  The reason that 
>> you get a blank screen is that the nano-x screen type is not defined. 
>> This patch may only work with the latest cvs of vncserver.
>>
>> dave
>
> Dave:
>
> Do you still need a physical framebuffer with your patch?
>
> If not, that would be really neat....  (I see all sorts of embedded app 
> uses....)
>
> --Yan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 

Almost have the VNC server working!

I am using the latest CVS source for Nano-X and had to get the latest 
libvncserver as
the the RFB (remote frame buffer) member deferPtrUpdateTime was added after
version 0.7.1.

I can now start a TightVNC client session on my PC and display and 
interact with the
embedded linux system.

My only problems are:

    1 - The colors are bad. I use a custom pallette to give me more 
shades of blues
        and grays to make my GUI look nice but I am using 565 color 
mapping and
        this does not translate well to true color. Anyone have any 
hints here?
        I believe rfbServerFormat.trueColour needs to be set to FALSE 
and the
        rfbColourMap structure needs to be initialized with my pallette.

    2 - I also notice that if screen updates from my application stop 
the VNC client
        closes after about 20 seconds of inactivity. I have several 
screens that are
        static which do not update and that causes problems.


One good aspect of the TightVNC client is that I can scale the 320x240 
pixel window
to a 640x480 window which makes it much easier to see on my 1248x1024 
screen on my
PC.

Thanks for the help so far!

Pete