Re: MUSCLE New PC/SC Ideas
Hello, I agree with most of you and that is why I will add a compiler define so that you can compile PC/SC to either run with dynamic allocation or with allocation at runtime. I agree with serial ports this is a pain - I'm working on some USB smartcard readers too. Dave * David Corcoran Internet Security/Smartcards Home: Purdue University 1008 Cherry Lane Department of Computer Science West Lafayette, IN 47906 CERIAS/COAST Laboratory Home: (765) 463-0096 Cell: (317) 514-4797 http://www.linuxnet.com * *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE New PC/SC Ideas
Is this PC/SC or the drivers though ? The Towitoko PC/SC driver for Win32 claims to release the serial port & only claim it 'on demand'. pc/sc requires card insertion events be delivered. So the drivers must keep the port open. Towitoko is technically in violation of the spec, which is one reason I like them. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE New PC/SC Ideas
Jim Rees wrote: > > Marten is absolutely right. One of the most irritating things about pc/sc > is the way it hijacks the serial port. Is this PC/SC or the drivers though ? The Towitoko PC/SC driver for Win32 claims to release the serial port & only claim it 'on demand'. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE New PC/SC Ideas
Marten is absolutely right. One of the most irritating things about pc/sc is the way it hijacks the serial port. Last time I checked most computers only had two. If you insist on bug-for-bug compatibility with Microsoft, at least make port hijacking an option in the config file. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE New PC/SC Ideas
Dave, My humble suggestions: 1) Please put all poll loops for status change etc. in the IFD_HANDLER. The IX36/56 driver will eventually sleep on IRQ for this... Maybe there are more readers that can send IRQ on status change? 2) Your monitor process is a step towards the Windows PC/SC way of allocating and activating everything in sight. Be careful ;-) If you can, consider to avoid keeping ports open and readers active when no application actually uses them. Saves power (laptops may power down inactive PCMCIA readers!) and system resources. Might reduce IRQ conflicts in some COM port crowded machines too. Also, don't repeat the Windows PC/SC mistake of keeping the card powered up all the time. Thus using the emergency power down as normal practise at card removal, even when the application has deactivated the card for removal. :-( Best Regards Morten At 16:10 2000-03-15 -0500, you wrote: > >Hello, > >I'm just finishing up a new version of pcsc-lite. This one works >differently though. When you start the server it connects automatically >to the readers and threads off a process to monitor card status. Status >requests from the application ask this thread for status instead of the >reader. Now you can run simultaneous GetStatusChange functions, transmits >and everything else you want. I wrapped a mutex around all reader >functions so you can share transmit/status requests. Also, I have fixed >Begin/End transaction so they will block until another application quits. >Since the libraries aren't loaded/unloaded as much the memory leaks are >almost none. > >I should have a release out next week. I will probably end up using this >one for good but I'm taking suggestions. > > >Dave > >* >David Corcoran Internet Security/Smartcards > >Home: Purdue University >1008 Cherry Lane Department of Computer Science >West Lafayette, IN 47906 CERIAS/COAST Laboratory >Home: (765) 463-0096 >Cell: (317) 514-4797 > >http://www.linuxnet.com > >* > >*** >Linux Smart Card Developers - M.U.S.C.L.E. >(Movement for the Use of Smart Cards in a Linux Environment) >http://www.linuxnet.com/smartcard/index.html >*** > *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
MUSCLE Working with two card Readers !!!
Dear Carlos, When can I expect the new release? I require the same for Card and Sam. Earlier, I have asked you for the drivers for Memory cards. Can you let me know, how can I use towitoko Chipdrive micro card reader to read Siemense SLE 4428 secure memory card. This card supports 3W protocol. Thanks in advance. On Wed, 15 Mar 2000, Carlos Prados wrote: >Hello, > >Current version only handles one reader at a time. >Next release will support 4 readers simultaneously. >Also a single multithreaded process will be able to >use one reader from diferent threads. > >Thanks, >Carlos. > >--- Nilesh Correia <[EMAIL PROTECTED]> wrote: >> Hi All, >> I ahve got two towitoko chipdrive macro connected >> to COM 1 and COM 2. >> Now the problem is using CT_data function, how can I >> pass commands to this two >> card reader simultaneouly. At Command prompt tester >> 1 and tester 2 works fine. >> >> CT_data uses only ctn, what is the exact use of >> this? why can't we >> pass on port no. insted of ctn. -- Bye And Take Care. Nilesh Correia. Phone : 98440 92683 Email :- [EMAIL PROTECTED] or [EMAIL PROTECTED] *Freindship Is Like Money, Easily Made Than Kept !!! * *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE IFD handler document?
At 03:46 PM 3/15/00 -0500, you wrote: >Hello, > >I am trying to write an IFD_Handler PC/SC driver. Is there any spec / >document on how to write one? Otherwise, I will start from David's >code. > >Thanks. > >-- >Concentration .. Naomaru Itoi >*** >Linux Smart Card Developers - M.U.S.C.L.E. >(Movement for the Use of Smart Cards in a Linux Environment) >http://www.linuxnet.com/smartcard/index.html >*** Hi , Naomaru If you want write IFD_Handler you can find PC/SC specification at this URL http://www.pcscworkgroup.com/ . David's code is good for understand mechanism for linking specific functionality of each reader to generic PC/SC Resource Manager request. Moreover,for testing your IFD_Handler you must have PC/SC driver for your reader. I have just finished my master thesis, about smart card under Linux, at Politecnico of Torino University,in Italy. If You want more information,please write to me. Best regards. Michele Michele Pagliuzzi via Garibaldi n. 12 12030 VILLANOVA SOLARO (CN) - ITALY --- e-m@il :[EMAIL PROTECTED] [EMAIL PROTECTED] *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
