Thanks Doron,
The firmware is to be written from scratch.
I´m trying to build the driver from firefly sample without success.
I will need receive a PIN entered on the ATM keyboard product and all
keyboard traffic for another product.
I have this solution for PS/2 Keyboard using an upper filter.
I think if I write an upper filter I won´t care the USB stuff… like URBs,
pipes. Is it correct ?
Regards
Wilson
-----Mensagem original-----
De: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]Em nome de Doron Holan
Enviada em: terça-feira, 31 de janeiro de 2006 15:12
Para: Windows System Software Devs Interest List
Assunto: RE: [ntdev] HID Keyboard with special features
If you are building the HID keyboard from scratch, you can probably expose
some of this functionality through a separate top level collection. For
instance, you can have private usage that you expose to download firmware to
the device. this will allow the complicated logic to live in user mode
(e.g. reading, validating, parsing the firmware file, etc).
Are you going to encrypt all keyboard traffic or just special parts of the
keyboard? Again, if it is just parts, you can create a separate top level
collection to expose this functionality.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Tuesday, January 31, 2006 10:06 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] HID Keyboard with special features
Also, note that it’s fairly easy to send control transfers if you are
layered below the FDO (hidusb), because you don’t need a pipe handle.
However, if you need to perform bulk or interrupt transfers, you’ll need to
watch for URB_FUNCTION_SELECT_CONFIGURATION and friends, so that you can
keep a copy of the pipe handles. This will often break the contract between
device and FDO, since bulk/interrupt transfers are usually part of
multi-transfer protocols. Control transfers, though, are self-contained,
and therefore usually fairly safe.
– arlie
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ray Trent
Sent: Tuesday, January 31, 2006 12:54 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] HID Keyboard with special features
In order to talk to the device you’ll need to send URBs. In order to do
that, you need to be below hidusb in the stack (because it filters out any
URB requests). So, install on the USB PnPID and specify your driver as a
lower filter.
Yes, KMDF is probably the easiest way to go with that.
Wilson Bernardes wrote:
Hello,
I need do build a HID USB Keyboard with some special features but
I´m
new in USB and HID.
This features are something like updating firmware on fly, receive
and send encrypted data and so on.
I´ve just installed the KMDF 1.0 and new DDK.
I´m very confusing about the correct way to follow.
I already inspect the firefly sample and it doesn´t help very much.
Do I need make a lower or upper filter driver ??
Is the Walter Oney book a better starting point for my project ?
(I´m
using Chris Cant book but it´s a bit confuse).Any help is highly apprecitated.
Regards.
WilsonScanned by WinProxy
http://www.Ositis.com/
–
Ray
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@stonestreetone.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Scanned by WinProxy
http://www.Ositis.com/