Hello,
it seems to be more Bluetooth driver's problem, because I see the dongle in
lsusb
Bus 005 Device 002: ID 0b05:b700 ASUSTek Computer, Inc. Broadcom Bluetooth
2.1
Michal
Andrew Morton writes:
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sat, 20 Feb 2010 08:00:33 GMT bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=15360
Summary: Bluetooth dongle can't be put into UP state
Product: Drivers
Version: 2.5
Kernel Version: 2.6.32.3
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
AssignedTo: drivers_bluetooth@xxxxxxxxxxxxxxxxxxxx
ReportedBy: cijoml@xxxxxxxx
Regression: Yes
In 2.6.31:
hci0: Type: USB
BD Address: 00:15:AF:FA:36:04 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:1348156 acl:3392 sco:0 events:1253 errors:0
TX bytes:306309 acl:2175 sco:0 commands:42 errors:0
In 2.6.32:
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:42 errors:0
Eee901:/home/cijoml# lsusb
Bus 004 Device 002: ID 0b05:b700 ASUSTek Computer, Inc. Broadcom Bluetooth 2.1
It's a 2.6.31 -> 2.6.32 regression. Is it likely to be in
drivers/bluetooth, or in drivers/usb?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
