Hai,
I am writing a device driver for 1394 controller on windows.
1394 needs physical memory address for the self-id and config rom bus
buffer. How can I allocate a buffer which address can be accessed by the
hardware.
If memory is allocated by ExallocatePool it returns the virtual memory
address about which device do not know.
Can any one of you tell me a way to solve this.
Thanx in advance.
Reagards,
kedar.
AllocateCommonBuffer is one way.
So, is your card not OHCI compliant? I am curious as to why you are writing
your own driver for this card as opposed to using the standard Windows 1394
bus driver stack for this card?
–
Bill McKenzie
Compuware Corporation
http://www.compuware.com/products/driverstudio
“kedar” wrote in message news:xxxxx@ntdev…
>
> Hai,
>
> I am writing a device driver for 1394 controller on windows.
>
> 1394 needs physical memory address for the self-id and config rom bus
> buffer. How can I allocate a buffer which address can be accessed by the
> hardware.
> If memory is allocated by ExallocatePool it returns the virtual memory
> address about which device do not know.
>
> Can any one of you tell me a way to solve this.
>
>
> Thanx in advance.
>
> Reagards,
> kedar.
>
>
Bill McKenzie,
My card is OHCIcompliant and where can I get the details of standard
Windows 1394 bus driver stack .
Regards,
kedar.
Just to be clear here, you are saying that your card is a OHCI compliant
1394 host controller card right? If so, and you plug that card in to a
Windows platform (later than NT4), drivers should load automagically. If
drivers don’t load automagically, I would be suspect of your OHCI
compliance.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/NDIS pkts with our free WDMSniffer util:
http://frontline.compuware.com/nashua/patches/utility.htm
“kedar” wrote in message news:xxxxx@ntdev…
>
> Bill McKenzie,
>
> My card is OHCIcompliant and where can I get the details of standard
> Windows 1394 bus driver stack .
>
>
> Regards,
> kedar.
>
>
> I am writing a device driver for 1394 controller on windows.
1394 needs physical memory address for the self-id and config rom
bus
buffer. How can I allocate a buffer which address can be accessed by
the
hardware.
By ->AllocateCommonBuffer for sure.
Max