From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH] Paravirt framebuffer backend tools [2/5] Date: Tue, 05 Sep 2006 12:57:12 -0400 Message-ID: <44FDAC68.8050205@cs.utexas.edu> References: <20060904090150.GC4812@cam.ac.uk> <1157472715.7571.88.camel@aglarond.local> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1157472715.7571.88.camel@aglarond.local> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Katz Cc: aliguori , xen-devel , sos22@srcf.ucam.org, Markus Armbruster List-Id: xen-devel@lists.xenproject.org Jeremy Katz wrote: > On Mon, 2006-09-04 at 10:01 +0100, Steven Smith wrote: > >>> +CFLAGS += -g -Wall >>> >> You shouldn't need to add -g here; Rules.mk handles it for you if >> debug is set. >> > > *nod* -Wall gets set in Config.mk as well -- will nuke. > > >>> --- /dev/null Thu Jan 01 00:00:00 1970 +0000 >>> +++ b/tools/xenfb/keymapping.c Sat Sep 02 15:19:25 2006 -0400 >>> @@ -0,0 +1,141 @@ >>> +#include >>> +#include >>> +#include >>> + >>> +uint32_t gdk_linux_mapping[0x10000] = { >>> + [GDK_a] = KEY_A, >>> >> This is kind of ugly. Is there any chance it could be autogenerated? >> Also, where did 0x10000 come from? >> >> Also, depending on GTK just for the keymap table is a real pain. Or >> is it already required for libvncserver? >> > > libvncserver requires GTK. And I don't know that there's really any > good way to auto-generate it unfortunately. I somehow expect that > 0x10000 came from "it'll be big enough" but Anthony would have to > confirm :-) > That's the biggest that a GDK scan code can currently be. That way, we can use a simple indexed table. Regards, Anthony Liguori > The mappings are unfortunately a bit of a fact of life since we have to > convert from what the X layer gets to what the kernel expects. And the > two couldn't be farther from the same. And then it's even more fun when > toolkits get involved. >