From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 30 19:57:01 2006 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 3F7F416ACD1 for ; Tue, 30 May 2006 19:57:01 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [209.89.70.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE88543D6A for ; Tue, 30 May 2006 19:57:00 +0000 (GMT) (envelope-from lyndon@orthanc.ca) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by orthanc.ca (8.13.4/8.13.4) with ESMTP id k4UJuvlf012646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 May 2006 13:56:57 -0600 (MDT) (envelope-from lyndon@orthanc.ca) Date: Tue, 30 May 2006 13:56:57 -0600 (MDT) From: Lyndon Nerenberg To: Maksim Yevmenkin In-Reply-To: <447C83B4.5060905@savvis.net> Message-ID: <20060530135402.C12000@orthanc.ca> References: <20060528153917.I84195@orthanc.ca> <447C83B4.5060905@savvis.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on orthanc.ca Cc: freebsd-bluetooth@freebsd.org Subject: Re: DBT-122 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: Tue, 30 May 2006 19:57:11 -0000 > i'm not sure what are you asking here. are you asking > > 1) if the specific dongle model (i.e. d-link dbt-122) is supported by freebsd In a nutshell: yes. Under 6.1-RELEASE I have tried both the DBT-122 and a Kensington (unknown model #), and both show up as ugen* devices, and not ubt* as expected. I'm still trying to wrap my head around the specifics of FreeBSD's bluetooth implementation, so I'm unclear whether I have unsupported hardware, or a botched kernel configuration, or what. --lyndon