Re: MUSCLE New PC/SC Ideas

2000-03-16 Thread David Corcoran 

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

2000-03-16 Thread Jim Rees 

  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

2000-03-16 Thread Jon Barber 

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

2000-03-16 Thread Jim Rees 

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

2000-03-16 Thread marten . norman 

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
***