From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] H5 3 wire UART connect problem
Date: Wed, 06 Jul 2005 11:45:49 +0200 [thread overview]
Message-ID: <1120643149.8967.13.camel@pegasus> (raw)
In-Reply-To: <f16b04cf050706022079c5b876@mail.gmail.com>
Hi Hariharan,
> Please find her with the source modified for the H:5 3 WIRE UART
> Silicon wave dongle
> implementation in Bluez stack.
please send an unified diff for the hciattach changes.
Is this statement "3-Wire UART differs only with the protocol number
definitions" really true? If yes, it should be very easy to integrate
the 3-Wire UART support directly into hci_bcsp.c without any unneeded
overhead.
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-06 9:45 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
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 [this message]
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=1120643149.8967.13.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.