public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 17:12:37 +0200	[thread overview]
Message-ID: <48BFFAE5.9040801@free.fr> (raw)
In-Reply-To: <1220536177.6714.68.camel@californication>

Hi Marcel

>> 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 :-)
> 
> I am seriously sick of this f*cked up hardware. What is it? My guess
> would be a TI chip.

...and you won !!

> 
>>> 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' :-)
> 
> I would first have to know which host controller it is, before I
> actually think about adding something like this.


I dug deeper in this second problem.
In fact it has not been solved by the 2.6.17-rc5 kernel.

I misinterpreted the result as i inadvertedly changed bluetooth dongle 
at the same time.
So issue with wrong pin code only arise whith Sony Erisson(TI) + ST + bluez.
Sony Erisson(TI) + BCM + bluez works.

As you said issue is clearly seems to come from the hardware (LMP).



> 
>>> 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. :-(
> 
> Don't use SOL_L2CAP or SOL_RFCOMM anymore. They will be all
> SOL_BLUETOOTH since there are no different between the socket options
> itself.

Yeah sure but from the kernel point of view there is a a level parameter 
passed to setsockopt/getsockopt which is already ignored... or maybe you 
were just speeking about user space ?

Regards,

Fabien

  reply	other threads:[~2008-09-04 15:12 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
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 [this message]
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=48BFFAE5.9040801@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