Date: Tue, 11 Jun 2002 11:57:21 -0700 From: Terry Lambert <tlambert2@mindspring.com> 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 Message-ID: <3D064811.D512445F@mindspring.com> References: <20020611173935.84573.qmail@web13305.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D064811.D512445F>