public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Frequency hopping(channel)
Date: Thu, 19 Jul 2007 17:32:51 +0200	[thread overview]
Message-ID: <1184859172.7111.6.camel@violet> (raw)
In-Reply-To: <624812.65481.qm@web38507.mail.mud.yahoo.com>

Hi Robert,

> I have one question to the folks in Bluez group. I saw that we have to
> specify channel for L2CAP and RFCOMM connections:
> 
> struct sockaddr_rc rfcommclient = { 0 };
> 
> rfcommclient.rc_channel = channel;
> 
> Since Bluetooth uses frequency hopping and hops from one channel to
> another what is the need to specify this field??
> 
> Also, I see that throughout the L2CAP or RFCOMM connections it shows
> the same PSM value(one we specify for the channel) in the hcidump.
> 
> Does that mean no hopping is taking place ??
> 
> I am sorry if its a silly question but expecting an answer ??

you might wanna read the specification again. I know it is big, but you
mixed up a couple of things here. The RFCOMM channels and L2CAP PSMs are
part of the multiplexing (like TCP port numbers). They have nothing to
do with any frequency hopping inside the Bluetooth radio.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-07-19 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 15:23 [Bluez-users] Frequency hopping(channel) Robert Schmidt
2007-07-19 15:32 ` Marcel Holtmann [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=1184859172.7111.6.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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