[ltp] uhci-hcd problems

[René Castberg]

Just a note that in windows it is possible to programatically connect/
disconnect the hardware.  So there must be some way of doing it. 
Unforunatly the NVRAM doesn't seem to store this information, and i
don't know enough about the hardware that i could debug it to find
out... Maybe somebody else on the list does???

Rene

On Wed, 2004-06-16 at 11:48 +0100, Mark Houlder wrote:he hardware so 
> Not sure about the SCO issue - I tried removing it from my kernel and it 
> made no difference :(
> 
> and as far as i know, there's no way to programmatically 
> connect/disconnect the bluetooth hardware...
> 
> 
> mark
> 
> 
> Cameron McCormack wrote:
> > Hi Mark.
> > 
> > Mark Houlder:
> > 
> >>anyone come across this before, and/or suggest a solution?
> > 
> > 
> > So I got my mouse today, it works well (except I haven't quite worked
> > out how to get all the extra buttons working properly).  Anyway, I
> > experienced the same problem as you.  I'm running 2.6.6.  I checked the
> > changelog for 2.6.7 and saw this:
> > 
> >   <marcel@holtmann.org>
> > 	[Bluetooth] Fix disconnect race on ISOC interface
> > 	
> > 	The hci_usb_disconnect() gets called recursively when SCO support
> > 	is enabled and used. This causes sysfs_hash_and_remove() finally to
> > 	dereference a NULL pointer.
> > 	
> > 	Noticed by Sebastian Schmidt <yath@yath.eu.org>
> > 
> > This sounds like it should fix the problem.
> > 
> > Cameron
> > 
> 
> 
> intY has scanned this email for all known viruses (www.inty.com)
>