Re: 1394 Virtual Device Driver

From: cristalink (cristalink_at_nospam.nospam)
Date: 12/16/04 

Date: Fri, 17 Dec 2004 08:33:59 +1300

>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
>
>
>

Relevant Pages

  • Re: i386: pata_cs5520 does not work
    ... Device driver platform lacks bus and class support for being resumed. ... Device driver pci0000:00 lacks bus and class support for being resumed. ...
    (Linux-Kernel)
  • Re: The Kernal Is A Huge Security Whole In Windows
    ... The easiest way to exploit the security hole I am discussing is obviously ... driver writer is ridiculous, I'm sorry. ... responsible for making his device driver secure? ... > Performance Tab> View> Show Kernel Times. ...
    (microsoft.public.win2000.security)
  • Re: hard drive scrubbing utility
    ... we only teach the basics relative to PCI-style bus devices. ... The type of device driver you are writing makes a lot of difference also. ... There are some new books coming out from Microsoft Press on the new Kernel Mode Driver ...
    (microsoft.public.vc.mfc)
  • Re: Sort-of-Newbie Question(s)
    ... task at hand belong to the device driver development realm, ... driver to be backward compatible with Windows XP and Windows 2000, ... WDF works from Windows 2000 on. ... Can I use Visual C++ Express Edition to develop a device driver ...
    (microsoft.public.development.device.drivers)
  • 1394 Virtual Device Driver
    ... 1394 DSP nodes and a virtual device inside the PC. ... enumerates the bus successfully including the virtual device driver. ... The physical device driver for Node 1: ...
    (microsoft.public.development.device.drivers)