gemplus gempc pcmcia smart card reader

Hi,

libccid supports it, I'd like to add it to openct too, but
I have no idea how to talk to it? Should I see a serial
device file or anything? Or does it need a special kernel
driver? I'm a bit confused. How does libccid talk to it?

Thanks for your help.

Regards, Andreas
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel

On 12/09/06, Andreas Jellinghaus <ajdungeon.inka.de> wrote:
> Hi,

Hello,

You are talking about the NEW GemPC Card and not the old
GemPC 400, right?
Both are PCMCIA but are completely different inside.

> libccid supports it, I'd like to add it to openct too,
but
> I have no idea how to talk to it? Should I see a serial
> device file or anything? Or does it need a special
kernel
> driver? I'm a bit confused. How does libccid talk to
it?

When you insert the device in your PCMCIA slot Linux will
create a new
serial port. I don't know if it is easy to predict the new
serial port
name. Maybe last /dev/ttySx +1.

The device can then be use as a normal GemPC Twin in serial
mode (The
GemPC Twin can be connected to a USB or serial port
depending on the
cable you use). No kernel module is needed.

This GemPC Card reader is already supported by my CCID
driver +
pcsc-lite. pcscd will rescan its serial configuration file
(/etc/reader.conf) when a SIGUSR1 signal is received so it
is possible
to hot plug/unplug the reader to make it appear/disappear.
The
"problem" is that I do not provide a
hotplug/udev or whatever else
configuration file.

Maybe a better solution would be to add support of
ifdhandler API in
OpenCT so you could use any ifdhandler driver without
rewriting it.

Bye,

-- 
  Dr. Ludovic Rousseau
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel

Ludovic Rousseau wrote:
> You are talking about the NEW GemPC Card and not the
old GemPC 400, right?
> Both are PCMCIA but are completely different inside.
>

Ah, ok, I didn't know there were two different card
readers. the one I 
have has no version or product number on it, simply
"GemPC Card" or 
something (don't have it with me right now).

Once I compiled my kernel with serial_cs support, I get a
ttyS0 device.
or to be exact: I have ttyS0..3, the S0 vanishes and comes
back tied
to the card reader.

what our driver does is open the device and set speed etc.
with an
ioctl, and that ioctl failes (sorry, need to lookup the
error message).

> When you insert the device in your PCMCIA slot Linux
will create a new
> serial port. I don't know if it is easy to predict the
new serial port
> name. Maybe last /dev/ttySx +1.

I managed to tap into udev and thus can exactly get the
event with the
device name and relationship to pcmcia and certain
prod_id[1-4].

> The device can then be use as a normal GemPC Twin in
serial mode (The
> GemPC Twin can be connected to a USB or serial port
depending on the
> cable you use). No kernel module is needed.

ah, ok. is it ccid compliant or some other protocol?

> This GemPC Card reader is already supported by my CCID
driver +
> pcsc-lite. pcscd will rescan its serial configuration
file
> (/etc/reader.conf) when a SIGUSR1 signal is received so
it is possible
> to hot plug/unplug the reader to make it
appear/disappear. The
> "problem" is that I do not provide a
hotplug/udev or whatever else
> configuration file.

ok, thanks, I will have a look.

> Maybe a better solution would be to add support of
ifdhandler API in
> OpenCT so you could use any ifdhandler driver without
rewriting it.

on top? we already have it, openct has ct-api, ifdhandler
and pcsc-lite.
on the buttom side? there is no api. using any other driver
wouldn't 
give us why we started the project: to have one
implementation of t=0, 
t=1 etc. and not one per driver.

but I sure need to seriously look at libccid, it has many
advanced 
features openct is missing, and I hope to port some of them
to openct
some day.

Regards, Andreas
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel

On 13/09/06, Andreas Jellinghaus <ajdungeon.inka.de> wrote:
> ah, ok. is it ccid compliant or some other protocol?

It is not CCID compliant since CCID is only for USB. But it
uses a
(proprietary?) protocol to embed CCID frames in a serial
communication.

Have a look at ccid/src/ccid_serial.c in my driver. It
contains a
_very_ short description of the protocol. You can also
cut-n-paste
large parts of the code.

Bye,

-- 
  Dr. Ludovic Rousseau
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel