From: Mauro Tortonesi <mtortonesi@ing.unife.it>
To: Marcel Holtmann <marcel@holtmann.org>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] problems with nc6 with bluez support
Date: Thu, 22 Jan 2004 12:31:10 +0100 [thread overview]
Message-ID: <200401221231.10350.mtortonesi@ing.unife.it> (raw)
In-Reply-To: <1074770040.19046.1.camel@pegasus>
On Thursday 22 January 2004 12:14, you wrote:
> Hi Mauro,
>
> > sorry, i sent the email before it was finished :-( i was saying that when
> > i try to perform data tranfers over sco the bluez/usb subsystem on the
> > receiving host hangs: my dlink dbt120 usb dongle is shut down (the 2 leds
> > switch off) and the system does not recognize it anymore even if i unplug
> > it and plug it in again. and if i then replace the dlink dbt120 with an
> > anycom 220 usb dongle nothing changes: the green led of the anycom dongle
> > lits but the usb subsystem does not even recognize the peripheral.
> >
> > the system keeps refusing to recognize usb dongles even if i unload and
> > reload the hci_usb, bluez, sco and l2cap modules and the hcid and sdpd
> > daemons.
> >
> > how can i solve these problesm? do you have any clues?
>
> as already told, SCO is not for data transfer.
what do you mean when you say that SCO is not for data transfer? what are the
limits of SCO sockets?
> But show us the output of "hciconfig hci0 version" and "hciconfig hci0
> revision" (as root).
for the dlink dbt120 usb dongle:
[root@giskard root]# hciconfig hci0 version
hci0: Type: USB
BD Address: 00:0D:88:8E:CA:07 ACL MTU: 192:8 SCO MTU: 64:8
HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1 (0x1) LMP Subver: 0x1bb
Manufacturer: Cambridge Silicon Radio (10)
[root@giskard root]# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0D:88:8E:CA:07 ACL MTU: 192:8 SCO MTU: 64:8
HCI 15.3 (bc02x)
for the anycom 220 usb dongle:
[root@giskard root]# hciconfig hci0 version
hci0: Type: USB
BD Address: 00:0A:9A:00:EB:B5 ACL MTU: 339:4 SCO MTU: 64:0
HCI Ver: 1.1 (0x1) HCI Rev: 0x93 LMP Ver: 1.1 (0x1) LMP Subver: 0x93
Manufacturer: Transilica, Inc. (24)
[root@giskard root]# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0A:9A:00:EB:B5 ACL MTU: 339:4 SCO MTU: 64:0
Unsupported manufacturer
i am using hciconfig from bluez-utils 2.3.
BTW: clearly, when the usb/bluez subsystem hangs after trying to perform sco
transfers, hciconfig does not recognize any bluetooth interface.
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi mtortonesi@ing.unife.it
mauro@deepspace6.net
mauro@ferrara.linux.it
Deep Space 6 - IPv6 with Linux http://www.deepspace6.net
Ferrara Linux User Group http://www.ferrara.linux.it
next prev parent reply other threads:[~2004-01-22 11:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 9:42 [Bluez-devel] problems with nc6 with bluez support Mauro Tortonesi
2004-01-22 10:27 ` Marcel Holtmann
2004-01-22 11:21 ` Mauro Tortonesi
2004-01-22 11:38 ` Marcel Holtmann
2004-01-23 10:25 ` Mauro Tortonesi
2004-01-23 13:28 ` Marcel Holtmann
2004-01-22 10:27 ` Mauro Tortonesi
2004-01-22 11:14 ` Marcel Holtmann
2004-01-22 11:31 ` Mauro Tortonesi [this message]
2004-01-22 11:44 ` Marcel Holtmann
2004-01-23 11:18 ` Mauro Tortonesi
2004-01-23 13:35 ` Marcel Holtmann
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=200401221231.10350.mtortonesi@ing.unife.it \
--to=mtortonesi@ing.unife.it \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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