public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mingfan.Lu" <lucharse@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] About concurrency sdp_connect
Date: Wed, 27 Sep 2006 15:53:01 +0800	[thread overview]
Message-ID: <3f5a9ba20609270053o46cb0ebapaca698778f277c9b@mail.gmail.com> (raw)
In-Reply-To: <1159304948.800.39.camel@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 1374 bytes --]

holtman,
  I have test the pathc on 2.6.18-mh3
  When I use the dongle(bluetooth spec. 1.2), it seemed ok.
  but for the dongle (bluetooth spec. 1.1), it wasn't useful.


2006/9/27, Marcel Holtmann <marcel@holtmann.org>:
>
> Hi Peter,
>
> > my last attempt to make this work actually failed, but I didn't put much
> > energy into it. Feel free to come up with a working version. The path
> > how to handle this is clear.
>
> forget whatever I told you to handle this inside L2CAP. It is nearly
> impossible to get the locking for this right. I crashed my Quad G5
> multiple times today.
>
> So I went back to fix this inside the HCI layer. You can apply the
> attached patch on top of 2.6.18-mh3 and it should give you concurrent
> connect support for all protocols.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>
>


-- 
With respects,
   Mingfan.Lu

[-- Attachment #1.2: Type: text/html, Size: 2303 bytes --]

[-- Attachment #2: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-09-27  7:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  4:22 [Bluez-devel] About concurrency sdp_connect Mingfan.Lu
2006-09-14  9:04 ` Peter Wippich
2006-09-14 11:45   ` Fabrizio Guglielmino
2006-09-14 12:01     ` Peter Wippich
2006-09-14 12:17       ` Fabrizio Guglielmino
2006-09-14 12:30         ` Peter Wippich
2006-09-15  9:44           ` Marcel Holtmann
2006-09-15  9:54             ` Fabrizio Guglielmino
2006-09-15 11:37               ` Peter Wippich
2006-09-26 21:09             ` Marcel Holtmann
2006-09-27  7:53               ` Mingfan.Lu [this message]
2006-09-27  7:57                 ` Marcel Holtmann
2006-09-29 14:18                   ` 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=3f5a9ba20609270053o46cb0ebapaca698778f277c9b@mail.gmail.com \
    --to=lucharse@gmail.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