From: Stefan Mischke <survivor@uni-paderborn.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: read_RSSI and others not thread-safe?
Date: Fri, 08 Oct 2004 18:02:11 +0200 [thread overview]
Message-ID: <4166BA03.9050106@uni-paderborn.de> (raw)
In-Reply-To: <1097250057.4407.25.camel@pegasus>
Hi Marcel!
Ok, but I don't understand why my problem occurs. Look at this:
- thread T1 does hci_send_req(read_RSSI), waits for event E1
- thread T2 does hci_send_req(read_RSSI), waits for event E2
- Lets assume E2 comes earlier than E1
Why do BOTH threads receive E2? When is an event consumed?
Regards
Stefan
Marcel Holtmann schrieb:
>Hi Stefan,
>
>
>it is a raw socket and every process can get all events. It is not
>possible to prevent this and actually the HCI itself is not designed for
>something like this. However you must be root to get some special
>events.
>
>Regards
>
>Marcel
>
>
>
>
next prev parent reply other threads:[~2004-10-08 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 12:41 [Bluez-devel] read_RSSI and others not thread-safe? Stefan Mischke
2004-10-08 14:48 ` [Bluez-devel] " Stefan Mischke
2004-10-08 15:29 ` Marcel Holtmann
2004-10-08 15:38 ` Stefan Mischke
2004-10-08 15:40 ` Marcel Holtmann
2004-10-08 16:02 ` Stefan Mischke [this message]
2004-10-08 16:06 ` 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=4166BA03.9050106@uni-paderborn.de \
--to=survivor@uni-paderborn.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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.