nanogui: Thread: VNC with latest Git image of Nano-X


[<<] [<] Page 1 of 1 [>] [>>]
Subject: VNC with latest Git image of Nano-X
From: Pete Klemm ####@####.####
Date: 28 Jun 2012 16:38:40 -0000
Message-Id: <4FEC8877.3080805@esysr.com>

I am having an issue with VNC screen updates. Portions of
the screen that change are not updated properly unless I
force a refresh from the VNC client.

I am using the latest source from the git repository and
I am linked with the most recent Debian Squeeze stable
release of libvncserver-dev 0.9.7+b1.

This used to work fine, but I had to upgrade to the latest
git to support UTF-8 and now the VNC is broken.

Any thoughts where to look, libvnc or drivers/vncserver.c?

Anyone have this working?

I thought I could pull in the latest libvncserver source
(0.9.9) but I see a lot of "Fixme's" and commented out
code in drivers/vncserver.c so I suspect this is a Nano-X
issue.

Any input would be appreciated.

Pete
Subject: Re: [nanogui] VNC with latest Git image of Nano-X
From: Greg Haerr ####@####.####
Date: 5 Jul 2012 05:38:37 -0000
Message-Id: <7D934FC1-2A17-45EB-92E2-1752A2491C1D@censoft.com>

> I am using the latest source from the git repository and
> I am linked with the most recent Debian Squeeze stable
> release of libvncserver-dev 0.9.7+b1.
> 
> This used to work fine, but I had to upgrade to the latest
> git to support UTF-8 and now the VNC is broken.
> 
> Any thoughts where to look, libvnc or drivers/vncserver.c?
> 
> Anyone have this working?
> 
> I thought I could pull in the latest libvncserver source
> (0.9.9) but I see a lot of "Fixme's" and commented out
> code in drivers/vncserver.c so I suspect this is a Nano-X
> issue.

Pete - I had to comment out support for VNC server when porting
the 0.93 blit code.  The old code in vncserver.c needs to be 
changed to call the new-style blit routines in order to make
this work.  I didn't have a copy of libvncserver that I could compile
and link nano-X with without errors.  If you could get something
at least compiling and linking, I can help getting the blits re-wired.

The blit routines are defined in device.h:: struct SCREENDEVICE.  Which
one to call will depend on your hardware pixel format and the source
pixel format.

Regards,

Greg
Subject: Re: [nanogui] VNC with latest Git image of Nano-X
From: Pete Klemm ####@####.####
Date: 18 Sep 2012 16:43:05 -0000
Message-Id: <5058A493.30509@esysr.com>

On 7/5/2012 12:38 AM, Greg Haerr wrote:
>> I am using the latest source from the git repository and
>> I am linked with the most recent Debian Squeeze stable
>> release of libvncserver-dev 0.9.7+b1.
>>
>> This used to work fine, but I had to upgrade to the latest
>> git to support UTF-8 and now the VNC is broken.
>>
>> Any thoughts where to look, libvnc or drivers/vncserver.c?
>>
>> Anyone have this working?
>>
>> I thought I could pull in the latest libvncserver source
>> (0.9.9) but I see a lot of "Fixme's" and commented out
>> code in drivers/vncserver.c so I suspect this is a Nano-X
>> issue.
> Pete - I had to comment out support for VNC server when porting
> the 0.93 blit code.  The old code in vncserver.c needs to be
> changed to call the new-style blit routines in order to make
> this work.  I didn't have a copy of libvncserver that I could compile
> and link nano-X with without errors.  If you could get something
> at least compiling and linking, I can help getting the blits re-wired.
>
> The blit routines are defined in device.h:: struct SCREENDEVICE.  Which
> one to call will depend on your hardware pixel format and the source
> pixel format.
>
> Regards,
>
> Greg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
>
Sorry for the extremely long pause here. I was side tracked to another 
project for a couple months.

Anyway, here are the details of my build:

My target is a Marvell PXA320 (armv5tel) running Debian Squeeze. I am 
building natively with GCC 4.4.5.

I am using the following source (diff for microwin is attached):

micrown (Nano-X)
nxlib latest git source
LibVNCServer-0.9.9
freetype-2.4.8

I have diff files available, however my first attempt to send this
email was rejected as exceeding 3K bytes, so I am resending without 
them. The diffs contain changes to get VNC to link properly, but also 
some customization for my application (paths, no VNC passwd, version 
timestamp, UTF-8 support and debug messages)

VNC is connecting and mostly working. The issue I have is small screen 
image changes do not get updated. The only way to get those changes is 
to wait for a large change or hit the refresh button on the VNC client.

Any guidance here is appreciated. I am willing to do the grunt work, but 
don't have an idea where to start.

Thanks much,

Pete Klemm




Subject: Re: [nanogui] VNC with latest Git image of Nano-X
From: Greg Haerr ####@####.####
Date: 18 Sep 2012 18:57:07 -0000
Message-Id: <BABF9470-9036-4552-99F3-08E71600D1F9@censoft.com>

> 
> I am using the following source (diff for microwin is attached):
> 
> micrown (Nano-X)
> nxlib latest git source
> LibVNCServer-0.9.9
> freetype-2.4.8
> 
> The attached diffs contain changes to get VNC to link properly, but also some customization
> for my application (paths, no VNC passwd, version timestamp, UTF-8 support and debug messages)
> 
> VNC is connecting and mostly working. The issue I have is small screen image changes
> do not get updated. The only way to get those changes is to wait for a large change or
> hit the refresh button on the VNC client.

I assume you're running the latest (git) microwindows source.
Are you testing this on X11 or a framebuffer device?

If so, the reason that you're likely not getting screen updates is that
the new blit routines don't update automatically, they require a
call to the psd->Update() procedure with the coordinates of the
screen that have been modified.  If you look at some of the routines
in engine/convblit*.c, you'll see how this is used.

Thus, in your driver, after performing the draw code, you'll want to 
call psd->Update with the bounding rect of the areas modified.

There is the possibility this is not the issue, but this is definitely required
when using X11 or non-framebuffer due to the new drawing architecture with
backing store. I haven't looked at your changes yet, as I'm still buried at work.

Regards,

Greg
Subject: Re: [nanogui] VNC with latest Git image of Nano-X
From: Pete Klemm ####@####.####
Date: 18 Sep 2012 19:22:15 -0000
Message-Id: <5058C9DA.4070801@esysr.com>

On 9/18/2012 1:57 PM, Greg Haerr wrote:
>> I am using the following source (diff for microwin is attached):
>>
>> micrown (Nano-X)
>> nxlib latest git source
>> LibVNCServer-0.9.9
>> freetype-2.4.8
>>
>> The attached diffs contain changes to get VNC to link properly, but also some customization
>> for my application (paths, no VNC passwd, version timestamp, UTF-8 support and debug messages)
>>
>> VNC is connecting and mostly working. The issue I have is small screen image changes
>> do not get updated. The only way to get those changes is to wait for a large change or
>> hit the refresh button on the VNC client.
> I assume you're running the latest (git) microwindows source.
> Are you testing this on X11 or a framebuffer device?
>
> If so, the reason that you're likely not getting screen updates is that
> the new blit routines don't update automatically, they require a
> call to the psd->Update() procedure with the coordinates of the
> screen that have been modified.  If you look at some of the routines
> in engine/convblit*.c, you'll see how this is used.
>
> Thus, in your driver, after performing the draw code, you'll want to
> call psd->Update with the bounding rect of the areas modified.
>
> There is the possibility this is not the issue, but this is definitely required
> when using X11 or non-framebuffer due to the new drawing architecture with
> backing store. I haven't looked at your changes yet, as I'm still buried at work.
>
> Regards,
>
> Greg
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
>
I am using framebuffer. I'll let you know if calling psd->Update() helps.

Thanks,
Pete
[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.