From: "Heston James - Cold Beans" <heston.james@coldbeans.co.uk>
To: "'BlueZ development'" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] CreateBonding while periodic scanning
Date: Fri, 11 Jul 2008 09:14:24 +0100 [thread overview]
Message-ID: <00de01c8e32e$213a9fb0$63afdf10$@james@coldbeans.co.uk> (raw)
In-Reply-To: <1215757212.9744.13.camel@californication>
Hi Manuel, good to see you mate.
>> I've sent this patch before, but for some reason I didn't got either a
>> positive or even negative response.
>>
>> Problem is like this, when we're doing a periodic scan we should be able
>> to do bonding, but according to the code we can't, so then something is
>> wrong, either we can't do periodic scanning, or we need to fix a bug.
>
> so in general you should be able to create an ACL link when even in
> inquiry phase. So in theory it should stop periodic inquiry and then
> create the ACL link and then continue. We might have hit some chip
> limitations here and this is why it was there. I removed it since it low
> risk. No so many applications use periodic inquiry :)
I've experienced this very same behaviour in the past and was always
concerned that it was me using the mainloop inappropriately, I'm glad to see
other people find the same issue.
When using period inquiry, it would seem that if I perform any other form of
operation, such as an SDP enquiry, or creating an RFCOMM connection it halts
the current 'period' of scanning and it doesn't start again until the start
of the next 'period'.
This does cause a fair amount of frustration as it means if you're sdping
nearby remote device as you find them that you're only ever really dealing
with 1 remote device per scan period which is very inefficient.
I've noticed the exact same behaviour with a standard inquiry scan too, as
soon as attempting to perform one of these other operations whilst scanning
the scan stops and the 'discoverycomplete()' signal is emmited.
Manuel, I'm interested in the patch and will look at applying it to my local
working copy to see how it behaves for me.
Marcel, Are you saying that this issue cannot be resolved by a patch and is
a chip limitation? Is there likely to be any fix for this?
Marcel, for those of us that need a periodic enquiry, would you advocate the
use of our own internal standard inquiry loops that restart a scan when
discoverycomplete() signal is emitted? Or is this likely to crash the bluez
deamon by putting too much strain on it?
Heston
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-07-11 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 19:22 [Bluez-devel] [PATCH] CreateBonding while periodic scanning Manuel Naranjo
2008-07-11 6:20 ` Marcel Holtmann
2008-07-11 8:14 ` Heston James - Cold Beans [this message]
2008-07-11 8:31 ` Marcel Holtmann
2008-07-11 8:34 ` Heston James - Cold Beans
2008-07-11 10:07 ` Manuel Naranjo
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='00de01c8e32e$213a9fb0$63afdf10$@james@coldbeans.co.uk' \
--to=heston.james@coldbeans.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
/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