From: Pavel Ruzicka <pavouk@pavouk.org>
To: Eran <eran_l@over-here.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Ambicom BT2000E card, can't get hciattach to work
Date: Thu, 22 Apr 2004 11:24:33 +0200 [thread overview]
Message-ID: <200404221124.34165.pavouk@pavouk.org> (raw)
In-Reply-To: <4086FFD9.50104@over-here.org>
Hello,
> Sorry I forgot to mention it - but hciconfig shows a fully 'up and
> running' interface. I use the bt950_cs driver.
> I further checked and most hcitool commands work except the link quality.
I don't try link quality. It's possible, that this function doesn't work with
this driver or your BT devices doesn't have established connection.
> I Have tried removing the bluetooth.conf from my pcmcia/ directory and
> use hciattach with /dev/ttyS03, but no success here as well (could not
> find correct parameters). Why is it the preferred way?
Because there are more BT cards with BT950 uart and ericsson chipset which
supposedly works with serial_cs driver and hciattach.
It's better to have for all these cards only one universal driver.
It's possible, that BT2000E requires some special initialization which
hciattach doesn't know, but I'am not expert.
Best regards,
Pavel Ruzicka
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-04-22 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 20:47 [Bluez-users] Ambicom BT2000E card, can't get hciattach to work Eran
2004-04-21 22:27 ` Pavel Ruzicka
2004-04-21 23:12 ` Eran
2004-04-22 9:24 ` Pavel Ruzicka [this message]
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=200404221124.34165.pavouk@pavouk.org \
--to=pavouk@pavouk.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=eran_l@over-here.org \
/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