using mouse input through resource manager interface

bridged with qdn.public.ddk.input
Post Reply
Guest

using mouse input through resource manager interface

Post by Guest » Thu Jul 26, 2001 10:44 pm

I have been playing around with using the input driver independent of
Photon. I'm targetting an x86 system with a PS/2 mouse. I start
devi-hirun with the following command: "devi-hirun -Pr ps2 mousedev &". I
then start my test application, which simply does an open(), a read(), and
a close() on /dev/devi/mouse0. It usually works the first time, and I am
able to see correct button and move events coming from the mouse. The
problem is that when I try to run my test again, I am unable to read
anything from the mouse. However, devi-hirun is still running at this
point and /dev/devi/mouse0 still exists. Is there some sort of reset
command which I need to issue to the mouse in order to use it again? Does
anyone have any ideas?

thanks
Charlie

Frank Liu

Re: using mouse input through resource manager interface

Post by Frank Liu » Tue Oct 09, 2001 4:26 am

have you had answer to this?
I am doing the same thing for my XFree86 X Window port.
After I start "devi-hirun -Pr ps2 mousedev &", I can see
the /dev/devi/mouse0, but the mouse doesnt work right,
if I move the mouse, the cursor/pointer on the screen will
jump around and then stick to the edge.
The only way I can get it to work is to attach a serial mouse
and then use the /dev/ser1 device. The funny thing is if I
start "devi-hirun -Pr msoft fd -d/dev/ser1 &", and let X window
use /dev/devi/mouse0, I will end up with the same problem as
the PS2 mouse. It looks like the "devi-hirun" is doing something.
Any help will be appreciated.
Frank

On 26 Jul 2001 Charlie_Surface@oti.com wrote:
I have been playing around with using the input driver independent of
Photon. I'm targetting an x86 system with a PS/2 mouse. I start
devi-hirun with the following command: "devi-hirun -Pr ps2 mousedev &". I
then start my test application, which simply does an open(), a read(), and
a close() on /dev/devi/mouse0. It usually works the first time, and I am
able to see correct button and move events coming from the mouse. The
problem is that when I try to run my test again, I am unable to read
anything from the mouse. However, devi-hirun is still running at this
point and /dev/devi/mouse0 still exists. Is there some sort of reset
command which I need to issue to the mouse in order to use it again? Does
anyone have any ideas?

thanks
Charlie


Alex Chapiro

Re: using mouse input through resource manager interface

Post by Alex Chapiro » Tue Oct 09, 2001 12:53 pm

Actually, I don't understand your experiment. If you start driver with -Pr
parameters, Photon doesn't receive mouse events and doesn't render mouse
cursor any more. To restore mouse cursor (if you really need this strange
configuration) you have to start second instance of devi-hirun:

devi-hirun ps2 fd -d /dev/mouse0

This secondary instance should process mouse events and transfer them to
Photon.
If you are using your own Photon driver, you have to use correct mouse
protocol (3 or 4-bytes PS2 mouse in this case).

If my understanding of your question is incorrect, please elaborate it a
little bit more.

"Frank Liu" <liug@mama.indstate.edu> wrote in message
news:Pine.LNX.4.33.0110082326010.21594-100000@mama.indstate.edu...

have you had answer to this?
I am doing the same thing for my XFree86 X Window port.
After I start "devi-hirun -Pr ps2 mousedev &", I can see
the /dev/devi/mouse0, but the mouse doesnt work right,
if I move the mouse, the cursor/pointer on the screen will
jump around and then stick to the edge.
The only way I can get it to work is to attach a serial mouse
and then use the /dev/ser1 device. The funny thing is if I
start "devi-hirun -Pr msoft fd -d/dev/ser1 &", and let X window
use /dev/devi/mouse0, I will end up with the same problem as
the PS2 mouse. It looks like the "devi-hirun" is doing something.
Any help will be appreciated.
Frank

On 26 Jul 2001 Charlie_Surface@oti.com wrote:

I have been playing around with using the input driver independent of
Photon. I'm targetting an x86 system with a PS/2 mouse. I start
devi-hirun with the following command: "devi-hirun -Pr ps2 mousedev &".
I
then start my test application, which simply does an open(), a read(),
and
a close() on /dev/devi/mouse0. It usually works the first time, and I
am
able to see correct button and move events coming from the mouse. The
problem is that when I try to run my test again, I am unable to read
anything from the mouse. However, devi-hirun is still running at this
point and /dev/devi/mouse0 still exists. Is there some sort of reset
command which I need to issue to the mouse in order to use it again?
Does
anyone have any ideas?

thanks
Charlie



Alex Chapiro

Re: using mouse input through resource manager interface

Post by Alex Chapiro » Tue Oct 09, 2001 1:06 pm

Sorry, later I read you message in another thread. Just ignore my previous
answer. What I can suggest you is to try to start driver with verbosity
level 3 (-vvv) without XFree86 and to look at the output. It helps to
understand if the output to mouse0 is correct. It could be very useful, if
you send at least part f this logging data to me.


"Alex Chapiro" <achapiro@qnx.com> wrote in message
news:9pus19$52$1@nntp.qnx.com...
Actually, I don't understand your experiment. If you start driver with -Pr
parameters, Photon doesn't receive mouse events and doesn't render mouse
cursor any more. To restore mouse cursor (if you really need this strange
configuration) you have to start second instance of devi-hirun:

devi-hirun ps2 fd -d /dev/mouse0

This secondary instance should process mouse events and transfer them to
Photon.
If you are using your own Photon driver, you have to use correct mouse
protocol (3 or 4-bytes PS2 mouse in this case).

If my understanding of your question is incorrect, please elaborate it a
little bit more.

"Frank Liu" <liug@mama.indstate.edu> wrote in message
news:Pine.LNX.4.33.0110082326010.21594-100000@mama.indstate.edu...


have you had answer to this?
I am doing the same thing for my XFree86 X Window port.
After I start "devi-hirun -Pr ps2 mousedev &", I can see
the /dev/devi/mouse0, but the mouse doesnt work right,
if I move the mouse, the cursor/pointer on the screen will
jump around and then stick to the edge.
The only way I can get it to work is to attach a serial mouse
and then use the /dev/ser1 device. The funny thing is if I
start "devi-hirun -Pr msoft fd -d/dev/ser1 &", and let X window
use /dev/devi/mouse0, I will end up with the same problem as
the PS2 mouse. It looks like the "devi-hirun" is doing something.
Any help will be appreciated.
Frank

On 26 Jul 2001 Charlie_Surface@oti.com wrote:

I have been playing around with using the input driver independent of
Photon. I'm targetting an x86 system with a PS/2 mouse. I start
devi-hirun with the following command: "devi-hirun -Pr ps2 mousedev
&".
I
then start my test application, which simply does an open(), a read(),
and
a close() on /dev/devi/mouse0. It usually works the first time, and I
am
able to see correct button and move events coming from the mouse. The
problem is that when I try to run my test again, I am unable to read
anything from the mouse. However, devi-hirun is still running at this
point and /dev/devi/mouse0 still exists. Is there some sort of reset
command which I need to issue to the mouse in order to use it again?
Does
anyone have any ideas?

thanks
Charlie





Post Reply

Return to “qdn.public.ddk.input”