Am Freitag 23 Januar 2009 12:59:57 schrieb Stanislav Brabec: > HAL documentation recommends to discriminate between three types of FDI > files: > - preprobe: Actions before hal starts to identify the device > - information: Collecting information about the device > - policy: Perform actions > > Current openct FDI file mixes information (that it is a Smart Card > reader) and policy (call hal addon). > > One of possible ways to implement it better is an additional keyword. > Another way would be using of USB IDs known as Smart Card readers in > information and repeating USB IDs of readers known to work in policy.
ah, good point. cleaning this up is a good idea. with hal, do we need to make sure only either openct fdi file or ccid fdi file is installed? or how can you manage, whether some device will be used by openct or by libccid+pcsc-lite? > > ccid shouldn't matter. do you need to put the category as capability too? > > It is a potentially interesting information, easily detectable from USB > ID. ok. > A dumb question. Is following true or only reverse implication is valid? > > no keywords => smart_card_reader.class1 > smart_card_reader.pinpad => smart_card_reader.class2 > smart_card_reader.display + smart_card_reader.pinpad => > smart_card_reader.class3 yes. so "class1/2/3" might be better than pinpad/display to avoid confusion. btw: some vendors have also "class4", but in those cases the reader has some application specific firmware, and thus is currently not of concern to us. > DeviceKit is not yet complete. Redhat plans to introduce it for Fedora > 11 and port applications later. ah, ok. thanks for the information. Regards, Andreas _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
