From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: kbdif Date: Thu, 14 Feb 2008 10:06:35 +0000 Message-ID: <20080214100635.GA4356@implementation.uk.xensource.com> References: <20080213174137.GF4378@implementation.uk.xensource.com> <8763wsenbm.fsf@pike.pond.sub.org> <20080213182318.GG4378@implementation.uk.xensource.com> <87hcgcaq03.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: <87hcgcaq03.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 Thu 14 Feb 2008 09:42:04 +0100, a écrit : > Samuel Thibault writes: > > 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. > > Any problems with this execution order? Yes: in the code I'm currently writing I have kbd_dev = init_kbdfront(nodename); fb_dev = init_fbfront(nodename, width, height, etc.); And this can't work currently, I instead have to run init_kbdfront and init_fbfront in threads so as to get them running in parallel. Samuel