From: Abe Kohandel <abe.kohandel@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: BlueZ Header Files
Date: Sat, 12 Dec 2020 09:17:47 +0000 [thread overview]
Message-ID: <20201212091747.GA16@a267d509f080> (raw)
Hello,
I would like to preface this question by saying that I am very new to both BlueZ and linux application development.
I have a question regarding the differences between the BlueZ header files and bluetooth subsystem header files in the linux kernel. I have been specifically looking at the case of establishing a L2CAP LE connection for the Object Transfer Service and I can see that the linux kernel bluetooth header files have the definitions for L2CAP_LE_CONN_REQ (0x14) and the associated l2cap_le_conn_req structure but the BlueZ header files do not. I have been able to establish my connection by manually introducing these definitions in my application but I would like to compile my application against the BlueZ library and I cannot do that without these definitions. I would be happy to submit a patch to add the definitions but first wanted to understand if there was a reason for their absence.
Thanks,
Abe
next reply other threads:[~2020-12-12 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 9:17 Abe Kohandel [this message]
2020-12-12 19:19 ` BlueZ Header Files Abe Kohandel
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=20201212091747.GA16@a267d509f080 \
--to=abe.kohandel@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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