Never use it, it is too buggy. The decent sample of 1394 code is
1394DCAM from the DirectShow branch of the DDK. It uses 1394 as lower
edge and connects to Stream.sys (StreamClassRegisterAdapter etc) from
the upper one. It also is a good sample of isochronous traffic
handling.
Max
----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Friday, September 20, 2002 9:52 AM
Subject: [ntdev] ´ð¸´: [ntdev] 1394 WDM Device Driver
>
> In DDK source code,have a sample code about 1394,you can take a look
at
> here.
>
>
>
>
> “Sean Bentley”
> ÊÕ¼þÈË£º “NT
Developers Interest List”
> ·¢¼þÈË£º
> xxxxx@lis ³ËÍ£º
> ts.osr.com Ö÷Ì⣺ [ntdev]
1394 WDM Device Driver
>
>
> 02-09-20 12:34
> Çë´ð¸´ ¸ø “NT
> Developers Interest
> List”
>
>
>
>
>
>
> General Situation -
> I am writing a Windows XP WDM device driver to communicate from
PC-to-PC
> over IEEE-1394.
>
> Specifics -
> - My goal is to communicate in native 1394 and NOT to use TCP/IP
over 1394
> (though I know this is available).
> - This driver is for “demo purposes only” (ie. it does not have to
be
> robust enough for a wide-distribution).
> - My questions are not really 1394 related, but specifically about
WDM.
> - I am new to the universe of “Windows Drivers”, especially WDM.
That
> said, I HAVE read a lot on this subject and dug in fairly deep (or
so I
> think). I now think I’m ready to ask some specific questions…
>
> Questions -
> 1) I understand the concept of the 1394 Driver Stack and the WDM
driver
> stack in general. What I’m having trouble with is in this area is
how
> SPECIFICALLY to attach to the 1394 driver stack. The way I see it,
once I
> plug-in the other PC, the PnP Manager should somehow enumerate it
and find
> my driver somehow through the inf files. I’m having trouble getting
this
> to happen. I’ve read about using the Hardware ID of the device
being
> added to the bus, but what would the Hardware ID be for just another
PC
> hosting 1394?
>
> 2) I’ve also thought of not going through the PnP Manager and just
using
> the Add New Hardware Wizard. But once again, how SPECIFICALLY in
this
> case would I attach to the 1394 driver stack. I understand the role
of
> the AddDevice() routine to create my device object and attach it to
the
> stack. And the way I understand it, the PnP Manager will pass in a
PDO to
> AddDevice(). But how can I get the PNP Manager to recognize that
the PDO
> I need is for the 1394 PDO (1394bus.sys) ?
>
> I could ask a million more, but just the answers to these would get
me
> over a big hurdle. I’d GREATLY appreciate ANY help.
>
> Thanks,
> Sean
>
> —
> You are currently subscribed to ntdev as: xxxxx@sunplus.com.cn
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> b®¶¹®vµjƶi¢ºn‰zn‘Š•zzز