HID mini port over i8042prt PS2 stack?

I'd like to report my PS2 interface device to system as a HID class
device.
That means I'd like to ask i8042prt to be my port driver,
I know there is a moufilter sample in the DDK, well it report itself
as a mouse class instead of HID class, and it is a upper filter for
the i8042prt.
Is it possible to create a HID driver which talked to i8042prt and
report itself as a HID class device?
Any hint would be apprecited.
-chueh888

You will need to replace the system-provided KbdClass, and manually install
your replacement for a particular keyboard stack (with a reboot, since PS/2
devices cannot be stopped).

The replacement must have the same lower edge as KbdClass has, with a HID
upper edge.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

"chueh8" <> wrote in message
news: oups.com...
> I'd like to report my PS2 interface device to system as a HID class
> device.
> That means I'd like to ask i8042prt to be my port driver,
> I know there is a moufilter sample in the DDK, well it report itself
> as a mouse class instead of HID class, and it is a upper filter for
> the i8042prt.
> Is it possible to create a HID driver which talked to i8042prt and
> report itself as a HID class device?
> Any hint would be apprecited.
> -chueh888
>

No you cannot replace kbdclass. It's a class filter driver and it's required
even for hid keyboard devices. You have to install the i8042prt driver as a
HID device (or custom class device - PS2) with an upper device filter. This
is required to preven the kbdclass from attaching to your stack. The job of
the device filter is to register with HIDCLASS as hid minidriver and emulate
a HID keyboard device. The filter then would talk to the port driver to get
the data and feed it to the HIDclass as hid reports.

The final stack would look like:

kbdclass - class filter
kdbhid - FDO
hidclass - PDO
hidmini-driver - as upper filter
i8042prt - FDO
Root bus - PD0

Question to the OP, why do you want to make your PS2 device appear as a
device?

--
- This posting is provided "AS IS" with no warranties, and confers no
rights.

Hi, Eliyas
Thanks for your hint!
1. If the stack should be the one you described, then how the inf
would be?
2. I have the similar thinking as yours, somewhat different is that I
modified the vhidmini sample, and ask i8042prt to be a lower filter of
vhidmini, is it the same as your comment? (and now we are trying to
get hooked by i8042prt..)
3. Actually, our device is a digitier with different interface to
system, USB/UART/PS2, for USB I/F we go as the HID class and no more
vendor driver needed, we could trasfer digitier data to system with
inbox hid driver. For UART I/F, we modify the hidpen sample, which is
a hid mini driver but ask serial.sys as its lower filter. As to
report to system that we are a hid digitier, also to be the same hid
interface for our utility, we'd like to write a driver which report to
system we are a hid digitier but hook into ps2 stack.
Any comment or hint would be welcomed and appreciated!
-chueh888


On 8 27 , 10 51 , "Eliyas Yakub [MSFT]"
<eliy...@online.discussion.microsoft.com> wrote:
> No you cannot replace kbdclass. It's a class filter driver and it's required
> even for hid keyboard devices. You have to install the i8042prt driver as a
> HID device (or custom class device - PS2) with an upper device filter. This
> is required to preven the kbdclass from attaching to your stack. The job of
> the device filter is to register with HIDCLASS as hid minidriver and emulate
> a HID keyboard device. The filter then would talk to the port driver to get
> the data and feed it to the HIDclass as hid reports.
>
> The final stack would look like:
>
> kbdclass - class filter
> kdbhid - FDO
> hidclass - PDO
> hidmini-driver - as upper filter
> i8042prt - FDO
> Root bus - PD0
>
> Question to the OP, why do you want to make your PS2 device appear as a
> device?
>
> --
> - This posting is provided "AS IS" with no warranties, and confers no
> rights.

I think you should discuss this with our tablet PC folks and figure out the
right approach. Send me a private email with the clear description of the
problem and I will hook you up with the right folks.

-Eliyas

Note: PS/2 devices are not designed (even electrically) for hotplug.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

"chueh8" <> wrote in message
news: ups.com...
> Hi, Eliyas
> Thanks for your hint!
> 1. If the stack should be the one you described, then how the inf
> would be?
> 2. I have the similar thinking as yours, somewhat different is that I
> modified the vhidmini sample, and ask i8042prt to be a lower filter of
> vhidmini, is it the same as your comment? (and now we are trying to
> get hooked by i8042prt..)
> 3. Actually, our device is a digitier with different interface to
> system, USB/UART/PS2, for USB I/F we go as the HID class and no more
> vendor driver needed, we could trasfer digitier data to system with
> inbox hid driver. For UART I/F, we modify the hidpen sample, which is
> a hid mini driver but ask serial.sys as its lower filter. As to
> report to system that we are a hid digitier, also to be the same hid
> interface for our utility, we'd like to write a driver which report to
> system we are a hid digitier but hook into ps2 stack.
> Any comment or hint would be welcomed and appreciated!
> -chueh888
>
>
> On 8 27 , 10 51 , "Eliyas Yakub [MSFT]"
> <eliy...@online.discussion.microsoft.com> wrote:
> > No you cannot replace kbdclass. It's a class filter driver and it's
required
> > even for hid keyboard devices. You have to install the i8042prt driver as a
> > HID device (or custom class device - PS2) with an upper device filter. This
> > is required to preven the kbdclass from attaching to your stack. The job of
> > the device filter is to register with HIDCLASS as hid minidriver and
emulate
> > a HID keyboard device. The filter then would talk to the port driver to get
> > the data and feed it to the HIDclass as hid reports.
> >
> > The final stack would look like:
> >
> > kbdclass - class filter
> > kdbhid - FDO
> > hidclass - PDO
> > hidmini-driver - as upper filter
> > i8042prt - FDO
> > Root bus - PD0
> >
> > Question to the OP, why do you want to make your PS2 device appear as a
> > device?
> >
> > --
> > - This posting is provided "AS IS" with no warranties, and confers no
> > rights.
>
>

as the previous owner of i8042prt, you do not want to go down this path, it
will be very complicated. I think what you can do is insert a device upper
filter driver between i8042prt and mouclass. Have this driver enumerate a
PDO, use the KMDF kbdfiltr driver as an example. The PDO you will be
enumerating is not raw though. On top of this new PDO you will install
your HID miniport. You can create a custom i/o interface to get the mouse
input data from your filter. This way you leave the i8042prt stack in tact
and create a 2nd HID stack on the side.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Maxim S. Shatskih" <> wrote in message
news:...
> Note: PS/2 devices are not designed (even electrically) for hotplug.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
>
> http://www.storagecraft.com
>
> "chueh8" <> wrote in message
> news: ups.com...
>> Hi, Eliyas
>> Thanks for your hint!
>> 1. If the stack should be the one you described, then how the inf
>> would be?
>> 2. I have the similar thinking as yours, somewhat different is that I
>> modified the vhidmini sample, and ask i8042prt to be a lower filter of
>> vhidmini, is it the same as your comment? (and now we are trying to
>> get hooked by i8042prt..)
>> 3. Actually, our device is a digitier with different interface to
>> system, USB/UART/PS2, for USB I/F we go as the HID class and no more
>> vendor driver needed, we could trasfer digitier data to system with
>> inbox hid driver. For UART I/F, we modify the hidpen sample, which is
>> a hid mini driver but ask serial.sys as its lower filter. As to
>> report to system that we are a hid digitier, also to be the same hid
>> interface for our utility, we'd like to write a driver which report to
>> system we are a hid digitier but hook into ps2 stack.
>> Any comment or hint would be welcomed and appreciated!
>> -chueh888
>>
>>
>> On 8 27 , 10 51 , "Eliyas Yakub [MSFT]"
>> <eliy...@online.discussion.microsoft.com> wrote:
>> > No you cannot replace kbdclass. It's a class filter driver and it's
> required
>> > even for hid keyboard devices. You have to install the i8042prt driver
>> > as a
>> > HID device (or custom class device - PS2) with an upper device filter.
>> > This
>> > is required to preven the kbdclass from attaching to your stack. The
>> > job of
>> > the device filter is to register with HIDCLASS as hid minidriver and
> emulate
>> > a HID keyboard device. The filter then would talk to the port driver to
>> > get
>> > the data and feed it to the HIDclass as hid reports.
>> >
>> > The final stack would look like:
>> >
>> > kbdclass - class filter
>> > kdbhid - FDO
>> > hidclass - PDO
>> > hidmini-driver - as upper filter
>> > i8042prt - FDO
>> > Root bus - PD0
>> >
>> > Question to the OP, why do you want to make your PS2 device appear as a
>> > device?
>> >
>> > --
>> > - This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>>
>>
>

Hi, Doron,

I guess your suggestion is just what I want to do,
Well, I don't really know how to implement the following...
>"Have this driver enumerate a
> PDO, use the KMDF kbdfiltr driver as an example. The PDO you will be
> enumerating is not raw though. On top of this new PDO you will install
> your HID miniport."
And also how to combine hid and mouse upper filter into one inf
file...
More details would be appreciated...
(do that when bus_relation_pnp?)

So far we have tried to install a virtual hid driver and set i8042prt
as its lower filter,,
well, we try to send out internal_mouse_connect down to i8042prt, it
is ok,
but i8042prt failed to send out ps2 hook to our driver...

We are trying Eliyas's suggestion,, well not finished yet...
Any more details would be appreciated!
Thanks.
-chueh888








On 8 29 , 12 44 , "Doron Holan [MSFT]" <dor...@online.microsoft.com>
wrote:
> as the previous owner of i8042prt, you do not want to go down this path, it
> will be very complicated. I think what you can do is insert a device upper
> filter driver between i8042prt and mouclass. Have this driver enumerate a
> PDO, use the KMDF kbdfiltr driver as an example. The PDO you will be
> enumerating is not raw though. On top of this new PDO you will install
> your HID miniport. You can create a custom i/o interface to get the mouse
> input data from your filter. This way you leave the i8042prt stack in tact
> and create a 2nd HID stack on the side.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Maxim S. Shatskih" <ma...@storagecraft.com> wrote in messagenews:.. .
>
>
>
> > Note: PS/2 devices are not designed (even electrically) for hotplug.
>
> > --
> > Maxim Shatskih, Windows DDK MVP
> > StorageCraft Corporation
> > ma...@storagecraft.com
> >http://www.storagecraft.com
>
> > "chueh8" <steelch...@gmail.com> wrote in message
> >news: oups.com...
> >> Hi, Eliyas
> >> Thanks for your hint!
> >> 1. If the stack should be the one you described, then how the inf
> >> would be?
> >> 2. I have the similar thinking as yours, somewhat different is that I
> >> modified the vhidmini sample, and ask i8042prt to be a lower filter of
> >> vhidmini, is it the same as your comment? (and now we are trying to
> >> get hooked by i8042prt..)
> >> 3. Actually, our device is a digitier with different interface to
> >> system, USB/UART/PS2, for USB I/F we go as the HID class and no more
> >> vendor driver needed, we could trasfer digitier data to system with
> >> inbox hid driver. For UART I/F, we modify the hidpen sample, which is
> >> a hid mini driver but ask serial.sys as its lower filter. As to
> >> report to system that we are a hid digitier, also to be the same hid
> >> interface for our utility, we'd like to write a driver which report to
> >> system we are a hid digitier but hook into ps2 stack.
> >> Any comment or hint would be welcomed and appreciated!
> >> -chueh888
>
> >> On 8 27 , 10 51 , "Eliyas Yakub [MSFT]"
> >> <eliy...@online.discussion.microsoft.com> wrote:
> >> > No you cannot replace kbdclass. It's a class filter driver and it's
> > required
> >> > even for hid keyboard devices. You have to install the i8042prt driver
> >> > as a
> >> > HID device (or custom class device - PS2) with an upper device filter.
> >> > This
> >> > is required to preven the kbdclass from attaching to your stack. The
> >> > job of
> >> > the device filter is to register with HIDCLASS as hid minidriver and
> > emulate
> >> > a HID keyboard device. The filter then would talk to the port driver to
> >> > get
> >> > the data and feed it to the HIDclass as hid reports.
>
> >> > The final stack would look like:
>
> >> > kbdclass - class filter
> >> > kdbhid - FDO
> >> > hidclass - PDO
> >> > hidmini-driver - as upper filter
> >> > i8042prt - FDO
> >> > Root bus - PD0
>
> >> > Question to the OP, why do you want to make your PS2 device appear as a
> >> > device?
>
> >> > --
> >> > - This posting is provided "AS IS" with no warranties, and confers no
> >> > rights.- -
>
> - -

you will need 2 INFs, one for the filter (in the pointers class), one for
the HID stack (in the HID class). Use KMDF for all of your drivers here, it
will be much easier for yourself.

as for when the i8042prt sends certain ioctls, look at the sources
themselves, they are in the WDK

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"chueh8" <> wrote in message
news: ups.com...
> Hi, Doron,
>
> I guess your suggestion is just what I want to do,
> Well, I don't really know how to implement the following...
>>"Have this driver enumerate a
>> PDO, use the KMDF kbdfiltr driver as an example. The PDO you will be
>> enumerating is not raw though. On top of this new PDO you will install
>> your HID miniport."
> And also how to combine hid and mouse upper filter into one inf
> file...
> More details would be appreciated...
> (do that when bus_relation_pnp?)
>
> So far we have tried to install a virtual hid driver and set i8042prt
> as its lower filter,,
> well, we try to send out internal_mouse_connect down to i8042prt, it
> is ok,
> but i8042prt failed to send out ps2 hook to our driver...
>
> We are trying Eliyas's suggestion,, well not finished yet...
> Any more details would be appreciated!
> Thanks.
> -chueh888
>
>
>
>
>
>
>
>
> On 8 29 , 12 44 , "Doron Holan [MSFT]" <dor...@online.microsoft.com>
> wrote:
>> as the previous owner of i8042prt, you do not want to go down this path,
>> it
>> will be very complicated. I think what you can do is insert a device
>> upper
>> filter driver between i8042prt and mouclass. Have this driver enumerate
>> a
>> PDO, use the KMDF kbdfiltr driver as an example. The PDO you will be
>> enumerating is not raw though. On top of this new PDO you will install
>> your HID miniport. You can create a custom i/o interface to get the
>> mouse
>> input data from your filter. This way you leave the i8042prt stack in
>> tact
>> and create a 2nd HID stack on the side.
>>
>> d
>>
>> --
>> Please do not send e-mail directly to this alias. this alias is for
>> newsgroup purposes only.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Maxim S. Shatskih" <ma...@storagecraft.com> wrote in
>> messagenews:.. .
>>
>>
>>
>> > Note: PS/2 devices are not designed (even electrically) for hotplug.
>>
>> > --
>> > Maxim Shatskih, Windows DDK MVP
>> > StorageCraft Corporation
>> > ma...@storagecraft.com
>> >http://www.storagecraft.com
>>
>> > "chueh8" <steelch...@gmail.com> wrote in message
>> >news: oups.com...
>> >> Hi, Eliyas
>> >> Thanks for your hint!
>> >> 1. If the stack should be the one you described, then how the inf
>> >> would be?
>> >> 2. I have the similar thinking as yours, somewhat different is that I
>> >> modified the vhidmini sample, and ask i8042prt to be a lower filter of
>> >> vhidmini, is it the same as your comment? (and now we are trying to
>> >> get hooked by i8042prt..)
>> >> 3. Actually, our device is a digitier with different interface to
>> >> system, USB/UART/PS2, for USB I/F we go as the HID class and no more
>> >> vendor driver needed, we could trasfer digitier data to system with
>> >> inbox hid driver. For UART I/F, we modify the hidpen sample, which is
>> >> a hid mini driver but ask serial.sys as its lower filter. As to
>> >> report to system that we are a hid digitier, also to be the same hid
>> >> interface for our utility, we'd like to write a driver which report to
>> >> system we are a hid digitier but hook into ps2 stack.
>> >> Any comment or hint would be welcomed and appreciated!
>> >> -chueh888
>>
>> >> On 8 27 , 10 51 , "Eliyas Yakub [MSFT]"
>> >> <eliy...@online.discussion.microsoft.com> wrote:
>> >> > No you cannot replace kbdclass. It's a class filter driver and it's
>> > required
>> >> > even for hid keyboard devices. You have to install the i8042prt
>> >> > driver
>> >> > as a
>> >> > HID device (or custom class device - PS2) with an upper device
>> >> > filter.
>> >> > This
>> >> > is required to preven the kbdclass from attaching to your stack. The
>> >> > job of
>> >> > the device filter is to register with HIDCLASS as hid minidriver and
>> > emulate
>> >> > a HID keyboard device. The filter then would talk to the port driver
>> >> > to
>> >> > get
>> >> > the data and feed it to the HIDclass as hid reports.
>>
>> >> > The final stack would look like:
>>
>> >> > kbdclass - class filter
>> >> > kdbhid - FDO
>> >> > hidclass - PDO
>> >> > hidmini-driver - as upper filter
>> >> > i8042prt - FDO
>> >> > Root bus - PD0
>>
>> >> > Question to the OP, why do you want to make your PS2 device appear
>> >> > as a
>> >> > device?
>>
>> >> > --
>> >> > - This posting is provided "AS IS" with no warranties, and confers
>> >> > no
>> >> > rights.- -
>>
>> - -
>
>

Hi, Doron,

Installed kbfiltr as you suggestted, but I modified it from
WdfPdoInitAssignRawDevice(pDeviceInit, &GUID_DEVCLASS_KEYBOARD) to
WdfPdoInitAssignRawDevice(pDeviceInit, &GUID_DEVCLASS_HIDCLASS);
when crating the PDO.

Well, I don't find the system enumerating a new device and ask me for
a new HID device to install...
then I don't know how to install the 2nd inf for my hid mini port...
Any comment? Thanks.

-chueh888



On 8 29 , 5 52 , "Doron Holan [MSFT]" <dor...@online.microsoft.com>
wrote:
> you will need 2 INFs, one for the filter (in the pointers class), one for
> the HID stack (in the HID class). Use KMDF for all of your drivers here, it
> will be much easier for yourself.
>
> as for when the i8042prt sends certain ioctls, look at the sources
> themselves, they are in the WDK
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "chueh8" <steelch...@gmail.com> wrote in message
>
> news: ups.com...
>
>
>
> > Hi, Doron,
>
> > I guess your suggestion is just what I want to do,
> > Well, I don't really know how to implement the following...
> >>"Have this driver enumerate a
> >> PDO, use the KMDF kbdfiltr driver as an example. The PDO you will be
> >> enumerating is not raw though. On top of this new PDO you will install
> >> your HID miniport."
> > And also how to combine hid and mouse upper filter into one inf
> > file...
> > More details would be appreciated...
> > (do that when bus_relation_pnp?)
>
> > So far we have tried to install a virtual hid driver and set i8042prt
> > as its lower filter,,
> > well, we try to send out internal_mouse_connect down to i8042prt, it
> > is ok,
> > but i8042prt failed to send out ps2 hook to our driver...
>
> > We are trying Eliyas's suggestion,, well not finished yet...
> > Any more details would be appreciated!
> > Thanks.
> > -chueh888
>
> > On 8 29 , 12 44 , "Doron Holan [MSFT]" <dor...@online.microsoft.com>
> > wrote:
> >> as the previous owner of i8042prt, you do not want to go down this path,
> >> it
> >> will be very complicated. I think what you can do is insert a device
> >> upper
> >> filter driver between i8042prt and mouclass. Have this driver enumerate
> >> a
> >> PDO, use the KMDF kbdfiltr driver as an example. The PDO you will be
> >> enumerating is not raw though. On top of this new PDO you will install
> >> your HID miniport. You can create a custom i/o interface to get the
> >> mouse
> >> input data from your filter. This way you leave the i8042prt stack in
> >> tact
> >> and create a 2nd HID stack on the side.
>
> >> d
>
> >> --
> >> Please do not send e-mail directly to this alias. this alias is for
> >> newsgroup purposes only.
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
>
> >> "Maxim S. Shatskih" <ma...@storagecraft.com> wrote in
> >> messagenews:.. .
>
> >> > Note: PS/2 devices are not designed (even electrically) for hotplug.
>
> >> > --
> >> > Maxim Shatskih, Windows DDK MVP
> >> > StorageCraft Corporation
> >> > ma...@storagecraft.com
> >> >http://www.storagecraft.com
>
> >> > "chueh8" <steelch...@gmail.com> wrote in message
> >> >news: oups.com...
> >> >> Hi, Eliyas
> >> >> Thanks for your hint!
> >> >> 1. If the stack should be the one you described, then how the inf
> >> >> would be?
> >> >> 2. I have the similar thinking as yours, somewhat different is that I
> >> >> modified the vhidmini sample, and ask i8042prt to be a lower filter of
> >> >> vhidmini, is it the same as your comment? (and now we are trying to
> >> >> get hooked by i8042prt..)
> >> >> 3. Actually, our device is a digitier with different interface to
> >> >> system, USB/UART/PS2, for USB I/F we go as the HID class and no more
> >> >> vendor driver needed, we could trasfer digitier data to system with
> >> >> inbox hid driver. For UART I/F, we modify the hidpen sample, which is
> >> >> a hid mini driver but ask serial.sys as its lower filter. As to
> >> >> report to system that we are a hid digitier, also to be the same hid
> >> >> interface for our utility, we'd like to write a driver which report to
> >> >> system we are a hid digitier but hook into ps2 stack.
> >> >> Any comment or hint would be welcomed and appreciated!
> >> >> -chueh888
>
> >> >> On 8 27 , 10 51 , "Eliyas Yakub [MSFT]"
> >> >> <eliy...@online.discussion.microsoft.com> wrote:
> >> >> > No you cannot replace kbdclass. It's a class filter driver and it's
> >> > required
> >> >> > even for hid keyboard devices. You have to install the i8042prt
> >> >> > driver
> >> >> > as a
> >> >> > HID device (or custom class device - PS2) with an upper device
> >> >> > filter.
> >> >> > This
> >> >> > is required to preven the kbdclass from attaching to your stack. The
> >> >> > job of
> >> >> > the device filter is to register with HIDCLASS as hid minidriver and
> >> > emulate
> >> >> > a HID keyboard device. The filter then would talk to the port driver
> >> >> > to
> >> >> > get
> >> >> > the data and feed it to the HIDclass as hid reports.
>
> >> >> > The final stack would look like:
>
> >> >> > kbdclass - class filter
> >> >> > kdbhid - FDO
> >> >> > hidclass - PDO
> >> >> > hidmini-driver - as upper filter
> >> >> > i8042prt - FDO
> >> >> > Root bus - PD0
>
> >> >> > Question to the OP, why do you want to make your PS2 device appear
> >> >> > as a
> >> >> > device?
>
> >> >> > --
> >> >> > - This posting is provided "AS IS" with no warranties, and confers
> >> >> > no
> >> >> > rights.- -
>
> >> - -- -
>
> - -