Date: Mon, 18 Apr 2005 17:10:06 -0400 From: Martes G Wigglesworth <wigglesworth02@comcast.net> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net>, Bluetooth <freebsd-bluetooth@freebsd.org> Subject: Re: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF adapter... Message-ID: <1113858606.651.10.camel@Mobil1.276NET> In-Reply-To: <4263E1E0.1000303@savvis.net> References: <1113779315.669.266.camel@Mobil1.276NET> <42630AE5.2070909@savvis.net> <1113798969.651.5.camel@Mobil1.276NET> <4263E1E0.1000303@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 on what is needed to patch as you have indicated? I really want to get 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. 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1113858606.651.10.camel>