From owner-freebsd-bluetooth@FreeBSD.ORG  Thu May  5 13:51:32 2011
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
Delivered-To: bluetooth@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DB4351065677
	for <bluetooth@freebsd.org>; Thu,  5 May 2011 13:51:32 +0000 (UTC)
	(envelope-from root@free.fr)
Received: from smtpfb1-g21.free.fr (smtpfb1-g21.free.fr [212.27.42.9])
	by mx1.freebsd.org (Postfix) with ESMTP id 26A608FC1C
	for <bluetooth@freebsd.org>; Thu,  5 May 2011 13:51:30 +0000 (UTC)
Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5])
	by smtpfb1-g21.free.fr (Postfix) with ESMTP id EE0A92D937
	for <bluetooth@freebsd.org>; Thu,  5 May 2011 15:33:44 +0200 (CEST)
Received: from free.fr (unknown [82.235.65.2])
	by smtp5-g21.free.fr (Postfix) with ESMTP id CEC4AD4834A
	for <bluetooth@freebsd.org>; Thu,  5 May 2011 15:33:38 +0200 (CEST)
From: Raoul <rmgls@free.fr>
To: bluetooth@freebsd.org
Date: Thu, 05 May 2011 15:33:38 +0200
Sender: root@free.fr
Message-Id: <20110505133338.CEC4AD4834A@smtp5-g21.free.fr>
Cc: 
Subject: opcodes documentation
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Using Bluetooth in FreeBSD environments
	<freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2011 13:51:32 -0000


hi all,

in the bluetooth man page i read:

SYNOPSIS
    bt_devsend(int s, uint16_t opcode, void *param, size_t plen);

    ...

DESCRIPTION
     The bt_devsend() function sends a Bluetooth HCI command with the given
     opcode to the provided socket s, previously obtained with bt_devopen(3).
     The opcode parameter is expected to be in the host byte order.  The param
     and plen parameters specify command parameters.  The bt_devsend() func-
     tion does not modify the HCI filter on the provided socket s.  The func-
     tion returns 0 on success, or -1 if an error occurred.

grep'ing in netgraph/...
i don't find any opcode other than in bt_devsend...

are they device specifics, or something like read/rwite and so on?

Sorry for thje naive newbie question, but sure some slight
additions to the man page would be appreciated on this topic.

Thanks.

Raoul
rmgls@free.fr