From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Prepare patch bluez for the CoD in hci_conn
Date: Mon, 06 Dec 2004 07:40:36 +0100 [thread overview]
Message-ID: <1102315236.8510.55.camel@pegasus> (raw)
In-Reply-To: <1102340081.653.6.camel@debian>
Hi Chen,
> Do you remember that I have asked a CoD question in this list and you
> ask me to do a patch to let the CoD value in hci_conn? Now I have time
> to do this work and I have something to clarify for I am not a bluez
> member before and I am not very fimiliar with BlueZ.
>
> This time I just want to keep the remote CoD value in hci_conn when a
> connection is done. But as you know, sometimes it is impossible for us
> to get the CoD of the remote class without a prestage inquiry. So, not
> every CoD value in hci_conn is valid. I will check the BT spec to find a
> right way to tell the user whether the CoD is valid.
>
> Is it enough that I add a field to hci_conn and when the connection is
> done I update the field?
you need only to add a "__u8 dev_class[3]" field to the data structure
and if you don't know the current value for CoD. For example for an
outgoing connection, where the value is not in the inquiry cache, then
you simply put 0x000000 in there.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-12-06 6:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 13:34 [Bluez-devel] Prepare patch bluez for the CoD in hci_conn Chen Bin
2004-12-06 6:40 ` Marcel Holtmann [this message]
2004-12-06 15:11 ` Chen Bin
2004-12-06 7:18 ` Marcel Holtmann
2004-12-06 15:50 ` Chen Bin
2004-12-06 8:07 ` Marcel Holtmann
2004-12-06 15:53 ` Chen Bin
2004-12-06 8:41 ` Marcel Holtmann
2004-12-06 16:54 ` Chen Bin
2004-12-06 9:04 ` Marcel Holtmann
2004-12-06 17:40 ` Chen Bin
2004-12-06 9:56 ` Marcel Holtmann
2004-12-06 17:05 ` Chen Bin
2004-12-06 9:14 ` Marcel Holtmann
2004-12-06 17:21 ` Chen Bin
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=1102315236.8510.55.camel@pegasus \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox