Alon Bar-Lev wrote:
> > Because of problems with libusb I have to timeout every 2 seconds
> > so a PC_to_RDR_GetSlotStatus command is sent to the reader every
> > 2 seconds.
> > This short timeout should be removed in a later version of the
> > CCID driver.
>
> I hope so... The dependency of libus
--On Monday, February 02, 2009 07:38:23 PM +0100 Andreas Jellinghaus
wrote:
> but keeping openct around with or without ccid
> driver, or having some other drivers around
> to implement non-ccid drivers all ends up with
> the same result: lots of common functionality in
> several places.
The so
On 04.02.2009, at 20:36, Alon Bar-Lev wrote:
> On Wednesday 04 February 2009 12:29:01 Martin Preuss wrote:
>> Hi,
>>
>> On Dienstag, 3. Februar 2009, Alon Bar-Lev wrote:
>>> On Wednesday 04 February 2009 00:00:44 Martin Preuss wrote:
>> [...]
>>> True. This is why I suggest separating the reader
On Wednesday 04 February 2009 11:11:26 Ludovic Rousseau wrote:
> 2009/2/3 Alon Bar-Lev :
> > In time I believe commonly used drivers may be migrated into new framework,
> > to be more efficient, maintainable and share the common code base available
> > in the reader library. Example: Logging, Proto
On Wednesday 04 February 2009 12:29:01 Martin Preuss wrote:
> Hi,
>
> On Dienstag, 3. Februar 2009, Alon Bar-Lev wrote:
> > On Wednesday 04 February 2009 00:00:44 Martin Preuss wrote:
> [...]
> > True. This is why I suggest separating the reader framework from the
> > application API.
> [...]
>
>
On Wednesday 04 February 2009 15:00:11 Ludovic Rousseau wrote:
> Alon,
>
> What is the benefit of using:
>PKG_CHECK_EXISTS(
>[libpcsclite],
>[PKG_CHECK_MODULES([PCSC], [libpcsclite])]
> instead of just:
> PKG_CHECK_MODULES([PCSC
Hi Max,
Douglas forwarded your mail to several lists to me. could you please do me
a favor and forward this response to those lists as well? (I'm not subscribed
to them ...) Thanks!
I have two comments:
first) opensc does not use libp11 (but libp11 can use opensc or any other
pkcs#11 module).
2009/2/4 Martin Preuss :
> Hi,
>
> On Mittwoch, 4. Februar 2009, Ludovic Rousseau wrote:
>> 2009/2/3 Martin Preuss :
>> > 1) with pcscd all readers are always *on*. As soon as a reader is
>> > connected it is started and polled for card insertion and removal even
>> > when there is no client. I wou
Alon,
What is the benefit of using:
PKG_CHECK_EXISTS(
[libpcsclite],
[PKG_CHECK_MODULES([PCSC], [libpcsclite])]
instead of just:
PKG_CHECK_MODULES([PCSC], [libpcsclite])
Is it because PCSC_CFLAGS and PCSC_LIBS are erased in the se
Hi,
On Dienstag, 3. Februar 2009, Alon Bar-Lev wrote:
> On Wednesday 04 February 2009 00:00:44 Martin Preuss wrote:
[...]
> True. This is why I suggest separating the reader framework from the
> application API.
[...]
Ah, now I understand: so what you propose is to make the PC/SC just a client
o
Hi,
On Mittwoch, 4. Februar 2009, Ludovic Rousseau wrote:
> 2009/2/3 Martin Preuss :
> > 1) with pcscd all readers are always *on*. As soon as a reader is
> > connected it is started and polled for card insertion and removal even
> > when there is no client. I would very much like the pcscd to onl
2009/2/3 Alon Bar-Lev :
> In time I believe commonly used drivers may be migrated into new framework,
> to be more efficient, maintainable and share the common code base available
> in the reader library. Example: Logging, Protocols, Device Access etc.
I think you are too optimistic here. Many dri
Hello,
2009/2/3 Martin Preuss :
> 1) with pcscd all readers are always *on*. As soon as a reader is connected it
> is started and polled for card insertion and removal even when there is no
> client. I would very much like the pcscd to only power up a reader if there
> is at least one client. This
13 matches
Mail list logo
