From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bluez-users-admin@lists.sourceforge.net>
Subject: Re: [Bluez-users] Source sample custom Bluetooth
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
In-Reply-To: <AFDBF1EE-5DB6-11D9-8017-000D9348D4BE@magnifeye.com>
References: <4dfd570904122402134ec2fd32@mail.gmail.com>
	 <4dfd570904122509237f2a2f48@mail.gmail.com>
	 <1103995727.8758.31.camel@pegasus>
	 <4dfd570904122509451e811d7a@mail.gmail.com>
	 <1103996976.8758.34.camel@pegasus>
	 <4dfd5709041225095410f71a46@mail.gmail.com>
	 <1103997529.8758.36.camel@pegasus>
	 <4dfd570904122510081a9bfa7@mail.gmail.com>
	 <4dfd570904122510085371c17b@mail.gmail.com>
	 <4dfd57090412251011705f52be@mail.gmail.com>
	 <4dfd5709041225103246f6934c@mail.gmail.com>
	 <1104000494.8758.46.camel@pegasus> <002601c4ebb8$4de24200$020ba8c0@heejune>
	 <1104125195.9393.12.camel@pegasus>
	 <BEB39C04-5B6A-11D9-8017-000D9348D4BE@magnifeye.com>
	 <1104604846.4253.1.camel@pegasus>
	 <FA69107A-5DAA-11D9-8017-000D9348D4BE@magnifeye.com>
	 <1104776407.8894.53.camel@pegasus>
	 <AFDBF1EE-5DB6-11D9-8017-000D9348D4BE@magnifeye.com>
Content-Type: text/plain
Message-Id: <1104778613.8894.62.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-users-admin@lists.sourceforge.net
Errors-To: bluez-users-admin@lists.sourceforge.net
Reply-To: bluez-users@lists.sourceforge.net
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bluez-users>,
	<mailto:bluez-users-request@lists.sourceforge.net?subject=unsubscribe>
List-Id: BlueZ users <bluez-users.lists.sourceforge.net>
List-Post: <mailto:bluez-users@lists.sourceforge.net>
List-Help: <mailto:bluez-users-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bluez-users>,
	<mailto:bluez-users-request@lists.sourceforge.net?subject=subscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=bluez-users>
Date: Mon, 03 Jan 2005 19:56:53 +0100

Hi Jonathan,

> This device has a custom blue tooth stack (no rfcomm). I need to 
> inquire, connect (I can do that and see code to do it) and then to 
> build a aclpacket and do a aclread. What is the equivalent on the linux 
> side?

in this case you have to use the HCI raw socket. Otherwise you won't be
able to deal with ACL data packets. However every stack should at least
suppport L2CAP, because dealing with raw ACL data packets is never a
good idea.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users