1394: IRP_MN_BUS_RESET

NTDEV
1

Hi,

my 1394 device sends a bus reset to indicate that it has booted and is
ready for operation. The driver answers this with sending some needed
connection information to the device and now communication can be
established. More host computers can connect to the device that way.

I was answering IRP_MN_BUS_RESET, but this is deprecated and also does
not seem to get called on my Windows 7 test machine. What would be the
alternative way to get informed about a bus reset.

Thanks for any hints,
Hagen.

2

Hi Hagen,

You can create a mechanism similar to the one you are currently using: Using REQUEST_BUS_RESET_NOTIFICATION your driver can register a bus reset notification routine.
The bus driver will invoke the notification routine in response to a bus reset (at DISPATCH_LEVEL). The notification routine shall complete a pending IRP (IOCTL defined by you) to communicate the bus reset from the driver to the application.

Best regards
Thomas

3

Thanks, Robin, Thomas,

that seems to work!
I must have overlooked that in the WDK documentation…! Although a
hint to REQUEST_BUS_RESET_NOTIFICATION on the deprecated
IRP_MN_BUS_RESET would have helped. But this is solved,

Thanks a lot,
Hagen.

On Wed, Jan 6, 2010 at 10:06 AM, wrote:
> Hi Hagen,
>
> You can create a mechanism similar to the one you are currently using: Using REQUEST_BUS_RESET_NOTIFICATION your driver can register a bus reset notification routine.
> The bus driver will invoke the notification routine in response to a bus reset (at DISPATCH_LEVEL). The notification routine shall complete a pending IRP (IOCTL defined by you) to communicate the bus reset from the driver to the application.
>
> Best regards
> Thomas
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>

–
___________________
dynamic acoustics e.U.
Weyringergasse 37/3/11a
1040 Vienna / Austria
+43 680 1268 751

VAT: ATU65049413
FN: 326751t
IBAN: AT463200000010353811
BIC: RLNWATWW

4

Please use the send feedback link on the doc page and suggest that this additional link be made

d

-----Original Message-----
From: stephan o’farrill
Sent: Wednesday, January 06, 2010 3:03 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] 1394: IRP_MN_BUS_RESET

Thanks, Robin, Thomas,

that seems to work!
I must have overlooked that in the WDK documentation…! Although a
hint to REQUEST_BUS_RESET_NOTIFICATION on the deprecated
IRP_MN_BUS_RESET would have helped. But this is solved,

Thanks a lot,
Hagen.

On Wed, Jan 6, 2010 at 10:06 AM, wrote:
> Hi Hagen,
>
> You can create a mechanism similar to the one you are currently using: Using REQUEST_BUS_RESET_NOTIFICATION your driver can register a bus reset notification routine.
> The bus driver will invoke the notification routine in response to a bus reset (at DISPATCH_LEVEL). The notification routine shall complete a pending IRP (IOCTL defined by you) to communicate the bus reset from the driver to the application.
>
> Best regards
> Thomas
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>

–
___________________
dynamic acoustics e.U.
Weyringergasse 37/3/11a
1040 Vienna / Austria
+43 680 1268 751

VAT: ATU65049413
FN: 326751t
IBAN: AT463200000010353811
BIC: RLNWATWW

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer