Re: [RFC] BlueZ D-Bus Sim Access Profile Server API description

[Johan Hedberg <johan.hedberg@gmail.com>]

Hi,

On Mon, Sep 13, 2010, Suraj Sumangala wrote:
> The "array{uint8}" is just the ATR response from the card reader. it
> is not a complete Bluetoth SAP response packet. We need to
> encapsulate ATR packet to form a Bluetooth SAP response packet. The
> packet will be roughly.
> 
> |Response code|Param1|Param data ( ResultCode )|param2|param data (ATR)|
> 
> The ResultCode will have to be mapped as 1 byte result code in the
> SAP response packet sent to the client.

Why would you want to expose these extra SAP profile details to the
Agent? The bluetoothd side should take care of all details like this
whenever possible. The only relevant data that needs to be transmitted
from the Agent to bluetoothd in this case is the ATR and bluetoothd can
then proceed with creating a proper SAP response packet based on that.

> How do we map the D-Bus error return to the ResultCode?

You'd need to define some sort of mapping table yourself. The list of
possible result codes is quite short (8 in SAP 1.1) so this shouldn't be
too hard. E.g. "Error, card not accessible" (0x02) could map to the
D-Bus error org.bluez.SapError.CardNotAccessible.

Johan