From: hariharan veerappan <hariharanneevee@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] H5 3 wire UART connect problem
Date: Fri, 1 Jul 2005 16:19:31 +0530 [thread overview]
Message-ID: <f16b04cf05070103496a3e64e6@mail.gmail.com> (raw)
In-Reply-To: <1120213256.15397.187.camel@pegasus>
Hello all,
If we wish to study some basic fundamentals of development.
Can any body advise whether any tutorials available for H5 UART (3 WIRE UAR=
T)
on bluez. Tell me the any website link for better solution for our developm=
ent.
Thanks and regards
Hariharan.v
On 7/1/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Hariharan,
>=20
> > we wants to develop and implement the 3 WIRE UART support for the
> > Bluez Stack. can any one suggest an idea to develop and implement
> > 3 WIRE UART in BlueZ.
> >
> > May i follow the H4 UART Implementation with Some modifications related=
with
> > H5 (3 WIRE UART). We came to know that Packets has to be added before a=
nd after
> > the HCI commands according to H4 and H5 UART. Is it right ?.
> >
> > We wish to know that whether it takes major development cycle.
> >
> > As per Silicon wave datasheet the 3 WIRE UART is compatible with BCSP.
> > May we have to follow the H4 UART or BCSP one for our development.
>=20
> create a file drivers/bluetooth/hci_3wire.c and start with BCSP as base.
> In general you can do a driver that supports BCSP and 3-Wire at the same
> time, but actually I really like to have two separate drivers. Try to
> start from scratch and don't copy too much things. The second part is
> adding support for 3-Wire to the hciattach program.
>=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
next prev parent reply other threads:[~2005-07-01 10:49 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 [this message]
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
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=f16b04cf05070103496a3e64e6@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