From: Marcel Holtmann <marcel@holtmann.org>
To: "Nicholas A. Preyss" <nalp@gmx.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Oops with 2.6.5-mh3
Date: Sat, 17 Apr 2004 11:01:20 +0200 [thread overview]
Message-ID: <1082192480.4489.50.camel@pegasus> (raw)
In-Reply-To: <20040417092404.GA1880@gmx.net>
Hi Nicholas,
> The problem was already submitted to lkml (i found at least 3reports)
> and one time declared impossible by Andrew Morton. I can't reproduce
> this error with 2.6.6-rc1 because, the usb dongle ain't even working
> at all. It seems USB is a bit messed up in that release.
for me it looks like that the hci_usb driver hits some bugs in the
current USB subsystem, but Alan Stern is going to fix them all. Please
work with him to fix them. If we need to change something on our side,
he will send me a patch and I'll include it.
> In 2.6.5 there is an easy workaround. If you don't need the hci_usb
> SCO (CONFIG_BT_HCIUSB_SCO) support, disable it in your kernelconfig.
Do this also work for 2.6.6-rcX?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-04-17 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 20:20 [Bluez-devel] Oops with 2.6.5-mh3 Matthias Thomae
2004-04-17 0:18 ` Marcel Holtmann
2004-04-17 9:24 ` Nicholas A. Preyss
2004-04-17 9:01 ` Marcel Holtmann [this message]
2004-04-17 9:09 ` Simone Gotti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1082192480.4489.50.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=nalp@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox