From: Marcel Holtmann <marcel@holtmann.org>
To: Andreas Gaufer <andreas.gaufer@blue-cell-networks.com>
Cc: Bluez Devel <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Link interrupted/destroyed by CC on other hci device
Date: Mon, 28 Jun 2004 22:15:45 +0200 [thread overview]
Message-ID: <1088453745.6030.89.camel@pegasus> (raw)
In-Reply-To: <20040628215642.516c0ff6.Andreas.Gaufer@blue-cell-networks.com>
Hi Andreas,
> I noticed that running OBEX Transfers on one hci device are interrupted
> (L2CAP link is destroyed) by a CC that is issued on a different hci dev.
>
>
> As far as i can see it only happens on T6xx Phones from SE but this is
> not for sure now. Im will start digging on this phenomina now.
>
> I would greatly appreciate hints or thoughts why this could happen.
I don't think that this can happen, but who knows for sure. Make binary
dump files and compare the timestamps of the two HCI devices.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-28 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 19:56 [Bluez-devel] Link interrupted/destroyed by CC on other hci device Andreas Gaufer
2004-06-28 20:15 ` Marcel Holtmann [this message]
2004-06-29 8:41 ` Andreas Gaufer
2004-06-29 17:51 ` 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=1088453745.6030.89.camel@pegasus \
--to=marcel@holtmann.org \
--cc=andreas.gaufer@blue-cell-networks.com \
--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