From: Marcel Holtmann <marcel@holtmann.org>
To: Tony Lindgren <tony@atomide.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] AmbiCom BT2000C works with hciattach
Date: Wed, 23 Jun 2004 09:34:22 +0200 [thread overview]
Message-ID: <1087976062.4209.61.camel@pegasus> (raw)
In-Reply-To: <20040623031119.GA20367@atomide.com>
Hi Tony,
> Just FYI, there was some discussion here a while back on the
> AmbiCom BT2000C, which is different from the earlier BT2000
> models.
>
> Well turns out it works fine with serial_cs + hciattach:
>
> hciattach /dev/ttyS1 csr -s 57600 57600
> or
> hciattach /dev/ttyS1 csr -s 57600 460800
> hciconfig hci0 up
> hcitool scan
> ...
>
> Sorry if this was already old news :) Please CC me on any
> replies, I'm not subscribing.
how good these news are actually depends on what kernel you are using ;)
Send me the output of "dump_cis" and I will add a line to hciattach for
that. What is "hciconfig -a" saying?
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-23 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 3:11 [Bluez-devel] AmbiCom BT2000C works with hciattach Tony Lindgren
2004-06-23 7:34 ` Marcel Holtmann [this message]
2004-06-23 16:14 ` Tony Lindgren
2004-06-23 16:26 ` Marcel Holtmann
2004-06-23 16:45 ` Tony Lindgren
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=1087976062.4209.61.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=tony@atomide.com \
/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.