From owner-freebsd-bluetooth@FreeBSD.ORG Tue Apr 19 16:53:16 2005 Return-Path: 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 0655A16A4CE for ; Tue, 19 Apr 2005 16:53:16 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B75A43D39 for ; Tue, 19 Apr 2005 16:53:15 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 769C33BF77; Tue, 19 Apr 2005 11:53:14 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26922-01-43; Tue, 19 Apr 2005 11:53:14 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id 3EBDE3BE25; Tue, 19 Apr 2005 11:53:14 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 19 Apr 2005 11:52:48 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 19 Apr 2005 11:52:30 -0500 Message-ID: <42653749.8090601@savvis.net> Date: Tue, 19 Apr 2005 09:52:25 -0700 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wigglesworth02@comcast.net References: <1113779315.669.266.camel@Mobil1.276NET> <42630AE5.2070909@savvis.net> <1113798969.651.5.camel@Mobil1.276NET> <4263E1E0.1000303@savvis.net> <1113858606.651.10.camel@Mobil1.276NET> In-Reply-To: <1113858606.651.10.camel@Mobil1.276NET> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Apr 2005 16:52:30.0217 (UTC) FILETIME=[2CB2F790:01C54500] X-Virus-Scanned: amavisd-new at savvis.net cc: Bluetooth Subject: Re: 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 List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 16:53:16 -0000 Martes, sorry for the delay. > Thanks for the response. I am just starting into the C-programming > stuff. I have some good books, but I won't be taking my C++ class until > the fall, so I am just winging it currently. Are there any good howtos that's fine. btw for this particular project you would not need c++. everything is written in c. > on what is needed to patch as you have indicated? I really want to get i do not think so. i would recommend to get a good unix programming book. something like Advanced Programming in the UNIX Environment, Addison-Wesley, 1992, ISBN 0-201-56317-7 > into this stuff, however, I am not well versed in programming operating > systems, yet. Any hints? I have downloaded the Architecure > Manual/Handbook, for FreeBSD, but I was hoping for a no frills > quick-start, for someone like myself. I have not found good information > on what in actually involved in patching the kernel. again, for this particular project, you probably wont have to patch the kernel. i need to change hcseriald(8) (which is a user-space daemon) so it would send extra initialization command to the device. since device looks like a serial port (modem) all i need to do is to send/receive few bytes to/from serial port. thanks, max > Thanks again, and will be waiting for that patch. > > On Mon, 2005-04-18 at 12:35, Maksim Yevmenkin wrote: > >>Martes, >> >> >>>Thanks for the info. I appologize for cross-posting, however, I have >>>been posting this problem on different lists for about a week, and no >>>responses came back, so I decided to multply my output in the hopes for >>>a response. >> >>hmmm... i must have missed it :( >> >> >>>Anyhow: >>> >>>When I attempt the rc.bluetooth script, I get the following: >>> >>> >>>>># sudo /etc/rc.bluetooth start sio4 >>>> >>>># >>>>#Could not execute command "reset". Operation timed out >> >>"reset" is the very first command in the initialization sequence. since >>it has timed out then communication between host and adapter is broken >>(for whatever reason). >> >>after google'ing a bit i found out that this particular card >> >>1. uses 16c950/954 uart, which is a good thing because it has 128 bytes >>fifo (compared to 16 bytes in 16c550a). you might want to try puc(4) >>driver that might have support for this uart. >> >>2. apparently needs extra initialization sequence. that is you need to >>send extra vendor specific command to the adapter to setup uart speed. >> >>my guess item (2) above is the reason why you got timeout in "reset". >>basically i need to prepare a patch for hcseriald(8) and send it to you. >>it will take me a few days to do that. since i do not have the card here >>i will rely on you to help me with testing. >> >>in the mean time you might want to try item (1) above to see if puc(4) >>driver works and recognize 16c950/954 uart. >> >>if you feel like hacking it yourself, you might want to take a look as >>linux bluez hciattach utility (online cvs >>http://cvs.sourceforge.net/viewcvs.py/bluez/utils/tools/hciattach.c?rev=1.29&view=markup). >>this utility does a similar (to hciseriald(8)) job. if you get it >>working please send me the patches and i will review and commit them. >> >> >>>I also find it extremely difficult to get anywhere when things don't work. Whenever I post to the appropriate list, >>>I get nothing. >> >>again, i must have missed it. i usually read bluetooth@ and mobile@ and >>look for bluetooth related questions. please use bluetooth@ list for all >>your bluetooth related questions. >> >> >>>In fact, your very needed response, only came in spite of my posts to Bluetooth, and Stable, where I would hope >>>I would be able to find such informed answers. >>> >>>Any tips on specific posts, such as mine? It is like people only want to talk about hacking stuff >>>that works already, and don't budge, when something needs repair, or explanation. >> >>it is better to post bluetooth related questions in bluetooth@ mailing list. >> >>thanks, >>max >> > >