From owner-freebsd-current Thu Nov 4 18:56:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 2916315801 for ; Thu, 4 Nov 1999 18:56:21 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id SAA50665; Thu, 4 Nov 1999 18:54:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911050254.SAA50665@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), Mike Smith Subject: Re: vga driver and signal In-reply-to: Your message of "Fri, 05 Nov 1999 13:18:20 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 18:54:11 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 05-Nov-99 Amancio Hasty wrote: > > Your idea sounds intriguing . How should we wired the KLD to > > the X server? or how will the KLD inform the X server that it > > has received a vertical retrace interrupt . > > It depends what you wanted to do, but you could have the X server feed the KLD > commands to do on a vert refresh, and when it happens the commands are executed > in kernel mode, which would save you a lot of time. > > Kind of complex though. Also the interrupt latency problem is still there. Not sure that this is as elegant as what you are suggesting , can the kernel schedule a user level routine to be executed when an interrupt occurs? I guess on Windoze land this is called a driver call-back. Just trying to prevent dragging the whole X server to the kernel -- Actually dragging the whole X server to the kernel is not a bad idea --- however it is something that I can not afford to do right now :( -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message