Virtual AVC Subunit

Hello fellow 1394 driver writers,

I’m looking forward to turn a Windows XP PC into a device that contains
an AVC subunit. The DDK explains the various virtual stacks (V1394 and
VAVC) and all the possible ioctls, but it does not explain the steps
required to create a subunit.

Basically, I want the system to create a VAVC PDO on which to load my
driver.

I already tried a couple of different paths I considered as possibly
worthy of success but I didn’t end up with what I was looking for. I
was wondering if any of you knew how to do this. Which parts of this
process can be done from user-mode and which parts need to be in the
kernel?

First, I need to get the AVC driver (AVC.SYS) loaded before I can
communicate with it and create the subunit. Apparently, I need to
create a new unit directory in the host configuration rom to include the
AVC signature in it (A02D&10001). I think I need to be in the kernel to
do such a thing. Is it true? It seems easy to call the V1394 API from
user-mode (by including ntdd1394.h) but it does not seem to be possible
to include 1394.h from user-mode. Any info about this?

Any help or comment on this topic is welcome. TIA

Mat

Shame on me, I posted HTML! Here's the original post:

Hello fellow 1394 driver writers,

I'm looking forward to turn a Windows XP PC into a device that contains
an AVC subunit. The DDK explains the various virtual stacks (V1394 and
VAVC) and all the possible ioctls, but it does not explain the steps
required to create a subunit.

Basically, I want the system to create a VAVC PDO on which to load my
driver.

I already tried a couple of different paths I considered as possibly
worthy of success but I didn't end up with what I was looking for. I
was wondering if any of you knew how to do this. Which parts of this
process can be done from user-mode and which parts need to be in the
kernel?

First, I need to get the AVC driver (AVC.SYS) loaded before I can
communicate with it and create the subunit. Apparently, I need to
create a new unit directory in the host configuration rom to include the
AVC signature in it (A02D&10001). I think I need to be in the kernel to
do such a thing. Is it true? It seems easy to call the V1394 API from
user-mode (by including ntdd1394.h) but it does not seem to be possible
to include 1394.h from user-mode. Any info about this?

Any help or comment on this topic is welcome. TIA

Mat