Am Donnerstag 20 Mai 2010, um 09:47:19 schrieb Juergen Beisert:
> Hi Andreas,
>
> Andreas Jellinghaus wrote:
> > Thinking about it for a few more minutes, I have a much better
> > advice: implement a serial port.
>
> That was also an idea of Alax Cox. But this implies to emulate the whole
> reade
Am Donnerstag 20 Mai 2010, um 10:11:03 schrieb Juergen Beisert:
> That's exactly what I have. But to bring such kind of driver into the
> mainline kernel, the API to the kernel space must be more generic. That's
> the reason, why I'm asking for more uses cases for these SmartCards than I
> have wit
On May 20, 2010, at 15:07 , Juergen Beisert wrote:
> Jim Rees wrote:
>> Juergen Beisert wrote:
>>
>> The external card reader device uses a local processor to run its own
>> firmware. But my case is a little bit different than with an external
>> reader device: My regular Linux system is the pro
Jim Rees wrote:
> Juergen Beisert wrote:
> > > Jim Rees wrote:
> > >> You might want to add pinpad support.
>
> The external card reader device uses a local processor to run its own
> firmware. But my case is a little bit different than with an external
> reader device: My regular Linux sys
Juergen Beisert wrote:
> > Jim Rees wrote:
> >> You might want to add pinpad support.
The external card reader device uses a local processor to run its own
firmware. But my case is a little bit different than with an external reader
device: My regular Linux system is the processor and
On Thu, 2010-05-20 at 11:11 +0200, Ludovic Rousseau wrote:
> I found my patch. It is at [1]. And the email is from Mon, 26 Jan 2009
> 06.
> [1]
> http://www.mail-archive.com/opensc-devel@lists.opensc-project.org/msg03536.html
>
Hoops. I don't understand why your patch was not integrated/debugged
Ludovic Rousseau wrote:
> 2010/5/20 Juergen Beisert :
> > Andreas Jellinghaus wrote:
> >> I think
> >> - read data
> >> - write data
> >> - warm reset
> >> - hard reset
> >> - get card status (card / no card / card removed and added again)
>
> You will also need a way to get card events: a card has
2010/5/20 Juergen Beisert :
> Andreas Jellinghaus wrote:
>> I think
>> - read data
>> - write data
>> - warm reset
>> - hard reset
>> - get card status (card / no card / card removed and added again)
You will also need a way to get card events: a card has been inserted,
a card has been removed.
Or
2010/5/19 Ludovic Rousseau :
> Le 19 mai 2010 18:33, Jean-Michel Pouré - GOOZE a écrit :
>> Ludovic, this may be useful to describe how libccid could evolve to
>> handle t=1 protocol
>
> libccid already supports T=1 (and better than OpenCT :-)
>
> Regarding T=1 I reused the T=1 layer from OpenCT w
Hi Andreas,
Andreas Jellinghaus wrote:
> Am Mittwoch 19 Mai 2010, um 15:32:22 schrieb Juergen Beisert:
> > I don't know if this is the correct list to ask this question. If not,
> > please give me a pointer.
>
> muscle list has even more experts on writing drivers I guess,
> but opensc-devel shoul
Hi Andreas,
Andreas Jellinghaus wrote:
> Thinking about it for a few more minutes, I have a much better
> advice: implement a serial port.
That was also an idea of Alax Cox. But this implies to emulate the whole
reader in kernel land (the kernel driver must be the 'firmware' of this
device). Th
Martin Paljak wrote:
> On May 19, 2010, at 19:35 , Juergen Beisert wrote:
> > The list gets longer:
> >
> > Jim Rees wrote:
> >> You might want to add pinpad support. Also think about how you want to
> >> handle multiple readers or multiple slots per reader. And card
> >> insert/removal notificat
Andreas Jellinghaus wrote:
Thinking about it for a few more minutes, I have a much better
advice: implement a serial port.
No no no! The serial port drivers have to muck with the uart to set all the
fussy rs232 parameters, like frame size and bit rate. I don't think you
want to emulate this
Thinking about it for a few more minutes, I have a much better
advice: implement a serial port.
the reader-smart card interface is not that much different from
a serial port I guess, so in kernel land you should be able
to look at many existing drivers for serial ports, and implement
a simple seri
Am Mittwoch 19 Mai 2010, um 15:32:22 schrieb Juergen Beisert:
> I don't know if this is the correct list to ask this question. If not,
> please give me a pointer.
muscle list has even more experts on writing drivers I guess,
but opensc-devel should be fine, too.
> Other SmartCard interfaces are b
Le 19 mai 2010 18:33, Jean-Michel Pouré - GOOZE a écrit :
> On Wed, 2010-05-19 at 18:12 +0200, Juergen Beisert wrote:
>> > Then a single and universal driver (ifdhandler) for pcsc-lite could
>> be
>> > created just as the CCID driver is universal (so-so) for CCID
>> devices.
>>
>> That could be th
On May 19, 2010, at 19:35 , Juergen Beisert wrote:
> The list gets longer:
>
> Jim Rees wrote:
>> You might want to add pinpad support. Also think about how you want to
>> handle multiple readers or multiple slots per reader. And card
>> insert/removal notification.
>
> 'pinpad' means a reader'
On May 19, 2010, at 19:33 , Jean-Michel Pouré - GOOZE wrote:
> On Wed, 2010-05-19 at 18:12 +0200, Juergen Beisert wrote:
>>> Then a single and universal driver (ifdhandler) for pcsc-lite could
>> be
>>> created just as the CCID driver is universal (so-so) for CCID
>> devices.
>>
>> That could be t
> What are the requirements a SmartCard user has to his/her interface:
>
> - switching on/off the interface
> - detecting if a SmartCard is plugged in
> - resetting the SmartCard
> - locking the SmartCard
> - setting up the communication parameters like FI/DI/convention
> - activating the clo
On Wed, 2010-05-19 at 18:12 +0200, Juergen Beisert wrote:
> > Then a single and universal driver (ifdhandler) for pcsc-lite could
> be
> > created just as the CCID driver is universal (so-so) for CCID
> devices.
>
> That could be the goal.
I remember a post on the mailing list explaining how Ope
Martin Paljak wrote:
> On May 19, 2010, at 18:15 , Juergen Beisert wrote:
> > Martin Paljak wrote:
> >> On May 19, 2010, at 16:32 , Juergen Beisert wrote:
> >>> I don't know if this is the correct list to ask this question. If not,
> >>> please give me a pointer.
> >>>
> >>> Other SmartCard interfa
On May 19, 2010, at 18:15 , Juergen Beisert wrote:
> Martin Paljak wrote:
>> On May 19, 2010, at 16:32 , Juergen Beisert wrote:
>>> I don't know if this is the correct list to ask this question. If not,
>>> please give me a pointer.
>>>
>>> Other SmartCard interfaces are built into an external rea
Martin Paljak wrote:
> On May 19, 2010, at 16:32 , Juergen Beisert wrote:
> > I don't know if this is the correct list to ask this question. If not,
> > please give me a pointer.
> >
> > Other SmartCard interfaces are built into an external reader (mostly
> > connected via USB or serial line). My S
On May 19, 2010, at 16:32 , Juergen Beisert wrote:
> Hi list,
>
> I don't know if this is the correct list to ask this question. If not, please
> give me a pointer.
>
> Other SmartCard interfaces are built into an external reader (mostly
> connected
> via USB or serial line). My SmartCard inte
Hi list,
I don't know if this is the correct list to ask this question. If not, please
give me a pointer.
Other SmartCard interfaces are built into an external reader (mostly connected
via USB or serial line). My SmartCard interface is built into a SoC processor
running a regular Linux based s
25 matches
Mail list logo
