public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: cijoml@volny.cz
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ error in cc,cc,dc sequence
Date: Sat, 17 Apr 2004 10:07:15 +0200	[thread overview]
Message-ID: <1082189235.4489.46.camel@pegasus> (raw)
In-Reply-To: <200404170957.35029.cijoml@volny.cz>

Hi Michal,

> > > when calling cc/dc/cc/dc/cc/dc it works like a charm
> > > but cc/cc/dc makes problems - can't disconnect
> >
> > maybe the kernel or your Bluetooth chip don't really likes double
> 
> kernel 2.4.26-mh1 and CSR 16.1.1 - Microsoft wireless transceiver

if it is really a kernel problem then it is present in every kernel,
because I never worked on it.

Regards

Marcel




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

  reply	other threads:[~2004-04-17  8:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 21:39 [Bluez-users] BlueZ error in cc,cc,dc sequence Michal Semler (volny.cz)
2004-04-16 23:49 ` Marcel Holtmann
2004-04-17  7:37   ` Michal Semler (volny.cz)
2004-04-17  7:45     ` Marcel Holtmann
2004-04-17  7:57       ` Michal Semler (volny.cz)
2004-04-17  8:07         ` Marcel Holtmann [this message]
2004-04-17  8:22           ` Michal Semler (volny.cz)
2004-04-17  9:03             ` 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=1082189235.4489.46.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=cijoml@volny.cz \
    /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