From: James Le Cuirot <chewi@aura-online.co.uk>
To: linux-bluetooth@vger.kernel.org
Subject: Re: PANU currently broken?
Date: Fri, 13 Mar 2009 17:20:33 +0000 [thread overview]
Message-ID: <20090313172033.13e0ed4a@symphony> (raw)
In-Reply-To: <2d5a2c100903120723m5ce4a0fcp59d5de8a09aa6242@mail.gmail.com>
On Thu, 12 Mar 2009 11:23:40 -0300
Luiz Augusto von Dentz <luiz.dentz@gmail.com> wrote:
> On Thu, Mar 12, 2009 at 8:11 AM, James Le Cuirot
> <chewi@aura-online.co.uk> wrote:
> > On Sun, 8 Mar 2009 23:22:15 +0000
> > James Le Cuirot <chewi@aura-online.co.uk> wrote:
> >
> >> I've managed to serve my phone with NAP successfully but using
> >> PANU in the other direction has not worked at all.
> >
> > I'm not necessarily asking for an immediate fix here but could
> > someone at least explain the situation? That might allow me to fix
> > it myself.
>
> I have a fix for it, the problem was that we use
> g_io_channel_set_close_on_unref on BtIO code so we should maintain a
> reference if we want to maintain the socket open.
>
> Try this patch and see if it helps:
> http://gitorious.org/projects/bluez/repos/vudentzs-clone/commits/adaf1c1d4f2c8764c3d5336759368a0e1dcb44c9
>
> ps: we are still reviewing the code so it may have some bug left.
Thanks, Luiz.
I'm afraid it's still not working though. I tried the patch on its own
against 4.32 and also the latest from the for-upstream branch. I
generally get "bnep setup failed" as well as "Hangup or error on l2cap
server socket" in the log.
James
prev parent reply other threads:[~2009-03-13 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 23:22 PANU currently broken? James Le Cuirot
2009-03-12 11:11 ` James Le Cuirot
2009-03-12 14:23 ` Luiz Augusto von Dentz
2009-03-13 17:20 ` James Le Cuirot [this message]
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=20090313172033.13e0ed4a@symphony \
--to=chewi@aura-online.co.uk \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.