public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Alok <alokbarsode@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Questions regarding NetLink APIs.
Date: Fri, 17 Oct 2008 20:21:31 +0530	[thread overview]
Message-ID: <1224255091.6175.18.camel@greatbear> (raw)

Marcel, 

I had a few queries regarding the netlink APIs. I have been referring to
net/wireless/nl80211.c for reference.

1. Would the ioctls on raw sock(BTPROTO_HCI), be converted into netlink
commands?
eg HCIGETDEVLIST (NLBLUETOOTH_CMD_GET_DEVLIST),
HCIGETDEVINFO    (NLBLUETOOTH_CMD_GET_DEV_INFO),
HCIDEVUP         (NLBLUETOOTH_CMD_DEVUP) .. etc 


2. Would the netlink attributes consist of HCI Ioctl requests
structures ? or individual structure members?
eg:

[NLBLUETOOTH_ATTR_DEV_INFO] = {.len = sizeof(struct hci_dev_info)} 


3. Would it be a separate kernel module? 

Thanks, 
Alok.


             reply	other threads:[~2008-10-17 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 14:51 Alok [this message]
2008-10-23  4:48 ` Questions regarding NetLink APIs Marcel Holtmann
2008-10-30 13:10   ` [PATCH] NetLink patches Alok

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=1224255091.6175.18.camel@greatbear \
    --to=alokbarsode@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