An only IR receiver for a wireless keyboard and a wireless

QNX Newsgroups (Archives) qdn.public.ddk.input
1

Hi,
I have a set of input devices for develope Input: a wireless keyboard, a
wireless mouse and a IR(infrared) receiver who has a serial output to a PC.
The nondecoded data of the keyboard and the mouse pass through the same
receiver. Here I have thus one interruption hardware and I need two event
buses in my devi-hirun. I think of using an only device module (like fd but
modified) to decode the data and separate them respectively to kbd module
and to the mouse module (msoft) and so on. But this will change the parallel
event bus structure in devi-hirun, what I would avoid if possible.
So have anyone a solution more optimal, more elegant than this?

Thanks

Any help would be appriciated
Qingguo Kou

2

Just look to DDK implementation of PS2 controller access: one module - many
devices. The only receiver separates data by source and emits different
pulses to corresponding buses.

“Qingguo Kou” <qingguo@irg.ca> wrote in message
news:9s9hof$hr6$1@inn.qnx.com…

Hi,
I have a set of input devices for develope Input: a wireless keyboard, a
wireless mouse and a IR(infrared) receiver who has a serial output to a
PC.
The nondecoded data of the keyboard and the mouse pass through the same
receiver. Here I have thus one interruption hardware and I need two event
buses in my devi-hirun. I think of using an only device module (like fd
but
modified) to decode the data and separate them respectively to kbd module
and to the mouse module (msoft) and so on. But this will change the
parallel
event bus structure in devi-hirun, what I would avoid if possible.
So have anyone a solution more optimal, more elegant than this?

Thanks

Any help would be appriciated
Qingguo Kou

3

But I don’t think there is an single receiver in the case of PS/2. There are
two hardware interruptions (if I don’t mistake), two I/O ports (Primary and
auxiliary to receive respectively the keyboard and mouse data), and two
instances of device level module (kb) . In my case, I can’t use a second
instance of the device level module (fd) because there is only one I/O port
(COM1 or COM2) receiving all the data.

Thanks.

Any help would be appriciated
Qingguo Kou

“Alex Chapiro” <achapiro@qnx.com> a écrit dans le message news:
9s9oqu$7nk$1@nntp.qnx.com…

Just look to DDK implementation of PS2 controller access: one module -
many
devices. The only receiver separates data by source and emits different
pulses to corresponding buses.

“Qingguo Kou” <> qingguo@irg.ca> > wrote in message
news:9s9hof$hr6$> 1@inn.qnx.com> …
Hi,
I have a set of input devices for develope Input: a wireless keyboard,
a
wireless mouse and a IR(infrared) receiver who has a serial output to a
PC.
The nondecoded data of the keyboard and the mouse pass through the same
receiver. Here I have thus one interruption hardware and I need two
event
buses in my devi-hirun. I think of using an only device module (like fd
but
modified) to decode the data and separate them respectively to kbd
module
and to the mouse module (msoft) and so on. But this will change the
parallel
event bus structure in devi-hirun, what I would avoid if possible.
So have anyone a solution more optimal, more elegant than this?

Thanks

Any help would be appriciated
Qingguo Kou
\

4

Yes, you are right, but only for regular case. There are platforms that
share one interrupt for both devices. PS2 API itself was designed keeping in
mind common case of using devices such as PS2 port multiplexer. In this
case one and the same interrupt handler processes all interrupt events. Take
a look at psd2api.c and ps2contr.c (interrupt handler intr_contr is in the
last one).


“Qingguo Kou” <qingguo@irg.ca> wrote in message
news:9sbup9$52f$1@inn.qnx.com…

But I don’t think there is an single receiver in the case of PS/2. There
are
two hardware interruptions (if I don’t mistake), two I/O ports (Primary
and
auxiliary to receive respectively the keyboard and mouse data), and two
instances of device level module (kb) . In my case, I can’t use a second
instance of the device level module (fd) because there is only one I/O
port
(COM1 or COM2) receiving all the data.

Thanks.

Any help would be appriciated
Qingguo Kou

“Alex Chapiro” <> achapiro@qnx.com> > a écrit dans le message news:
9s9oqu$7nk$> 1@nntp.qnx.com> …
Just look to DDK implementation of PS2 controller access: one module -
many
devices. The only receiver separates data by source and emits different
pulses to corresponding buses.

“Qingguo Kou” <> qingguo@irg.ca> > wrote in message
news:9s9hof$hr6$> 1@inn.qnx.com> …
Hi,
I have a set of input devices for develope Input: a wireless keyboard,
a
wireless mouse and a IR(infrared) receiver who has a serial output to
a
PC.
The nondecoded data of the keyboard and the mouse pass through the
same
receiver. Here I have thus one interruption hardware and I need two
event
buses in my devi-hirun. I think of using an only device module (like
fd
but
modified) to decode the data and separate them respectively to kbd
module
and to the mouse module (msoft) and so on. But this will change the
parallel
event bus structure in devi-hirun, what I would avoid if possible.
So have anyone a solution more optimal, more elegant than this?

Thanks

Any help would be appriciated
Qingguo Kou


\

5

Hi, Mr. Chapiro,
Thank you for your email. It has served as a good enlightening guidance for
me. And I’ll study in detail psd2api.c and ps2contr.c.
Since a week, I have been tring a simple solution by launching
devi-hirun kbd fd -d/dev/kbd msoft fdmk -d/dev/ser1
Here I only modified one time fd (fdmk) to call a function of IR data
decode. After decode, this function calls kbd->input or msoft->input
respectively on the basis of the nature of the data. All data come from
/dev/ser1. Nothing is connected to the keyboard port.
But I have still a problem: all keyboard IR data emitted in 8 bits have
become 7 bits (the highest bit est RAZ) when they are read from the
/dev/ser; and I can not find where they are changed.
Any help would be appriciated.
Qingguo Kou
----- Original Message -----
From: “Alex Chapiro” <achapiro@qnx.com>
To: “Qingguo Kou” <qingguo@irg.ca>
Sent: Wednesday, November 07, 2001 12:00 PM
Subject: Re: An only IR receiver for a wireless keyboard and a wireless
mouse to complete Input?


Yes, you are right, but only for regular case. There are platforms that
share one interrupt for both devices. PS2 API itself was designed keeping
in
mind common case of using devices such as PS2 port multiplexer. In this
case one and the same interrupt handler processes all interrupt events.
Take
a look at psd2api.c and ps2contr.c (interrupt handler intr_contr is in the
last one).

----- Original Message -----
From: “Qingguo Kou” <> qingguo@irg.ca
Newsgroups: qdn.public.ddk.input
Sent: Wednesday, November 07, 2001 4:37 PM
Subject: Re: An only IR receiver for a wireless keyboard and a wireless
mouse to complete Input?


But I don’t think there is an single receiver in the case of PS/2. There
are
two hardware interruptions (if I don’t mistake), two I/O ports (Primary
and
auxiliary to receive respectively the keyboard and mouse data), and two
instances of device level module (kb) . In my case, I can’t use a second
instance of the device level module (fd) because there is only one I/O
port
(COM1 or COM2) receiving all the data.

Thanks.

Any help would be appriciated
Qingguo Kou

“Alex Chapiro” <> achapiro@qnx.com> > a écrit dans le message news:
9s9oqu$7nk$> 1@nntp.qnx.com> …
Just look to DDK implementation of PS2 controller access: one module -
many
devices. The only receiver separates data by source and emits
different
pulses to corresponding buses.

“Qingguo Kou” <> qingguo@irg.ca> > wrote in message
news:9s9hof$hr6$> 1@inn.qnx.com> …
Hi,
I have a set of input devices for develope Input: a wireless
keyboard,
a
wireless mouse and a IR(infrared) receiver who has a serial output
to
a
PC.
The nondecoded data of the keyboard and the mouse pass through the
same
receiver. Here I have thus one interruption hardware and I need two
event
buses in my devi-hirun. I think of using an only device module (like
fd
but
modified) to decode the data and separate them respectively to kbd
module
and to the mouse module (msoft) and so on. But this will change the
parallel
event bus structure in devi-hirun, what I would avoid if possible.
So have anyone a solution more optimal, more elegant than this?

Thanks

Any help would be appriciated
Qingguo Kou




\

6

The problem was caused by the baud and the stopb setting of the serial port.
Qingguo Kou

“Qingguo Kou” <qingguo@irg.ca> a écrit dans le message news:
9tdutk$qt2$1@inn.qnx.com…

Hi, Mr. Chapiro,
Thank you for your email. It has served as a good enlightening guidance
for
me. And I’ll study in detail psd2api.c and ps2contr.c.
Since a week, I have been tring a simple solution by launching
devi-hirun kbd fd -d/dev/kbd msoft fdmk -d/dev/ser1
Here I only modified one time fd (fdmk) to call a function of IR data
decode. After decode, this function calls kbd->input or msoft->input
respectively on the basis of the nature of the data. All data come from
/dev/ser1. Nothing is connected to the keyboard port.
But I have still a problem: all keyboard IR data emitted in 8 bits have
become 7 bits (the highest bit est RAZ) when they are read from the
/dev/ser; and I can not find where they are changed.
Any help would be appriciated.
Qingguo Kou
----- Original Message -----
From: “Alex Chapiro” <> achapiro@qnx.com
To: “Qingguo Kou” <> qingguo@irg.ca
Sent: Wednesday, November 07, 2001 12:00 PM
Subject: Re: An only IR receiver for a wireless keyboard and a wireless
mouse to complete Input?


Yes, you are right, but only for regular case. There are platforms that
share one interrupt for both devices. PS2 API itself was designed
keeping
in
mind common case of using devices such as PS2 port multiplexer. In this
case one and the same interrupt handler processes all interrupt events.
Take
a look at psd2api.c and ps2contr.c (interrupt handler intr_contr is in
the
last one).

----- Original Message -----
From: “Qingguo Kou” <> qingguo@irg.ca
Newsgroups: qdn.public.ddk.input
Sent: Wednesday, November 07, 2001 4:37 PM
Subject: Re: An only IR receiver for a wireless keyboard and a wireless
mouse to complete Input?


But I don’t think there is an single receiver in the case of PS/2.
There
are
two hardware interruptions (if I don’t mistake), two I/O ports
(Primary
and
auxiliary to receive respectively the keyboard and mouse data), and
two
instances of device level module (kb) . In my case, I can’t use a
second
instance of the device level module (fd) because there is only one I/O
port
(COM1 or COM2) receiving all the data.

Thanks.

Any help would be appriciated
Qingguo Kou

“Alex Chapiro” <> achapiro@qnx.com> > a écrit dans le message news:
9s9oqu$7nk$> 1@nntp.qnx.com> …
Just look to DDK implementation of PS2 controller access: one
module -
many
devices. The only receiver separates data by source and emits
different
pulses to corresponding buses.

“Qingguo Kou” <> qingguo@irg.ca> > wrote in message
news:9s9hof$hr6$> 1@inn.qnx.com> …
Hi,
I have a set of input devices for develope Input: a wireless
keyboard,
a
wireless mouse and a IR(infrared) receiver who has a serial output
to
a
PC.
The nondecoded data of the keyboard and the mouse pass through the
same
receiver. Here I have thus one interruption hardware and I need
two
event
buses in my devi-hirun. I think of using an only device module
(like
fd
but
modified) to decode the data and separate them respectively to kbd
module
and to the mouse module (msoft) and so on. But this will change
the
parallel
event bus structure in devi-hirun, what I would avoid if
possible.
So have anyone a solution more optimal, more elegant than this?

Thanks

Any help would be appriciated
Qingguo Kou







\