This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.
Sébastien Lorquet squalyl at gmail.comHi, Well the reply from Harald tells me I didn't get Andreas' response in full, and it seems some replies have to be made. Can someone forward it to the list? Regards Sebastien On Thu, Aug 19, 2010 at 1:40 PM, Harald Welte <laforge at gnumonks.org> wrote: > On Thu, Aug 19, 2010 at 11:42:44AM +0200, Andreas.Eversberg wrote: > > hi sebastien, > > > > thanx for you advice. i will have job names like SIM_JOB_READ, > > SIM_JOB_UPDATE, SIM_JOB_GSMALGO,... i am a bit unsure about the path > array. i > > always thought that each EF has a unique ID. the DF where it is located, > can > > be determined by the first byte of the EF ID. but if it is possible to > have a > > sim with multiple DFgsm, then a path is required of course. > > I think it isn't good to just think of a normal SIM, but keep it as > flexible > with regard to smartcards compliant to 7816-4. Adding a path will not > really > make things terribly more complex, so I'd also agree with Sebastien to > include > tha path and be more flexible as a result. > > -- > - Harald Welte <laforge at gnumonks.org> > http://laforge.gnumonks.org/ > > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20100819/9f931d15/attachment.htm>