From: Fabien Chevalier <fabchevalier@free.fr>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Sniff mode issues regarding Sony Ericsson headsets: kernel patch proposal.
Date: Thu, 04 Sep 2008 12:43:57 +0200 [thread overview]
Message-ID: <48BFBBED.5010504@free.fr> (raw)
In-Reply-To: <1220471377.6714.52.camel@californication>
Hi Marcel,
>
> retest with 2.6.27-rc5 since that has full Simple Pairing support and is
> the kernel version that counts.
I'm gonna rebase on this one then.
>
> Also this is not BlueZ screwing anything up. Where is written that we
> have to get out of sniff mode before we can disconnect a link. What kind
> of hardware are you using? Does BlueZ always have to cleanup after
> broken hardware and f*cked up stacks?
Lol :-)
I never said that Bluez was screwing up anything.
But as usual, there are compromises to make between sticking close to
the standard and having good interoperability, which usually involves
some level of workaround :-)
>
>> Conclusion: to have those bloody Sony Erisson headsets working we have
>> to change two things in the kernel:
>> 1) Provide a way for a L2CAP socket user to alter sniff mode exit
>> behaviour
>> 2) Make sure we exit sniff mode before to disconnect
>>
>> Question 1: Are you interested in reviewing then merging my patches if i
>> try to fix thoses issues ?
>> Question 2: I have the gut feeling that we should change default
>> behaviour to the behaviour required by those headsets, and provide a
>> socket option for the bluetooth HID, rather than the other way round.
>> What do you think ?
>>
>> If we can come on an agreement on the proper way to fix this issue then
>> i should come with a patch in a 3-4 days timeframe.
>
> Make it two separate patches. We can send the exit sniff mode command
> that is not a problem. I still don't like it, because it is the job of
> the Link Manager to do this.
Will do.
You didn't answer to question 2: what's your choice ? (btw to question 1
neither, but i guess that means a 'yes' :-)
>
> For the sniff mode setting you have to use SOL_BLUETOOTH since I will
> remove all the other SOL_* and consolidate them.
hmmm... not sure i really see what you mean. :-(
Fabien
next prev parent reply other threads:[~2008-09-04 10:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 19:37 Sniff mode issues regarding Sony Ericsson headsets: kernel patch proposal Fabien Chevalier
2008-09-03 19:49 ` [Bluez-devel] " Marcel Holtmann
2008-09-04 10:43 ` Fabien Chevalier [this message]
2008-09-04 12:56 ` Fabien Chevalier
2008-09-04 13:51 ` Marcel Holtmann
2008-09-04 15:15 ` Fabien Chevalier
2008-09-04 13:49 ` Marcel Holtmann
2008-09-04 15:12 ` Fabien Chevalier
2008-09-13 21:09 ` Fabien Chevalier
2008-09-14 0:05 ` Marcel Holtmann
2008-09-14 8:24 ` Fabien Chevalier
2008-09-14 9:22 ` Marcel Holtmann
2008-09-14 10:00 ` Fabien Chevalier
2008-09-06 16:56 ` Brian Sammon
2008-09-08 17:32 ` Fabien Chevalier
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=48BFBBED.5010504@free.fr \
--to=fabchevalier@free.fr \
--cc=bluez-devel@lists.sourceforge.net \
--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