From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: kbdif Date: Wed, 13 Feb 2008 18:23:18 +0000 Message-ID: <20080213182318.GG4378@implementation.uk.xensource.com> References: <20080213174137.GF4378@implementation.uk.xensource.com> <8763wsenbm.fsf@pike.pond.sub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: <8763wsenbm.fsf@pike.pond.sub.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Markus Armbruster Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Markus Armbruster, le Wed 13 Feb 2008 19:14:05 +0100, a écrit : > Samuel Thibault writes: > > > Mmm, I can't find any event related to buttons in kbdif.h, was it just > > forgotten? > > > > Samuel > > XENKBD_TYPE_KEY, BTN_LEFT etc. Ah ok. Is there a reason for requiring fb and kbd to be initialised "in parallel"? I mean, hw/xenfb.c requires the kbd to be created, then the fb to be created, then the kbd to be initialized, then the fb to be initialized, then the kbd to be connected, then the fb to be connected. I would have thought that creating/initializing/connecting kbd first and then eventually fb would be allowed. Samuel