From: Marcel Holtmann <marcel@holtmann.org>
To: Fabien Chevalier <fabchevalier@free.fr>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Sniff mode issues regarding Sony Ericsson headsets: kernel patch proposal.
Date: Sun, 14 Sep 2008 11:22:51 +0200 [thread overview]
Message-ID: <1221384171.6695.85.camel@californication> (raw)
In-Reply-To: <48CCCA22.5090001@free.fr>
Hi Fabien,
> >> Here are patches against 2.6.27-rc6 and latest bluez git that add
> >> support for point 1 below.
> >
> > problem with these patches is that they are a layer violation between
> > L2CAP and HCI.
>
> Yes that is true but that is nothing that isn't already existing. Same
> trick is used for L2CAP_CONNINFO.
no they don't. Look at the code. It is nicely abstracted on how we
handle the two layers.
> > It should also work on incoming and outgoing connections
> > the same way.
>
> I'm not following you there...
We wanna be able to set this on a server socket and also enforce it on a
connection we created.
> > Also when using socket options, I prefer that we set them
> > and store the value and the execute it once the connections is up.
>
> Agreed. I was just too lazy to do that :-)
Lazy doesn't get it upstream :)
> > Personally I prefer if we would enhance hci_send_acl() to indicate that
> > we expect it got get out of any power state before processing this data
> > packet.
> >
> > And of course this socket option also has to work for RFCOMM.
>
> That's pretty much useless as i don't know if that will ever get used.
> However that's not much work, i can do it if that makes you happy. ;-)
I treat RFCOMM and L2CAP the same. If we implement something for one
protocol, we do have to do the same for the other.
> Do you have any comments on the user-land side or is it how you see things ?
Actually I do have to figure out the exact naming, but it is basically
set this option once approach. And the kernel will do the rest.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-09-14 9:22 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
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 [this message]
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=1221384171.6695.85.camel@californication \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=fabchevalier@free.fr \
/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.