From owner-freebsd-bluetooth@FreeBSD.ORG  Sun Apr 17 23:08:34 2005
Return-Path: <owner-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 2082816A4CE; Sun, 17 Apr 2005 23:08:34 +0000 (GMT)
Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7378543D1D; Sun, 17 Apr 2005 23:08:33 +0000 (GMT)
	(envelope-from wigglesworth02@comcast.net)
Received: from [192.168.2.55]
	(c-24-125-177-237.hsd1.va.comcast.net[24.125.177.237])
	by comcast.net (sccrmhc11) with SMTP
	id <2005041723083201100hmlnbe>; Sun, 17 Apr 2005 23:08:32 +0000
From: Martes G Wigglesworth <wigglesworth02@comcast.net>
To: Hackers-list-bsd <freebsd-hackers@freebsd.org>,
	Norfolk Unix Users' Group <twuug@twuug.org>,
	freebsd-questions <freebsd-questions-request@freebsd.org>,
	Bluetooth <freebsd-bluetooth@freebsd.org>
Content-Type: text/plain
Message-Id: <1113779315.669.266.camel@Mobil1.276NET>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Sun, 17 Apr 2005 19:08:35 -0400
Content-Transfer-Encoding: 7bit
Subject: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF
	adapter...
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: wigglesworth02@comcast.net
List-Id: Using Bluetooth in FreeBSD environments
	<freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>,
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>,
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Apr 2005 23:08:34 -0000

I am having difficulties using my CF/PCCard Bluetooth adapter from
Ambicom.  I have found similar error messages, associated with an
individual that was attempting to get his palm to sync with BSD, back in
2003.  The respondent to the individual's inquiry, indicated a patch,
and the subsequent response was that the patch worked.  I am unable to
locate the archived mail, via google, however, I am new to patching, and
have not yet been able to figure out where I might do so.  I get
continuous loop of errors when attempting to use the rc.bluetooth
script, or hcseriald with the correct ttyd4 device.  

Can anyone indicate where I might find a way to patch this problem, or
if I may be able to edit some src, that has to do with this device
interface driver? (sio4)

I get the following in my dmesg output while executing the following:

>hcseriald -d -f /dev/ttyd4 -n sio4 -s 115200

>ng_h4_input: sio4 - ignoring unknown packet type=0
>ng_h4_input: sio4 - ignoring unknown packet type=0x80

>dmesg output for the connection renders the following: 
>sio4: <Compact Flash Bluetooth Card> at port 0x3e8-0x3ef irq 11
>function 0 config 2 on pccard1
>sio4: type 16550A
>sio4: unable to activate interrupt in fast mode - using normal mode

I am stuck, and unable to get any farther than the start of hcseriald. 
I am unable to use my bluetooth at all, because I am unable to even find
a good howto for using hcseriald or even how I am supposed to connect
the interface even if I can use hcseriald.  Nothing ever happens other
than the output listed above.

my system is as follows:

FreeBSD 5.3-Release
Bluetooth CF Adapter: Ambicom BT2000 via PCCard CF adapter
Asus M6BN 

Please give some direction.  I am at a loss.