Bug in OSR DeviceTree?

NTDEV
1

While looking at the Device Tree of the MS Bluetooth driver stack
implementation for my USB Bluetooth Device I noticed that OSR’s DeviceTree
shows no device under the USB Bluetooth Device while I am pretty sure (from
debugging) that the device has two child devices (“Microsoft Bluetooth
Enumerator” and “Bluetooth Device (RFCOMM Protocol TDI”).

Am I getting something wrong or is this a bug in DeviceTree ?
I’m seeing this both on SP2 and on SP1 with the QFE installed.

Thanks,
Shahar.

2

Shahar Talmi wrote:

While looking at the Device Tree of the MS Bluetooth driver stack
implementation for my USB Bluetooth Device I noticed that OSR’s DeviceTree
shows no device under the USB Bluetooth Device while I am pretty sure (from
debugging) that the device has two child devices (“Microsoft Bluetooth
Enumerator” and “Bluetooth Device (RFCOMM Protocol TDI”).

You’re “pretty sure”?

Please be specific: You have a FDO for which there are no PDOs listed,
and they should be there or… do you mean something else? Wanna please
look at it in the debugger, and tell us precisely what it is that you’re
seeing that’s the problem?

When you have the details, please report bugs by sending mail to
“xxxxx@osr.com” (just to avoid clogging up this list with mail that
really is unicast by nature).

Peter
OSR

3

I’m sure.
BTHUSB reports two PDO’s in it’s bus relations while in DeviceTree no PDO’s
are listed.
I will report this to xxxxx@osr.com.

Shahar

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of PeterGV
Sent: Wednesday, November 17, 2004 10:19 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Bug in OSR DeviceTree?

Shahar Talmi wrote:

While looking at the Device Tree of the MS Bluetooth driver stack
implementation for my USB Bluetooth Device I noticed that OSR’s
DeviceTree shows no device under the USB Bluetooth Device while I am
pretty sure (from
debugging) that the device has two child devices (“Microsoft Bluetooth
Enumerator” and “Bluetooth Device (RFCOMM Protocol TDI”).

You’re “pretty sure”?

Please be specific: You have a FDO for which there are no PDOs listed, and
they should be there or… do you mean something else? Wanna please look at
it in the debugger, and tell us precisely what it is that you’re seeing
that’s the problem?

When you have the details, please report bugs by sending mail to
“xxxxx@osr.com” (just to avoid clogging up this list with mail that really is
unicast by nature).

Peter
OSR

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@safend.com To unsubscribe
send a blank email to xxxxx@lists.osr.com