From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Code questions
Date: Tue, 22 Feb 2005 00:17:29 +0100 [thread overview]
Message-ID: <1109027849.7626.38.camel@pegasus> (raw)
In-Reply-To: <1108566885.11909.29.camel@g-necml5-146.rd.francetelecom.fr>
Hi Emmanuel,
> I've looked to the code of BlueTooth in the linux 2.6.10 kernel, and
> I've a few questions :
>
> - I've noticed that OCF_PIN_CODE_REPLY and OCF_PIN_CODE_NEG_REPLY are
> defined in include/net/bluetooth/hci.h, but never used in the code; and
> that the function hci_pin_code_request_evt() is void. Does it mean that
> the current BlueZ implementation doesn't support PIN codes? (Just making
> sure.)
currently these events are handled by the hcid, but for the upcoming
security and profile manager they will be moved inside the kernel.
> - Is the PIN Code Request event masked away (I think it is, because I
> also read the BlueTooth Specification, and it doesn't allow not reacting
> to this event), and in this case, were is it masked? I didn't found the
> masking in the code.
Nothing is masked away.
> - I've noticed the same for other events (that they were not treated).
> Are they also just masked away, and, if yes, were in the code do this
> masking happens?
Explain what you mean.
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-21 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 15:14 [Bluez-devel] Code questions zze-COLBUS Emmanuel RD-MAPS-GRE
2005-02-21 23:17 ` Marcel Holtmann [this message]
2005-02-23 16:14 ` zze-COLBUS Emmanuel RD-MAPS-GRE
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=1109027849.7626.38.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