Re: USB device class is CDC class - which device driver to write.
- From: SenseShankar <SenseShankar@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Mar 2008 00:20:01 -0700
Hi,
It would be of great help if you could answer.
Will it be a issue to get digital certification from MS to support
Vista/XP/2000
when the USB device's class is different to that of the one which we specify
in
..INF file. (Given the thing that, my purpose of accessing the USB device is
working fine on Windows 2000/XP/Vista with minimal Authentication message
blocks while installation of the driver)
To be in specific, My USB Device shows baseclass as CDC -0x02; But I used
'Modem' as the Class to mention in .INF; (used the inbox usbser.sys driver,
by
using my own .INF), now would like to go for digital signing to avoid UCA
messages.
--
Thanks in advance,
Shankar G.
"chris.aseltine@xxxxxxxxx" wrote:
On Mar 12, 9:34 am, SenseShankar.
<SenseShan...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
"Usbser.sys will operate at the native speed of your device and the USB
stack. Baud rate, etc. settings are sent via control requests to Endpoint 0"
- If i understand it right, above thing you quoted is something how it
happens between 'Driver<-->H/w Device'.
Well, mostly. I'm saying if you call, say, SetCommState() on the COM
port created by usbser.sys, this will result in a series of serial
IOCTLs being sent to the driver. The driver, in turn, will translate
them into endpoint zero control requests sent to the device. In other
words, you won't get much in the way of endpoint zero requests without
interaction from userspace.
-Can you just breifly explain how exactly, from my application I should be
interacting with the device/Driver ?
(For example, In current existing scenario i wrote a serial class to write
&Read on to the port handle with specific baud(19200) rate given by my
protocol MODBUS - packet format.etc.)
Well, if you use usbser.sys, one of the advantages is that (in theory)
you can use exactly the same approach -- ReadFile()/WriteFile() plus
the existing set of serial API's.
- Will the usage of 'usbser.sys-CDC ACM' will still install the driver as a
'virtual COM port' OR Is there any other way to get it installed ? My concern
of questioning being - trying to make it(driver) work optimally and by
following the standards.
You basically have two choices: "Modem" class (which you don't want,
since your device is not a modem) or "Ports" ("virtual COM port")
class.
The class installer for each one will reserve you a COM port on the
system, while "Modem" class will additionally install your device as a
"modem" on the system, which again I don't think you want.
- References:
- Re: USB device class is CDC class - which device driver to write.
- From: chris . aseltine
- Re: USB device class is CDC class - which device driver to write.
- From: SenseShankar
- Re: USB device class is CDC class - which device driver to write.
- From: chris . aseltine
- Re: USB device class is CDC class - which device driver to write.
- From: SenseShankar
- Re: USB device class is CDC class - which device driver to write.
- From: chris . aseltine
- Re: USB device class is CDC class - which device driver to write.
- From: SenseShankar
- Re: USB device class is CDC class - which device driver to write.
- From: chris . aseltine
- Re: USB device class is CDC class - which device driver to write.
- Prev by Date: Re: DIFx 2.1: DPInst.exe and 'Welcome to the Found New Hardware Wizard' problem
- Next by Date: ntstrsafe.h "No such file or directory in Wndows DDk 2600" ????
- Previous by thread: Re: USB device class is CDC class - which device driver to write.
- Next by thread: 3 issues: PREfast annotations in WDK 6001
- Index(es):
Relevant Pages
|
Loading