From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] H5 3 wire UART connect problem
Date: Mon, 04 Jul 2005 15:00:28 +0200 [thread overview]
Message-ID: <1120482028.10273.154.camel@pegasus> (raw)
In-Reply-To: <f16b04cf05070405392568477e@mail.gmail.com>
Hi Hariharan,
> Presently we are working in 3 WIRE UART Bluetooth transport protocol
> implementation.
> We are in implementation of 3 WIRE UART in hciattach.c.
>
> Our Specification:
> Linux kernel - 2.4.20.
this kernel version is a little bit problematic. Do your development
with the 2.6.12 kernel and then backport it. Otherwise nobody will
review it and it may become useless.
> Module - Solicon wave Serial port Bluetooth Module.
I can test it out with a Casira and a BlueCore4.
> In the HCI attach, We are following the procedure of given below.
>
> Host side -> SYNC Command -> BT Device
> Host side <- SYNC Response <- BT Device
> Host Side <- SYNC Command <- BT Device
> Host Side -> SYNC Response -> BT Device
> Host side <- Config Command <- BT Device
> Host side -> Config Response -> BT Device
>
> Here after the device does not respond for any of the commands
Actually I have no idea why that happens, but I also don't have any
Silicon Wave development kit at hand.
> Please advise us whether our command sequence for the HCI attach of 3 WIRE
> bluetooth device.
Check the specification. I have no idea.
> Our progress plan in the Implementation of H5 3 WIRE in Bluez.
> First we attach the module HCI layer with the bluez stack.
> Second we build the driver to usr 3 WIRE stack.
> our plan is a proper one or not. Advise.
You add the basic configuration stuff to hciattach like it was done for
BCSP and then you set the TTY line discipline to N_HCI and switch to the
3-Wire UART protocol. However this must be implemented in hci_3wire.c
and linked correctly into the hci_uart.ko driver. The complete protocol
handling then has to be done inside the kernel.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-07-04 13:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 15:35 [Bluez-users] H5 3 wire UART connect problem hariharan veerappan
2005-06-30 18:51 ` Marcel Holtmann
2005-07-01 9:49 ` hariharan veerappan
2005-07-01 10:20 ` Marcel Holtmann
2005-07-01 10:49 ` hariharan veerappan
2005-07-01 13:21 ` Marcel Holtmann
2005-07-04 6:07 ` hariharan veerappan
2005-07-04 12:32 ` hariharan veerappan
2005-07-04 12:39 ` hariharan veerappan
2005-07-04 13:00 ` Marcel Holtmann [this message]
2005-07-05 7:15 ` hariharan veerappan
2005-07-05 8:13 ` Marcel Holtmann
2005-07-06 9:20 ` hariharan veerappan
2005-07-06 9:45 ` Marcel Holtmann
2005-07-06 10:01 ` hariharan veerappan
2005-07-04 12:56 ` Marcel Holtmann
2005-07-01 10:22 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1120482028.10273.154.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox