| |||||||||||||
OSCON: That "open phone" is not so openOSCON: That "open phone" is not so openPosted Jul 29, 2010 10:51 UTC (Thu) by laf0rge (subscriber, #6469)In reply to: OSCON: That "open phone" is not so open by tajyrink Parent article: OSCON: That "open phone" is not so open
having the GSM/3G modem as an external (proprietary) device is nice and ok for many people, _BUT_ at that point the interface to that device needs to be publicly documented/specified.
For old GSM/GPRS devices it typically was a serial line with AT commands and a 3GPP-specified multiplex protocol (TS 07.10). In that case, anyone could write code to drive that modem.
But the modern high-end 3G chipsets typically have proprietary RPC interfaces that are running on top of a dual-ported RAM of some sort. So you end up having proprietary components speaking a proprietary protocol to a proprietary GSM/3G modem, rather than _only_ a proprietary modem.
(Log in to post comments)
OSCON: That "open phone" is not so open Posted Jul 29, 2010 15:17 UTC (Thu) by martinfick (subscriber, #4455) [Link]
Not only that, the proprietary code on the other CPU still has access to all the RAM used by the CPU running the free OS! From a security standpoint, this is way worse than a stand alone separate modem.
|
|||||||||||||