From: Suraj Sumangala <suraj@Atheros.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Waldemar.Rymarkiewicz@tieto.com"
<Waldemar.Rymarkiewicz@tieto.com>,
Suraj Sumangala <Suraj.Sumangala@Atheros.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>,
"joakim.xj.ceder@stericsson.com" <joakim.xj.ceder@stericsson.com>
Subject: Re: Sim Access profile server implementation
Date: Tue, 5 Oct 2010 18:16:15 +0530 [thread overview]
Message-ID: <4CAB1E17.3060406@Atheros.com> (raw)
In-Reply-To: <1286280767.17473.89.camel@aeonflux>
Hi Waldemar,
On 10/5/2010 5:42 PM, Marcel Holtmann wrote:
> Hi Waldemar,
>
> please no top posting on this mailing list.
>
>> I understand you concerns about dbus reliability and I agree with you , but I guess we should find a compromise solution as ofono is not used widely in Linux mobile platforms nowadays.
>>
>> I my view, combination of a bluez plugin for sap and a platform dependend sim driver is a reliable and most available solution so far. The SAP plugin implements BT SAP spec and require simple API (connect, disconnect, apdu, atr, status) which is implemented in SIM driver for a certain platform. This way it's relatively easy to support SAP in different platforms. Ofono can have its own driver as well.
>>
>> What's you view on such design?
>> Can we also have a double solution one in ofono for ofono aware platforms and the second as a plugin for others?
>
> I am fine with starting this in BlueZ and see how far we get. And yes,
> plugin based is a must from my point of view. It is most likely similar
> to our different telephony drivers for Handsfree support.
>
> We will move strongly in the direction of oFono being the main telephony
> stack. So I do care mostly that this work in conjunction with oFono.
> Everything else is just a nice benefit if it doesn't clutter the
> overhaul implementation and requires pointless abstraction everywhere.
>
>> BTW, I already have this implemented and tested with real hardware (STEricsson). Bluez SAP works fine with Nokia 616 carkit :)
>
> Can you share that code with us. And also hardware if you. We are still
> having hard time to find proper hardware to test this on.
>
> Regards
>
> Marcel
>
>
Do let me know if you had to make some changes in the SAP implementation
for it to work.
It will be great if you can share the code in that case. I can update my
implementation accordingly.
Regards
Suraj
next prev parent reply other threads:[~2010-10-05 12:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 7:05 Sim Access profile server implementation suraj
2010-10-05 8:02 ` Marcel Holtmann
2010-10-05 9:08 ` Suraj Sumangala
2010-10-05 10:45 ` Waldemar.Rymarkiewicz
2010-10-05 12:12 ` Marcel Holtmann
2010-10-05 12:46 ` Suraj Sumangala [this message]
2010-10-06 7:28 ` Waldemar.Rymarkiewicz
2010-10-06 9:32 ` Waldemar.Rymarkiewicz
2009-06-06 9:57 ` Suraj Sumangala
2010-10-06 10:13 ` Waldemar.Rymarkiewicz
2010-10-06 12:41 ` Suraj Sumangala
2010-10-06 13:22 ` Waldemar.Rymarkiewicz
2010-10-06 10:00 ` Suraj Sumangala
2010-10-07 15:42 ` Marcel Holtmann
2010-10-08 14:27 ` Waldemar.Rymarkiewicz
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=4CAB1E17.3060406@Atheros.com \
--to=suraj@atheros.com \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=Suraj.Sumangala@Atheros.com \
--cc=Waldemar.Rymarkiewicz@tieto.com \
--cc=joakim.xj.ceder@stericsson.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 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).