From: Carles Cufi <carles.cufi@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth radio doesn´t reply to inquiry request
Date: Mon, 2 Mar 2009 18:32:44 +0100 [thread overview]
Message-ID: <aa4f458e0903020932g4eb4e283w61d49473c7b20353@mail.gmail.com> (raw)
In-Reply-To: <1235931668.6074.47.camel@localhost.localdomain>
Hi Marcel,
> Also should try the bluetooth-testing.git tree since it contains an
> updated btusb.ko driver.
I took the btusb.c from bluetooth-testing.git and compiled it into my
kernel. The symptoms remain exactly the same, the output of dmesg
looks identical, with the call to __set_isoc_interface still failing.
Is there anything else I can try? Do you believe this problem has been
introduced recently into the kernel?
Thanks again!
Regards,
Carles
next prev parent reply other threads:[~2009-03-02 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 12:45 Bluetooth radio doesn´t reply to inquiry request Carles Cufi
2009-03-01 18:21 ` Marcel Holtmann
2009-03-01 18:55 ` Carles Cufi
2009-03-01 23:55 ` Marcel Holtmann
2009-03-02 11:22 ` Carles Cufi
2009-03-02 17:32 ` Carles Cufi [this message]
2009-03-03 16:38 ` Carles Cufi
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=aa4f458e0903020932g4eb4e283w61d49473c7b20353@mail.gmail.com \
--to=carles.cufi@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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