[Bluez-devel] problems with nc6 with bluez support

[Bluez-devel] problems with nc6 with bluez support

[Mauro Tortonesi]

hi to everybody,

i have just modified nc6 (an advanced IPv6-enabled nc clone) to support 
connections over bluetooth. normal connections over l2cap seem to work fine 
(although i have not been able to tranfer audio data over l2cap yet) but when 
i try to perform data tranfers over sco the 

i am using kernel 2.4.25-pre6 and 2.4.22 on my test hosts. perhaps i should 
switch to 2.6-series kernels? i am not sure about this, since l2test and 
scotest from bluez-utils 2.3 seem to work fine on these kernel.


P.S.: i have not officially released the bluez-enabled version of nc6 yet, but 
      if you are interested you can find the latest cvs sources here:

      http://cvs.deepspace6.net/view/nc6

-- 
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




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] problems with nc6 with bluez support

[Marcel Holtmann]

Hi Mauro,

> i have just modified nc6 (an advanced IPv6-enabled nc clone) to support 
> connections over bluetooth. normal connections over l2cap seem to work fine 
> (although i have not been able to tranfer audio data over l2cap yet) but when 
> i try to perform data tranfers over sco the 

looks like nice stuff and if I find some extra time I will test it. But
you should forget about the SCO transfers. SCO is for audio transmission
(voice) only. Use L2CAP (SOCK_SEQPACKET) and RFCOMM (SOCK_STREAM).

> i am using kernel 2.4.25-pre6 and 2.4.22 on my test hosts. perhaps i should 
> switch to 2.6-series kernels? i am not sure about this, since l2test and 
> scotest from bluez-utils 2.3 seem to work fine on these kernel.

The 2.4.25-pre6 is still fine. If you get a problem with a 2.4 kernel
apply the latest of my -mh patches.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] problems with nc6 with bluez support

[Mauro Tortonesi]

On Thursday 22 January 2004 10:42, Mauro Tortonesi wrote:
> hi to everybody,
>
> i have just modified nc6 (an advanced IPv6-enabled nc clone) to support
> connections over bluetooth. normal connections over l2cap seem to work fine
> (although i have not been able to tranfer audio data over l2cap yet) but
> when i try to perform data tranfers over sco the

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?

> i am using kernel 2.4.25-pre6 and 2.4.22 on my test hosts. perhaps i should
> switch to 2.6-series kernels? i am not sure about this, since l2test and
> scotest from bluez-utils 2.3 seem to work fine on these kernel.
>
>
> P.S.: i have not officially released the bluez-enabled version of nc6 yet,
> but if you are interested you can find the latest cvs sources here:
>
>       http://cvs.deepspace6.net/view/nc6

-- 
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





-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] problems with nc6 with bluez support

[Marcel Holtmann]

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. But show us the output of
"hciconfig hci0 version" and "hciconfig hci0 revision" (as root).

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] problems with nc6 with bluez support

[Mauro Tortonesi]

On Thursday 22 January 2004 11:27, you wrote:
> Hi Mauro,
>
> > i have just modified nc6 (an advanced IPv6-enabled nc clone) to support
> > connections over bluetooth. normal connections over l2cap seem to work
> > fine (although i have not been able to tranfer audio data over l2cap yet)
> > but when i try to perform data tranfers over sco the
>
> looks like nice stuff and if I find some extra time I will test it.

yes, IMVHO it is nice indeed. unfortunately, i haven't added 
configuration-time checks for Bluez yet, so if anyone of you wants to try nc6 
with bluetooth, he'll have to edit src/Makefile and add -DHAVE_BLUEZ to DEFS 
and -lbluetooth to LDFLAGS.

i was thinking about adding something like the following test to configure.ac 
to check if the system supports bluez:

bluez=yes
PROTO_BLUEZ(
  [
    AC_CHECK_LIB(bluetooth, baswap, , bluez=no)
  ],
  [
    AC_MSG_NOTICE([Disabling Bluetooth support: PF_BLUETOOTH protocol family 
is required])
    bluez=no
  ]
)

where PROTO_BLUEZ is defined in this way:

AC_DEFUN([PROTO_BLUEZ],[
  AC_CACHE_CHECK([for Bluetooth support], [ds6_cv_proto_bluez],[
    AC_TRY_CPP([
#include <sys/types.h>
#include <sys/socket.h>

#ifndef PF_BLUETOOTH
#error Missing PF_BLUETOOTH
#endif
#ifndef AF_BLUETOOTH
#error Mlssing AF_BLUETOOTH
#endif
    ],[
      ds6_cv_proto_bluez=yes
    ],[
      ds6_cv_proto_bluez=no
    ])
  ])

  if test "X$ds6_cv_proto_bluez" = "Xyes"; then :
    $1
  else :
    $2
  fi
])

what do you think about it?

> But you should forget about the SCO transfers. SCO is for audio transmission
> (voice) only. Use L2CAP (SOCK_SEQPACKET) and RFCOMM (SOCK_STREAM).

in fact i just wanted to perform audio transmission.

i have written the audioread application, that reads an oggvorbis file, 
decodes it and writes the PCM samples to stdout, and the audiotest 
application, that reads PCM samples from stdin and writes them to /dev/dsp.

so i was testing audio transfers by issuing this command on the server host:

nc6 -b -l -p 10 | audiotest
(nc6 -b -l --sco | audiotest for SCO)

and this command on the client host:

audioread file.ogg | nc6 -b 00:0D:88:8E:CA:07 10
(audioread file.ogg | nc6 -b --sco 00:0D:88:8E:CA:07 for SCO)

i must have made something wrong, since all the audio transfer tests i've made 
failed.

> > i am using kernel 2.4.25-pre6 and 2.4.22 on my test hosts. perhaps i
> > should switch to 2.6-series kernels? i am not sure about this, since
> > l2test and scotest from bluez-utils 2.3 seem to work fine on these
> > kernel.
>
> The 2.4.25-pre6 is still fine. If you get a problem with a 2.4 kernel
> apply the latest of my -mh patches.

so are you suggesting to stick to 2.4 for the moment? i have been using 2.6 on 
my laptop for the last 5 months and i am really enthusiastic about it ;-)

-- 
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

Re: [Bluez-devel] problems with nc6 with bluez support

[Mauro Tortonesi]

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

Re: [Bluez-devel] problems with nc6 with bluez support

[Marcel Holtmann]

Hi Mauro,

> yes, IMVHO it is nice indeed. unfortunately, i haven't added 
> configuration-time checks for Bluez yet, so if anyone of you wants to try nc6 
> with bluetooth, he'll have to edit src/Makefile and add -DHAVE_BLUEZ to DEFS 
> and -lbluetooth to LDFLAGS.
> 
> i was thinking about adding something like the following test to configure.ac 
> to check if the system supports bluez:
> 
> bluez=yes
> PROTO_BLUEZ(
>   [
>     AC_CHECK_LIB(bluetooth, baswap, , bluez=no)
>   ],
>   [
>     AC_MSG_NOTICE([Disabling Bluetooth support: PF_BLUETOOTH protocol family 
> is required])
>     bluez=no
>   ]
> )
> 
> where PROTO_BLUEZ is defined in this way:
> 
> AC_DEFUN([PROTO_BLUEZ],[
>   AC_CACHE_CHECK([for Bluetooth support], [ds6_cv_proto_bluez],[
>     AC_TRY_CPP([
> #include <sys/types.h>
> #include <sys/socket.h>
> 
> #ifndef PF_BLUETOOTH
> #error Missing PF_BLUETOOTH
> #endif
> #ifndef AF_BLUETOOTH
> #error Mlssing AF_BLUETOOTH
> #endif
>     ],[
>       ds6_cv_proto_bluez=yes
>     ],[
>       ds6_cv_proto_bluez=no
>     ])
>   ])
> 
>   if test "X$ds6_cv_proto_bluez" = "Xyes"; then :
>     $1
>   else :
>     $2
>   fi
> ])
> 
> what do you think about it?

I must admit that I am not an autoconf expert, so my rule is that as
long as it works it is ok. A nice idea is to check for the sockaddr_*
definitions.

BTW please post a diff of nc6 that adds the Bluetooth support. This will
make it easier for me to audit your code.

> > But you should forget about the SCO transfers. SCO is for audio transmission
> > (voice) only. Use L2CAP (SOCK_SEQPACKET) and RFCOMM (SOCK_STREAM).
> 
> in fact i just wanted to perform audio transmission.
> 
> i have written the audioread application, that reads an oggvorbis file, 
> decodes it and writes the PCM samples to stdout, and the audiotest 
> application, that reads PCM samples from stdin and writes them to /dev/dsp.
> 
> so i was testing audio transfers by issuing this command on the server host:
> 
> nc6 -b -l -p 10 | audiotest
> (nc6 -b -l --sco | audiotest for SCO)
> 
> and this command on the client host:
> 
> audioread file.ogg | nc6 -b 00:0D:88:8E:CA:07 10
> (audioread file.ogg | nc6 -b --sco 00:0D:88:8E:CA:07 for SCO)
> 
> i must have made something wrong, since all the audio transfer tests i've made 
> failed.

The audio stuff is not very easy if you do SCO over HCI over USB. You
have to check if your dongle sends the SCO traffic over the HCI layer.
Then you really need the latest 2.4.25-pre kernel or you have to apply
one of my -mh patches.

> so are you suggesting to stick to 2.4 for the moment? i have been using 2.6 on 
> my laptop for the last 5 months and i am really enthusiastic about it ;-)

If you want to use SCO with an USB Bluetooth dongle? Yes, you must stick
to 2.4 until the SCO problem is solved. Of course if you own an OHCI USB
host adapater you can give 2.6 a try, but the UHCI will fail and crash
your system.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] problems with nc6 with bluez support

[Marcel Holtmann]

Hi Mauro,

> what do you mean when you say that SCO is not for data transfer? what are the 
> limits of SCO sockets?

this is not a limit of the SCO socket, it is a limit of the Bluetooth
design itself. A SCO link can have a different air coding and it is
possible that packets get dropped. The mailing list archive for more
details on it. The guys from CSR explained this very well.

> 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.

Install the latest bluez-libs and bluez-utils and do it again. Or use
the scoinfo utility from my website.

The Anycom dongle is problematic, because of the Transilica chip. I
don't know anything special about it. Please show us the content of
/proc/bus/usb/devices.

> BTW: clearly, when the usb/bluez subsystem hangs after trying to perform sco 
> transfers, hciconfig does not recognize any bluetooth interface.

What kind of USB chipset do you use? I heard of some problems with VIA
or ALI chipsets (can't remember what manufacturer it was).

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] problems with nc6 with bluez support

[Mauro Tortonesi]

On Thursday 22 January 2004 12:38, Marcel Holtmann wrote:
> Hi Mauro,
>
> I must admit that I am not an autoconf expert, so my rule is that as
> long as it works it is ok. A nice idea is to check for the sockaddr_*
> definitions.
>
> BTW please post a diff of nc6 that adds the Bluetooth support. This will
> make it easier for me to audit your code.

i have added configuration-time detection of bluez to nc6 and i have just 
merged the changes in the nc6 cvs repository:

http://cvs.deepspace6.net/view/nc6


> > > But you should forget about the SCO transfers. SCO is for audio
> > > transmission (voice) only. Use L2CAP (SOCK_SEQPACKET) and RFCOMM
> > > (SOCK_STREAM).
> >
> > in fact i just wanted to perform audio transmission.
> >
> > i have written the audioread application, that reads an oggvorbis file,
> > decodes it and writes the PCM samples to stdout, and the audiotest
> > application, that reads PCM samples from stdin and writes them to
> > /dev/dsp.
> >
> > so i was testing audio transfers by issuing this command on the server
> > host:
> >
> > nc6 -b -l -p 10 | audiotest
> > (nc6 -b -l --sco | audiotest for SCO)
> >
> > and this command on the client host:
> >
> > audioread file.ogg | nc6 -b 00:0D:88:8E:CA:07 10
> > (audioread file.ogg | nc6 -b --sco 00:0D:88:8E:CA:07 for SCO)
> >
> > i must have made something wrong, since all the audio transfer tests i've
> > made failed.
>
> The audio stuff is not very easy if you do SCO over HCI over USB. You
> have to check if your dongle sends the SCO traffic over the HCI layer.
> Then you really need the latest 2.4.25-pre kernel or you have to apply
> one of my -mh patches.

ok, thanks. i'll try to figure this out.


> > so are you suggesting to stick to 2.4 for the moment? i have been using
> > 2.6 on my laptop for the last 5 months and i am really enthusiastic about
> > it ;-)
>
> If you want to use SCO with an USB Bluetooth dongle? Yes, you must stick
> to 2.4 until the SCO problem is solved. Of course if you own an OHCI USB
> host adapater you can give 2.6 a try, but the UHCI will fail and crash
> your system.

very interesting. do you think there is a bug in the UHCI code which is 
related to isochronous traffic type? see this thread:

http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107238134310638&w=2

i am asking this because a friend of mine (fabio coatti, included in cc) has a 
dlink dbt120 usb dongle (hardware revision b2) and if he compiles the 2.6 
kernel with sco support over hci_usb he gets an oops each time he unplugs the 
dongle. IIRC, the crash happens only if he has hcid and sdpd running. 

oddly enough, with the same kernel and the same dbt120 usb dongle (although 
hardware revision b3) i had no such problems on my laptop. i don't know if 
this depends from the chipsets (i have an intel 815P and he has a brand new 
intel i875P), but it is sure worth investigating.

BTW: marcel & max, can i ask you what tools you use to debug your bluetooth 
kernel code? printk? kgdb? kdb?

-- 
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

Re: [Bluez-devel] problems with nc6 with bluez support

[Mauro Tortonesi]

[-- Attachment #1: Type: text/plain, Size: 4213 bytes --]

On Thursday 22 January 2004 12:44, you wrote:
> Hi Mauro,
>
> > what do you mean when you say that SCO is not for data transfer? what are
> > the limits of SCO sockets?
>
> this is not a limit of the SCO socket, it is a limit of the Bluetooth
> design itself. A SCO link can have a different air coding and it is
> possible that packets get dropped. The mailing list archive for more
> details on it. The guys from CSR explained this very well.

do you mean this thread:

http://sourceforge.net/mailarchive/message.php?msg_id=6447630

?

> > 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.
>
> Install the latest bluez-libs and bluez-utils and do it again. Or use
> the scoinfo utility from my website.

here it is. for the dlink dbt120 usb dongle:

[root@giskard test]# 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 test]# 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
        Chip version: BlueCore02
        Max key size: 56 bit
        SCO mapping:  HCI

for the anycom 220 usb dongle:

[root@giskard test]# 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 test]# hciconfig hci0 revision
hci0:   Type: USB
        BD Address: 00:0A:9A:00:EB:B5 ACL MTU: 339:4  SCO MTU: 64:0
        Unsupported manufacturer

> The Anycom dongle is problematic, because of the Transilica chip. I
> don't know anything special about it. Please show us the content of
> /proc/bus/usb/devices.

it is included in attachment.

> > BTW: clearly, when the usb/bluez subsystem hangs after trying to perform
> > sco transfers, hciconfig does not recognize any bluetooth interface.
>
> What kind of USB chipset do you use? I heard of some problems with VIA
> or ALI chipsets (can't remember what manufacturer it was).

i have an epox 8K5A mainboard with a VIA KT333 chipset. the usb chip is a VIA 
VT8235:

[mauro@giskard mauro]$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
[...]
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
[...]


-- 
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




[-- Attachment #2: usbdevices.txt --]
[-- Type: text/plain, Size: 1773 bytes --]

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc= 27/900 us ( 3%), #Int=  1, #Iso=  2
D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB UHCI-alt Root Hub
S:  SerialNumber=a400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=16 #Cfgs=  1
P:  Vendor=0f4d ProdID=1000 Rev= 4.01
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr= 26mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E:  Ad=84(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=05(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E:  Ad=84(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=05(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E:  Ad=84(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=05(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E:  Ad=84(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=05(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E:  Ad=84(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=05(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
E:  Ad=84(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=05(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms

Re: [Bluez-devel] problems with nc6 with bluez support

[Marcel Holtmann]

Hi Mauro,

> very interesting. do you think there is a bug in the UHCI code which is 
> related to isochronous traffic type? see this thread:
> 
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107238134310638&w=2
> 
> i am asking this because a friend of mine (fabio coatti, included in cc) has a 
> dlink dbt120 usb dongle (hardware revision b2) and if he compiles the 2.6 
> kernel with sco support over hci_usb he gets an oops each time he unplugs the 
> dongle. IIRC, the crash happens only if he has hcid and sdpd running. 

I haven't seen this crash on an OHCI host adapter, but I can't proof
that this is an UHCI problem. The USB guys are informed about that
problem and I hope they find the answer.

> oddly enough, with the same kernel and the same dbt120 usb dongle (although 
> hardware revision b3) i had no such problems on my laptop. i don't know if 
> this depends from the chipsets (i have an intel 815P and he has a brand new 
> intel i875P), but it is sure worth investigating.

Yes, of course. Every help to track this problem is welcome. Please post
bug reports or patches to the USB developer mailing list.

> BTW: marcel & max, can i ask you what tools you use to debug your bluetooth 
> kernel code? printk? kgdb? kdb?

I use the good old printk ;)

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] problems with nc6 with bluez support

[Marcel Holtmann]

Hi Mauro,

> > this is not a limit of the SCO socket, it is a limit of the Bluetooth
> > design itself. A SCO link can have a different air coding and it is
> > possible that packets get dropped. The mailing list archive for more
> > details on it. The guys from CSR explained this very well.
> 
> do you mean this thread:
> 
> http://sourceforge.net/mailarchive/message.php?msg_id=6447630

no, there was another one, that explained why it is hard (mostly
impossible) to use SCO for data transfers.

> here it is. for the dlink dbt120 usb dongle:
> 
> [root@giskard test]# 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 test]# 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
>         Chip version: BlueCore02
>         Max key size: 56 bit
>         SCO mapping:  HCI

This is fine and should work.

> for the anycom 220 usb dongle:
> 
> [root@giskard test]# 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 test]# 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 don't know if they map SCO over HCI or over PCM by default. From the
USB descriptor output it seems that they got this right, so it should be
no problem. But I don't know of anyone who had done sucessful SCO audio
transfers over HCI with other chips than CSR.

> i have an epox 8K5A mainboard with a VIA KT333 chipset. the usb chip is a VIA 
> VT8235:
> 
> [mauro@giskard mauro]$ lspci
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
> [...]
> 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
> 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
> 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
> 00:11.1 IDE interface: VIA Technologies, Inc. 
> VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
> [...]

Try the latest 2.4.25-pre and see if it works. I work with Intel and NEC
USB host adapters and never got a problem.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel