nanogui: mouse driver


Previous by date: 29 Jun 2001 19:49:16 -0000 Blocking mode operation for Microwindows/Win32 API, KIM,KYOUNG-IL (HP-Cupertino,ex1)
Next by date: 29 Jun 2001 19:49:16 -0000 Re: mouse driver, Jordan Crouse
Previous in thread: 29 Jun 2001 19:49:16 -0000 Re: mouse driver, Jordan Crouse
Next in thread: 29 Jun 2001 19:49:16 -0000 Re: mouse driver, Jordan Crouse

Subject: Re: [nanogui] mouse driver
From: MagnaSygg Technical Support ####@####.####
Date: 29 Jun 2001 19:49:16 -0000
Message-Id: <005401c100d4$342fd020$808210ac@swbell.net>

OK, I'm not a device driver writer, but the way it seems to me, is that
since
the kernel is taking the connection from (in my case the brain dead
connection)
and putting the data into /dev/mouse(?), then if I am using a PS2 type
device, I shouldn't need GPM to translate, and it just adds a layer of
unnecessary software. Is this true? What am I missing here?
Jeffrey

> You are confusing the job of the kernel and the job of the userland
> applications.  The kernel exists only as a service, no more no less.  Its
job
> is to actually read the PS2 port (or USB, or serial or direct connection
to
> the brain stem) and turn it into a recognizable set of data that can be
read
> by other programs.  The kernel provides this data in a handy set of device
> files which can be read or ignored as the case may be.
> Jordan
>
>



Previous by date: 29 Jun 2001 19:49:16 -0000 Blocking mode operation for Microwindows/Win32 API, KIM,KYOUNG-IL (HP-Cupertino,ex1)
Next by date: 29 Jun 2001 19:49:16 -0000 Re: mouse driver, Jordan Crouse
Previous in thread: 29 Jun 2001 19:49:16 -0000 Re: mouse driver, Jordan Crouse
Next in thread: 29 Jun 2001 19:49:16 -0000 Re: mouse driver, Jordan Crouse


Powered by ezmlm-browse 0.20.