From: Chen Bin <binch@mobilesoft.com.cn>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Prepare patch bluez for the CoD in hci_conn
Date: Mon, 06 Dec 2004 23:11:08 +0800 [thread overview]
Message-ID: <1102345868.2011.2.camel@debian> (raw)
In-Reply-To: <1102315236.8510.55.camel@pegasus>
Hi Marcel,
I have done this. I searched the BT spec and find two places which will
let us know the CoD value, and I simply test it, it works find.
Ok, next step is to make an interface(maybe ioctl) to let the user get
the CoD value, is it needed(if there has been a interface which can get
the entire hci_conn structure)? If it is not needed, I will send you the
patch now.
Chen
=D4=DA 2004-12-06=D2=BB=B5=C4 07:40 +0100=A3=ACMarcel Holtmann=D0=B4=B5=C0=
=A3=BA
> =B7=A2=BC=FE=C8=CB:=20
> Marcel Holtmann
> <marcel@holtmann.org>
> =BB=D8=B8=B4=D6=C1:=20
> bluez-devel@lists.sourceforge.net
> =CA=D5=BC=FE=C8=CB:=20
> BlueZ Mailing List
> <bluez-devel@lists.sourceforge.net>
> =D6=F7=CC=E2:=20
> Re: [Bluez-devel] Prepare patch
> bluez for the CoD in hci_conn
> =C8=D5=C6=DA:=20
> Mon, 06 Dec 2004 07:40:36 +0100
> (14:40 CST)
>=20
> Hi Chen,
>=20
> > 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.
> >=20
> > 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.
> >=20
> > Is it enough that I add a field to hci_conn and when the connection
> is
> > done I update the field?
>=20
> 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.
>=20
> Regards
>=20
> 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 15:11 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
2004-12-06 15:11 ` Chen Bin [this message]
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=1102345868.2011.2.camel@debian \
--to=binch@mobilesoft.com.cn \
--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