public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [Bluez-users] Motorola S9 and BlueZ 4.14
Date: Mon, 20 Oct 2008 17:53:47 -0300	[thread overview]
Message-ID: <2d5a2c100810201353v21a70714pb3c6fdc5aab4f54d@mail.gmail.com> (raw)
In-Reply-To: <4AA04BF6-26EE-488D-A22C-37855410E2F7@gmail.com>

Yes and no, it could be set to OPEN state before going really
connected, but it cannot emit the signal Connected otherwise
application will just try to get the fd which could not be available
thus a race condition could cause the problem. So if Connected signal
is mapped to OPEN state it wont work always. The problem could be that
the device simple want to go to STREAMING state which probably creates
the same situation on media transport, where headset and pulse are
competing to set the same state.

Im interested to know why the spec just don't say you need the
transport to be OPEN as the state means, since from CONFIGURED to OPEN
there is nothing else relevant to do regarding the state machine or
does it? Well for now we could just create yet another state so sink.c
could be notified when the transport is connected.


-- =

Luiz Augusto von Dentz
Engenheiro de Computa=E7=E3o

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great priz=
es
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=3D100&url=3D/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2008-10-20 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.81198.1224358186.3608.bluez-users@lists.sourceforge.net>
2008-10-18 19:48 ` [Bluez-users] Motorola S9 and BlueZ 4.14 Patryk Zawadzki
2008-10-18 20:40   ` Jelle de Jong
2008-10-19 15:55     ` [Bluez-devel] " Patryk Zawadzki
2008-10-19 16:09       ` Patryk Zawadzki
2008-10-19 16:35         ` Johan Hedberg
2008-10-19 16:54           ` Patryk Zawadzki
2008-10-19 17:06             ` Patryk Zawadzki
2008-10-19 17:16               ` Johan Hedberg
2008-10-20 20:53           ` Luiz Augusto von Dentz [this message]
2008-10-20 21:05             ` Johan Hedberg

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=2d5a2c100810201353v21a70714pb3c6fdc5aab4f54d@mail.gmail.com \
    --to=luiz.dentz@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