From: Suraj Sumangala <suraj@Atheros.com>
To: "Waldemar.Rymarkiewicz@tieto.com" <Waldemar.Rymarkiewicz@tieto.com>
Cc: "marcel@holtmann.org" <marcel@holtmann.org>,
Suraj Sumangala <Suraj.Sumangala@Atheros.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>
Subject: Re: [RFC] BlueZ D-Bus Sim Access Profile Server API description
Date: Thu, 16 Sep 2010 13:20:56 +0530 [thread overview]
Message-ID: <4C91CC60.6080604@Atheros.com> (raw)
In-Reply-To: <99B09243E1A5DA4898CDD8B700111448097968EDE3@EXMB04.eu.tieto.com>
Hi,
> I agree with this too. I prefere to have a sap implementation as bluez plugin, but we need to define api for sim operations which could be implemented in ofono or other proprietary stacks. I guess dbus was intended to be kind of hw abstraction api.
> Some time ago Claudio sent proposal implementation of sap server where he defined api for a driver to sim.
The main question will be
"where should be SAP profile packet handling be implemented?"
1. If it has to be implemented as part of bluetoothd, there is no other
option other than using dbus so that we have a consistent interface for
all modules who would be interested in using it.
2. If it has to be done in the "modem/SIM reader", then it will be part
of that module, not an independent module.
will all SIM card reader implementation be ready to implement a
Bluetooth SAP parser as part of it just to support Bluetooth as transport?
>
> Regards,
> /Waldek
Regards
Suraj
next prev parent reply other threads:[~2010-09-16 7:50 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
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 [this message]
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=4C91CC60.6080604@Atheros.com \
--to=suraj@atheros.com \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=Suraj.Sumangala@Atheros.com \
--cc=Waldemar.Rymarkiewicz@tieto.com \
--cc=linux-bluetooth@vger.kernel.org \
--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.