From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: >net-wireless/bluez-4.63 unable to connect audio streams due commit
Date: Mon, 4 Oct 2010 14:35:53 +0200 [thread overview]
Message-ID: <20101004123552.GC11737@pengutronix.de> (raw)
In-Reply-To: <1286187946.7898.0.camel@localhost.localdomain>
Hello Pacho,
On Mon, Oct 04, 2010 at 12:25:46PM +0200, Pacho Ramos wrote:
> > I would say this was because of double authentication request, but it
> > seems it is not the case, actually ssp doesn't seems to be used at all
> > here so this must be something else, maybe you should try this:
> >
> > http://thread.gmane.org/gmane.linux.bluez.kernel/7256
> >
>
> Thanks but, how should I try to apply that patch? Looks like
> net/bluetooth/rfcomm/core.c is not present on bluez-4.72 sources
I guess this is a patch to apply to your kernel, not bluez.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-10-04 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 18:13 >net-wireless/bluez-4.63 unable to connect audio streams due commit Pacho Ramos
2010-09-20 18:49 ` Johan Hedberg
2010-10-02 13:58 ` Pacho Ramos
2010-10-04 10:00 ` Luiz Augusto von Dentz
2010-10-04 10:25 ` Pacho Ramos
2010-10-04 12:35 ` Uwe Kleine-König [this message]
2010-10-04 12:45 ` How add support of LLMNR for PAN Chetankumar Manjegowda
2010-10-04 15:35 ` Arun Kumar
2010-10-05 4:47 ` Chetankumar Manjegowda
2010-10-11 11:17 ` Arun K. Singh
2010-10-18 18:24 ` >net-wireless/bluez-4.63 unable to connect audio streams due commit Pacho Ramos
2010-10-31 11:25 ` Pacho Ramos
2010-11-02 17:25 ` Peter Hurley
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=20101004123552.GC11737@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pacho@condmat1.ciencias.uniovi.es \
/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;
as well as URLs for NNTP newsgroup(s).