Hi,
thanks, this should be fixed in the latest release (3.99.10beta as of two
minutes ago).
The source of this bug was a typo in code which is only called for unknown
naming schemes.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de
they are both supposed to be 32 bit
wide...
I would rather state that using unsigned long (as pcsclite does) is not
quite the correct translation for DWORD, at least on other-than-32-bit
machines...
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2
that current versions of pcsc-lite try again initializing
the driver with a different naming scheme (e.g. libusb:) if the driver
doesn't support the libhal: name, but that's something you added later.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2
consider this matter closed.
For those old distributions which only support the libhal naming scheme we
still have support for libhal and for newer distributions where libhal is
deprecated we don't.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2
the driver which USB device is to be used, and for that the
USB address as used in the libusb naming scheme really is enough and quite
universal.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/
___
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com
. It will take at least a few days until there are packages for your
distro.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de
know for sure that they have the latest
version of the source code...
You should use at least 3.99.5.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de
and should work better.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/
___
Muscle mailing list
Muscle
=viewid=243;
However, even those drivers are outdated, the latest version is 3.99.5beta.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de
that.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/
___
Muscle mailing list
Muscle@lists.musclecard.com
http
tell us anything about what Kobil readers
expect.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/
___
Muscle
IMHO it would be best to keep it at the current naming scheme for libusb-
accessed device and leave the choice of how to access the device with the
driver.
Just my 2c.
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http
they come up with)?
It would be very nice if pcscd retried with a :libusb: name if the driver
doesn't understand :libhal:...
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http
not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/
___
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
)?
Or are there plans to switch to DeviceKit?
I'm asking because I'm currently in the process of adapting the Reiner SCT
cyberJack driver to OpenSuSE 11.2 and Ubuntu 9.10...
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http
until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/
___
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
...
Regards
Martin
--
Things are only impossible until they're not
Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/
___
Muscle mailing list
Muscle@lists.musclecard.com
http
is connected
to? With this change the firmware is now supposed to somehow acquire that
knowledge in order to detect how the multi-byte values of the CCID structures
are to be interpreted...
Or do I miss something here?
Regards
Martin
--
Things are only impossible until they're not
Martin
Hi again,
On Samstag, 21. März 2009, Martin Preuss wrote:
[...]
The statement Byte ordering is decided by machine architecture is stupid
in itself: How would the reader know what architecture the device is
connected to? With this change the firmware is now supposed to somehow
acquire
On Thursday 03 May 2007 01:18, Martin Paljak wrote:
On 03.05.2007, at 1:36, Martin Preuss wrote:
[...]
- the master-slave model described in the document Micha linked to
in his
mail), this is needed for thin-client support provided for Gnumed
Quickly going through the doc - the only
On Wednesday 02 May 2007 23:13, Martin Paljak wrote:
[...]
My question: Do you really want to talk to a reader ? Can't you
communicate with the reader via pcsc (SCardControl should do that)?
[...]
Basically you are right, and that's why Libchipcard is card-centered (it
rarely exposes the
On Wednesday 02 May 2007 23:52, Martin Paljak wrote:
On 03.05.2007, at 0:38, Martin Preuss wrote:
[...]
In general I don't have problems with having a variety of APIs
(although one
single API would greatly simplify the application programmers work)
as long
as none of them tries to bind
Hi,
On Tuesday 01 May 2007 18:29, Hanno Böck wrote:
[...]
Now, already some technical thoughts:
- We have, as far as I know, two kinds of chipcard-related driver types:
pcsc drivers and ctapi.
- At the moment, I can't see a reason why we shouldn't make it so simple to
just say put all
Hi,
On Tuesday 01 May 2007 23:00, Peter Stuge wrote:
On Tue, May 01, 2007 at 10:19:56PM +0200, Andreas Jellinghaus wrote:
On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote:
For CTAPI drivers there is also another problem that should be
addressed in the next step: I think it would
On Wednesday 02 May 2007 00:27, Michael Bender wrote:
Andreas Jellinghaus wrote:
On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote:
For CTAPI drivers there is also another problem that should be addressed
in the next step: I think it would be best to have a system
group/user chipcard
Hi,
there seems to be a problem with some definitions of windows types in
wintypes.h:
typedef unsigned long DWORD;
This is only correct on a 32 bit architecture. On 64 bit this resolves to a
QWORD instead of a DWORD. The reason for using DWORD I believe is to have a
32-bit type, so for this
Hi,
On Wednesday 28 March 2007 11:58, Ludovic Rousseau wrote:
On 28/03/07, Frank Cusack [EMAIL PROTECTED] wrote:
[...]
Isn't it broken to have install the PCSC include files in the PCSC subdir
and then to have them #include other PCSC include files but omit the PCSC
part of the path?
It
Hi,
On Monday 25 December 2006 14:14, Ludovic Rousseau wrote:
On 25/12/06, Martin Preuss [EMAIL PROTECTED] wrote:
On Sunday 24 December 2006 21:39, Ludovic Rousseau wrote:
On 24/12/06, Martin Preuss [EMAIL PROTECTED] wrote:
[...]
I see. Strange. The driver is loaded for the first reader so
it? Could someone please
give me a hint?
kind regards and Merry XMas :-)
Martin Preuss
--
Things are only impossible until they're not
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/
___
Muscle mailing list
Muscle
Hi,
thanks for your reply (especially on such a date and time) :-)
On Sunday 24 December 2006 21:39, Ludovic Rousseau wrote:
On 24/12/06, Martin Preuss [EMAIL PROTECTED] wrote:
[...]
I tried with 3 CCID readers and my CCID driver. I received Lun 0, 1000 and
2000.
[...]
Which version
31 matches
Mail list logo
