From: Marcel Holtmann <marcel@holtmann.org>
To: Suraj Sumangala <suraj@atheros.com>
Cc: linux-bluetooth@vger.kernel.org, Jothikumar.Mothilal@Atheros.com
Subject: Re: [RFC] BlueZ D-Bus Sim Access Profile Server API description
Date: Tue, 14 Sep 2010 14:42:26 +0900 [thread overview]
Message-ID: <1284442946.2405.50.camel@localhost.localdomain> (raw)
In-Reply-To: <1284374584-12282-1-git-send-email-suraj@atheros.com>
Hi Suraj,
> Below is the Sim Access Profile server role API discription.
> Please let me know your comments.
my obvious question is why do we wanna do this over D-Bus and not
connect it directly to the hardware via a plugin?
Remember that SIM transaction are timing critical and just relaying them
over D-Bus doesn't sound the right approach right now. While of course
even bluetoothd can't guarantee and response time, it is clearly better
than over D-Bus.
Regards
Marcel
next prev parent reply other threads:[~2010-09-14 5:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 10:43 [RFC] BlueZ D-Bus Sim Access Profile Server API description Suraj Sumangala
2010-09-13 10:59 ` Johan Hedberg
2010-09-13 11:31 ` Suraj Sumangala
2010-09-13 13:20 ` Johan Hedberg
2010-09-13 15:18 ` Suraj Sumangala
2010-09-13 16:47 ` Johan Hedberg
2010-09-14 5:00 ` Suraj Sumangala
2010-09-13 12:11 ` Waldemar.Rymarkiewicz
2010-09-13 12:29 ` Suraj Sumangala
2010-09-13 12:47 ` Waldemar.Rymarkiewicz
2010-09-13 15:25 ` Suraj Sumangala
2010-09-14 5:42 ` Marcel Holtmann [this message]
2010-09-14 6:28 ` Suraj Sumangala
2010-09-15 3:44 ` Marcel Holtmann
2010-09-15 6:14 ` Suraj Sumangala
2010-09-15 7:32 ` Nicolas GUILBAUD
2010-09-15 8:24 ` Suraj Sumangala
2010-09-15 8:56 ` Nicolas GUILBAUD
2010-09-16 23:00 ` Marcel Holtmann
2010-09-17 11:01 ` Nicolas GUILBAUD
2010-09-18 0:16 ` Marcel Holtmann
2010-09-15 9:18 ` Waldemar.Rymarkiewicz
2010-09-16 7:50 ` Suraj Sumangala
2010-09-16 23:04 ` 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=1284442946.2405.50.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=suraj@atheros.com \
/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;
as well as URLs for NNTP newsgroup(s).