From: Marcel Holtmann <marcel@holtmann.org>
To: radoa <cat@pobox.sk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hci event bug for Nokia 7650
Date: Fri, 29 Oct 2004 20:11:24 +0200 [thread overview]
Message-ID: <1099073484.6912.0.camel@pegasus> (raw)
In-Reply-To: <loom.20041029T194010-621@post.gmane.org>
Hi Radoa,
> I was trying create L2CAP socket and make connection to Nokia 7650 phone,
> but L2CAP always timeouted after about 40 seconds. I started debugging and I
> discovered that bluez kernel during establishing L2CAP connection drops event
> packet 0x1B (Max Slots Change) from 7650 phone, so then after timeout 7650
> phone send Disconnection Complete (0x05) event. I debugged this in function
> hci_event_packet(). Is this bug, or is it something wrong with phone stack, or
> is somethig wrong with stack, if bug, what should I send for rejecting command,
> or better how respond for command? I need establish connection using L2CAP
> sockets.
about what Linux kernel version are we talking? What kind of L2CAP
socket do you try to open?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-10-29 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 17:50 [Bluez-devel] hci event bug for Nokia 7650 radoa
2004-10-29 18:11 ` Marcel Holtmann [this message]
2004-10-29 18:47 ` [Bluez-devel] " radoa
2004-10-29 19: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=1099073484.6912.0.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=cat@pobox.sk \
/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