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
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
