From owner-freebsd-current  Tue Jun 11 11:58: 7 2002
Delivered-To: freebsd-current@freebsd.org
Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62])
	by hub.freebsd.org (Postfix) with ESMTP id 6EEC937B40F
	for <current@freebsd.org>; Tue, 11 Jun 2002 11:58:03 -0700 (PDT)
Received: from pool0380.cvx21-bradley.dialup.earthlink.net ([209.179.193.125] helo=mindspring.com)
	by snipe.mail.pas.earthlink.net with esmtp (Exim 3.33 #2)
	id 17Hqq4-0006Kk-00; Tue, 11 Jun 2002 11:57:57 -0700
Message-ID: <3D064811.D512445F@mindspring.com>
Date: Tue, 11 Jun 2002 11:57:21 -0700
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Maksim Yevmenkin <m_evmenkin@yahoo.com>
Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>,
	Harti Brandt <brandt@fokus.gmd.de>, current@FreeBSD.ORG
Subject: Re: Device cloning
References: <20020611173935.84573.qmail@web13305.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Maksim Yevmenkin wrote:
> Well, HCI _IS_NOT_ a network protocol like TCP or even UDP. It is a
> predefined set of control messages and events that user might send
> to the device. L2CAP which is runs over HCI _IS_ a network protocol
> and it is implemented in AF_BLUETOOTH protocol family. So application
> can say s = socket(AF_BLUETOOTH, SOCK_SEQ, BTPROTO_L2CAP) and then
> bind(s) and connect(s).


You might want to look at how you issue raw SCSI commands on devices
via CAM.  You can start with "man cam".

Your situation is exactly analogous (IMO) to a device interface
to a raw bus.

You will notice that most of it is section 3 (e.g. implemented in a
set of user space library routines on top of the SCSI bus commands).

If you look at how the CAM toys talk to the SCSI bus itself, though,
you will see an interface for jamming known format SCSI commands
down onto a SCSI bus, which is probably the level at which you want
your interface.

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message