From owner-freebsd-bluetooth@FreeBSD.ORG Thu Aug 11 16:44:28 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E16A216A41F for ; Thu, 11 Aug 2005 16:44:28 +0000 (GMT) (envelope-from maksim.yevmenkin@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 297B543D58 for ; Thu, 11 Aug 2005 16:44:27 +0000 (GMT) (envelope-from maksim.yevmenkin@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so321811rne for ; Thu, 11 Aug 2005 09:44:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FoJ55mDvrA1pHfUJxJV1VHRRJRpulhAbUAjK11RWFxBvEnmaTtiTUZ19bH1rnkcoFjM32BqbOr2NNnb9SacVtwGY2ctRhfLB40J4VPnKsds6VxB/jnesmFrwYrOSDqZpTfOsDaUSICDwmVS8Ouq9SkrypKmfOgpS6DOzBPeyYD8= Received: by 10.39.3.36 with SMTP id f36mr706935rni; Thu, 11 Aug 2005 09:44:27 -0700 (PDT) Received: by 10.38.208.5 with HTTP; Thu, 11 Aug 2005 09:44:27 -0700 (PDT) Message-ID: Date: Thu, 11 Aug 2005 09:44:27 -0700 From: Maksim Yevmenkin To: Oliver In-Reply-To: <42FB7A53.1060405@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42FB7A53.1060405@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: remote name X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2005 16:44:29 -0000 Oliver, > > + hccontrol -n nbt0hci remote_name_request headset > > Could not execute command "remote_name_request". Operation timed out >=20 > I always get no answer form remote devices (after the inquiry process), > casting this command. I get only the comand status event... hmm... very strange. sorry, but i can only tell you this: if your bluetooth device acknowledge the command (with command status event) then you should look at the status field in the event. the command can be either accepted (status field in the command status event is zero) or reject (non-zero status field). in either case, from bluetooth stack point of view, things are working as expected, i.e. communication between the host and the device is not broken, command gets acknowledged, etc. is your bluetooth device based on broadcom chip too? > In which conditions have to be the remote and the local device to be > successfull ? i do not think anything extra is required. it should just work. just tried it with 3com bluetooth dongle and se k700i phone. beetle# /usr/local/etc/rc.bluetooth start ubt0 BD_ADDR: 00:04:76:e1:ae:2b Features: 0xff 0xff 0x5 00 00 00 00 00=20 <3-Slot> <5-Slot> =20 Max. ACL packet size: 128 bytes Number of ACL packets: 8 Max. SCO packet size: 64 bytes Number of SCO packets: 8 beetle# hccontrol -n ubt0hci inquiry Inquiry result, num_responses=3D1 Inquiry result #0 BD_ADDR: k700i Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 00 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x5bc0 Inquiry complete. Status: No error [00] beetle# hccontrol -n ubt0hci remote_name_request k700i BD_ADDR: k700i Name: K700i thanks, max