Linux bluetooth development
 help / color / mirror / Atom feed
From: Mauro Tortonesi <mtortonesi@ing.unife.it>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] problems with nc6 with bluez support
Date: Thu, 22 Jan 2004 11:27:57 +0100	[thread overview]
Message-ID: <200401221127.57516.mtortonesi@ing.unife.it> (raw)
In-Reply-To: <200401221042.53134.mtortonesi@ing.unife.it>

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

  parent reply	other threads:[~2004-01-22 10:27 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 [this message]
2004-01-22 11:14   ` Marcel Holtmann
2004-01-22 11:31     ` Mauro Tortonesi
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=200401221127.57516.mtortonesi@ing.unife.it \
    --to=mtortonesi@ing.unife.it \
    --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