From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] packet type
Date: Sun, 03 Dec 2006 14:38:43 +0100 [thread overview]
Message-ID: <1165153123.19590.18.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.63.0612011423030.9177@redbean.intranet.gw-instruments.de>
Hi Peter,
> > is it possible to force bluez to use a self chosen packet type like DH5? or
> > will it automatically switch to the best packet type?
>
> You can set a Mask which packets types the baseband is allowed to use (see
> hcid.conf). However, from the allowed packet types the baseband chooses
> which one it actually uses . Further, some basenband implementations seems
> to interpret this "mask" differently (e.g. when you set the mask to DH5
> the baseband also uses all smaller packet types).
that is clearly a bug in the firmware, but please remember that packet
type DM1 is always selected.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-12-03 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 8:03 [Bluez-devel] packet type mark bernard
2006-12-01 13:27 ` Peter Wippich
2006-12-03 13:38 ` Marcel Holtmann [this message]
2006-12-03 13:37 ` Marcel Holtmann
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=1165153123.19590.18.camel@localhost \
--to=marcel@holtmann.org \
--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 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.