From: George <george.news@gmx.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Bluez BNEP connection close
Date: Wed, 26 Jan 2005 19:18:51 +0100 [thread overview]
Message-ID: <6.1.2.0.2.20050126191747.04a84710@pop.gmx.net> (raw)
In-Reply-To: <1106656339.8058.143.camel@pegasus>
Hi again...
With the PCMCIA card is much more stable. For the moment it only has
crashed one or twice when stressing the channel throughput.
Thanks for all the help.
Regards
At 13:32 25/01/2005, Marcel Holtmann wrote:
>Hi George,
>
>> In my code I have a reconnection capability once the bnep connection
>> disappears.
>> However doing some more tests I found that sometimes the interface
bnep0 is
>> still there (in the laptop) although there is no connectivity.
>> I mean, the interface exists but the channel or path is not more up.
>> Therefore my reconnection capability doesn't work on this case.
>
>this is maybe a bug or a little race in the code. Include more details
>and actually are way to reproduce it.
>
>> So... don't know what could happen. I have recompiled the kernel serveral
>> times changing the UCHI, OHCI and EHCI supports but still happens the
same..
>
>Recompiling the kernel doesn't help here. You need to exchange the USB
>host controller hardware for checking UHCI, OHCI or EHCI. I always have
>a second PCI USB controller in my system for these tests.
>
>> I'm thinking on buying a PCMCIA Bluetooth card to have a try as Marcel
>> thinks the problem is with the usb.
>
>It is worth testing, but don't ask for the best PCMCIA card. This is
>always another story. In general every card is working, but you must now
>the exact hciattach parameter to make them work.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
>Tool for open source databases. Create drag-&-drop reports. Save time
>by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
>Download a FREE copy at http://www.intelliview.com/go/osdn_nl
>_______________________________________________
>Bluez-users mailing list
>Bluez-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-26 18:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 16:06 [Bluez-users] Bluez BNEP connection close George
2005-01-24 15:49 ` Marcel Holtmann
2005-01-24 16:46 ` George
2005-01-24 16:23 ` Michal Semler
2005-01-24 16:23 ` Marcel Holtmann
2005-01-24 17:04 ` George
2005-01-24 16:47 ` Marcel Holtmann
2005-01-24 17:33 ` George
2005-01-24 17:14 ` Marcel Holtmann
2005-01-24 18:24 ` George
2005-01-24 18:04 ` Marcel Holtmann
2005-01-24 18:37 ` George
2005-01-25 8:33 ` George
2005-01-25 12:32 ` Marcel Holtmann
2005-01-26 18:18 ` George [this message]
2005-01-24 18:10 ` Michael McConnell
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=6.1.2.0.2.20050126191747.04a84710@pop.gmx.net \
--to=george.news@gmx.net \
--cc=bluez-users@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