public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: hariharan veerappan <hariharanneevee@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] H5 3 wire UART connect problem
Date: Mon, 4 Jul 2005 11:37:46 +0530	[thread overview]
Message-ID: <f16b04cf0507032307413fcef@mail.gmail.com> (raw)
In-Reply-To: <1120224082.15397.197.camel@pegasus>

Hello all,

I am still newer to the development of bluetooth drivers.

Can any body suggest, from where can i get H5 - 3 WIRE Transport
interface protocol
informations.

Thanks and Regards
Hariharan.V

On 7/1/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Hriharan,
>=20
> > If we wish to study some basic fundamentals of development.
> > Can any body advise whether any tutorials available for H5 UART (3 WIRE=
 UART)
> > on bluez. Tell me the any website link for better solution for our deve=
lopment.
>=20
> look at the hci_h4.c and hci_bcsp.c files for examples. They show you
> how to use our HCI UART API. The number of lines of code are very small
> and it should be easy to understand what the callback functions are for.
> The hciattach.c is a little bit more freaky. I need to split it into
> more separate files for each transport or vendor.
>=20
> Regards
>=20
> Marcel
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> 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=3D7477&alloc_id=3D16492&op=3Dclic=
k
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>


-------------------------------------------------------
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

  reply	other threads:[~2005-07-04  6:07 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 [this message]
2005-07-04 12:32             ` hariharan veerappan
2005-07-04 12:39               ` hariharan veerappan
2005-07-04 13:00                 ` Marcel Holtmann
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=f16b04cf0507032307413fcef@mail.gmail.com \
    --to=hariharanneevee@gmail.com \
    --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