Re: 1394 Virtual Device Driver

From: W. Scott Kerchner (kerchner_at_uic.com)
Date: 12/16/04

  • Next message: cristalink: "Re: 1394 Virtual Device Driver" 
    Date: Thu, 16 Dec 2004 16:06:27 -0500

    Thanks so much for your reply...

    I have no problem talking to my virtual device driver from another physical
    device
    on the bus whether it be a 1394 pc or a 1394 dsp.

    What I really would like to be able to do is have one virtual device driver
    send
    a message to a second virtual device driver both located on the same machine
    without going out to the bus.

    In other words... Send an IRP down to the port driver and have it recognize
    that this
    message is destined for my second virtual device driver and therefore enter
    my callback for
    the second virtual device.

    It seems that the port driver should be able to recognize that the
    destination port is the
    PC's port number and that the destination address is an address allocated
    within my
    second virtual device driver's address allocation range and therefore just
    "wrap the message
    back".

    Any input would be appreciated...

    Thanks in advance,

    Scott

    "cristalink" <cristalink@nospam.nospam> wrote in message
    news:OxnFyY64EHA.824@TK2MSFTNGP11.phx.gbl...
    > >Maybe sending a message between physical and virtual device drivers on
    the
    > >same machine is not possible??
    >
    > It seems so. Try two machines connected via 1394, one with a virtual
    device
    > driver, another one with physical devices.
    > --
    > http://www.firestreamer.com - NTBackup to DVD and DV
    >
    >
    > "W. Scott Kerchner" <kerchner@uic.com> wrote in message
    > news:uI9$9ne4EHA.4072@TK2MSFTNGP10.phx.gbl...
    > > Hello All,
    > >
    > > This question is directed towards anyone who has used 1394 virtual
    device
    > > drivers.
    > >
    > > I am using XP SP2 with a Unibrain 1394 FireBoard connected to three
    > > proprietary
    > > 1394 DSP nodes and a virtual device inside the PC. The 1394 host
    > > controller
    > > enumerates the bus successfully including the virtual device driver. And
    I
    > > am able
    > > to send a message from any physical driver to any proprietary node and
    > > from
    > > any proprietary node to my virtual device driver or physical driver.
    > >
    > > My problem is I would like to send a message from one of my physical
    > > drivers
    > > to my
    > > virtual driver (since this would actually be required if and when my
    > > virtual
    > > device becomes
    > > a physical device out on the bus). This doesn't seem to be supported by
    > > the
    > > bus driver or
    > > the port driver for that matter.
    > >
    > > Does anyone know if the 1394 driver stack (bus and port driver) supports
    > > communication
    > > between a physical device driver and a virtual device driver (On the
    same
    > > machine)?
    > >
    > > My system is configured as follows:
    > >
    > > Node 0: A Firespy Analyzer.
    > > Node 1: Proprietary 1394 DSP.
    > > Node 2: Proprietary 1394 DSP.
    > > Node 3: Proprietary 1394 DSP.
    > > Node 4: 1394 Host Controller.
    > > Node 4: Virtual Device Driver.
    > >
    > > The physical device driver for Node 1: Responds to address
    0xFFFFFA000000
    > > The physical device driver for Node 2: Responds to address
    0xFFFFFB000000
    > > The physical device driver for Node 3: Responds to address
    0xFFFFFC000000
    > > The virutal device driver for Node 4: Responsds to address
    > > 0xFFFFFD000000
    > >
    > > My desire is to send a write request message from the driver for the
    node
    > > 1
    > > device to my virtual
    > > device. I've even tried to send this request directly to the port driver
    > > (raw mode addressing) using node 4
    > > and the address for the virtual device without luck.
    > >
    > > if (fRawMode)
    > > {
    > > pIRB->u.AsyncWrite.DestinationAddress.IA_Destination_ID.NA_Bus_Number
    > > =
    > > LOCAL_BUS;
    > >
    pIRB->u.AsyncWrite.DestinationAddress.IA_Destination_ID.NA_Node_Number
    > > =
    > > 4;
    > > pIRB->u.AsyncWrite.DestinationAddress.IA_Destination_Offset.Off_High
    =
    > > 0xFFFF;
    > > pIRB->u.AsyncWrite.DestinationAddress.IA_Destination_Offset.Off_Low
    =
    > > 0xFD000000;
    > > }
    > >
    > > Does anyone have any ideas? Maybe sending a message between physical and
    > > virtual device drivers
    > > on the same machine is not possible??
    > >
    > > Thanks in advance.
    > >
    > > Scott Kerchner
    > >
    > >
    > >
    >
    >

  • Next message: cristalink: "Re: 1394 Virtual Device Driver"
    Loading