From: "Thor Egil Skaug" <paxtonrd@hotmail.com>
To: "'Steven Singer'" <steven.singer@csr.com>
Cc: "'BlueZ Mailing List'" <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] AUX1 packets
Date: Mon, 1 Mar 2004 08:07:55 -0800 [thread overview]
Message-ID: <000401c3ffa7$5b52f310$46a57e40@thores> (raw)
In-Reply-To: <40435D9D.5020509@csr.com>
>If both ends of the link support CQDDR then the Link Managers will do
this automatically.
>
>If you try to do this yourself, you'll just end up with the host and
the controller fighting each other.
>
> - Steven
But the LM can only use packet types that I specified in
create_connection or change_connection_packet_type,
in addition to the mandatory DM1 type. Am I correct in assuming this?
Will the link manager notify me through events that CQDDR scheme has
changed packet type?
How do I know whether CQDDR is supported, and is there any way of
disabling this?
Thor
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-03-01 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 19:35 [Bluez-users] AUX1 packets Thor Egil Skaug
2004-03-01 14:55 ` Marcel Holtmann
2004-03-01 15:44 ` Thor Egil Skaug
2004-03-01 15:58 ` Steven Singer
2004-03-01 16:07 ` Thor Egil Skaug [this message]
2004-03-01 16:18 ` Steven Singer
-- strict thread matches above, loose matches on Subject: below --
2004-03-01 17:02 Thor Egil Skaug
2004-03-01 18:13 ` Steven Singer
2004-03-01 19:09 ` Thor Egil Skaug
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='000401c3ffa7$5b52f310$46a57e40@thores' \
--to=paxtonrd@hotmail.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=steven.singer@csr.com \
/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