All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrizio Guglielmino <guglielmino@infitsrl.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] It's rfcomm connect problem
Date: Sat, 22 Jul 2006 16:08:08 +0200	[thread overview]
Message-ID: <2172AACE-61A5-4D43-90E2-059D659D8830@infitsrl.com> (raw)
In-Reply-To: <1153356539.4094.9.camel@aeonflux.holtmann.net>

Hi all,
I made some investigation about the BtOBEX_TransportConnect signaled  
to the list and Marcel some days before.
Openobex isn't involved in the problem, in my try I've writed from  
scatch a simple obex push client (not using openobex but only
socket).
In my test I found this : if there are two thread (also two process)  
making something like

  ...
  ret = connect(fd, (struct sockaddr *)dst, sizeof(struct sockaddr_rd));
  ...

in simultaneous way the second always fail (return -1). I've also  
tryed to "protect" the connect using a mutex and all works
but (naturally) second connection result conditioned to the frist  
(syncronous so thread it is not useful).

I think there is some solution to this but I don't know if it's using  
some ioctl on socket (nonbloking?) or some hci command to adapter.
Please can some one give me some hint?

I'm looking at kernel source related to rfcomm (/usr/src/ 
linux-2.6.116/net/bluetooth/rfcomm/*.c) but I'm not sure the problem  
reside here...


thanks, bye
Fabrizio 

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

  parent reply	other threads:[~2006-07-22 14:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 16:28 [Bluez-devel] Error: sdptool browse --> Connection reset by peer JP Freeley
2006-07-20  0:48 ` Marcel Holtmann
2006-07-20 21:27   ` JP Freeley
2006-07-25  4:26     ` JP Freeley
2006-07-22 14:08   ` Fabrizio Guglielmino [this message]
2006-07-24  8:38     ` [Bluez-devel] It's rfcomm connect problem Andreas Gaufer
2006-07-24 13:33       ` Fabrizio Guglielmino
2006-07-24 13:56         ` Andreas Gaufer
2006-07-24 16:35           ` Marcel Holtmann
2006-07-24 18:34             ` Andreas Gaufer
2006-07-24 20:30               ` Fabrizio Guglielmino
2006-07-24 21:12                 ` Marcel Holtmann
2006-07-27  9:04                   ` Fabrizio Guglielmino
2006-07-27  9:25                     ` [Bluez-devel] It's rfcomm connect problem [ERRATA] Fabrizio Guglielmino
2006-07-28 11:14                     ` [Bluez-devel] It's rfcomm connect problem Marcel Holtmann
2006-07-31 10:02                       ` [Bluez-devel] About l2cap patch to handle multiple connections Fabrizio Guglielmino
2006-07-31 14:14                         ` Marcel Holtmann
2006-08-02 11:24                           ` Fabrizio Guglielmino
2006-08-02 13:43                             ` 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=2172AACE-61A5-4D43-90E2-059D659D8830@infitsrl.com \
    --to=guglielmino@infitsrl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.