|Age||Commit message (Collapse)||Author||Files||Lines|
an USIM application can very well exist on a UICC without supporting
classic DF.GSM access. However, most commonly, both are found on
Before this change, a card application (USIM, ISIM, ...) didn't
exist as a separate concept from a card profile. This meant,
we had a manual combination of UICC card profile with USIM application,
and another one of UICC card profile and ISIM application. But what
if there's a combined USIM+ISIM?
In reality, applications exist as separate objects, on top of an
ETSI UICC. Lets therefore register all known applications to the
osim library core, and add code to osmo-sim-test which dynamically
detects all applications present on a given card (by reading EF.DIR).
Let's fix some erroneous/accidential references to wrong license,
update copyright information where applicable and introduce a
SPDX-License-Identifier to all files.
Considering the various styles and implications found in the sources, edit
scores of files to follow the same API doc guidelines around the doxygen
grouping and the \file tag.
Many files now show a short description in the generated API doc that was so
far only available as C comment.
The guidelines and reasoning behind it is documented at
In some instances, remove file comments and add to the corresponding group
instead, to be shared among several files (e.g. bitvec).
This array of bytes is not yet used but is referring to some specs. They
may be used in the future, so leave it there but mark it explicitly as