From: Marcel Holtmann <marcel@holtmann.org>
To: Rognlien Dag Kristian <Dag.K.Rognlien@sintef.no>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] tcsendbreak and flow control on hciattach (csr chip)
Date: Fri, 08 Oct 2004 12:04:17 +0200 [thread overview]
Message-ID: <1097229854.4893.4.camel@pegasus> (raw)
In-Reply-To: <39417DF3286A66428FA558987839F44F152D99@SINTEFXCH01.sintef.no>
Hi Dag,
> If I enable both flow control and send break with hciattach:
> hciattach -b ttyS1 csr 921600 flow
>
> The unit fails to initialize. This does not happen if I disable flow
> control, or send break.
> The problem is also solved by setting a sleep of 0.5 seconds after the
> tcsendbreak command in the hciattach.c code.
>
> This is on an Intel XScale platform.
>
> I use bluez libs and bluez utils 2.9 on a 2.4.21 kernel with the mh9
> patch.
>
> Any ideas for another solution than the usleep, or is this the best
> solution?
maybe this is CSR specific, I don't know. Actually I wasn't aware of
that the -b option is really used. However if the 0.5 seconds sleep is
needed then send me a patch for it and I will apply it.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-10-08 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 9:14 [Bluez-devel] tcsendbreak and flow control on hciattach (csr chip) Rognlien Dag Kristian
2004-10-08 10:04 ` Marcel Holtmann [this message]
2004-10-09 9:30 ` David Woodhouse
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=1097229854.4893.4.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Dag.K.Rognlien@sintef.no \
--cc=bluez-devel@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