All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: "István Váradi" <ivaradi@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Smart card reader support for Anysee DVB devices
Date: Mon, 29 Aug 2011 17:50:57 +0300	[thread overview]
Message-ID: <4E5BA751.6090709@iki.fi> (raw)
In-Reply-To: <CAFk-VPzKa4bNLCMMCagFi1LLK6PnY245YJqP5yisQH77nJ0Org@mail.gmail.com>

On 08/29/2011 05:44 PM, István Váradi wrote:
> Hi,
>
> 2011/8/17 Antti Palosaari<crope@iki.fi>:
>> On 08/15/2011 02:14 PM, Antti Palosaari wrote:
>>> On 08/15/2011 02:51 AM, Antti Palosaari wrote:
>>>> Biggest problem I see whole thing is poor application support. OpenCT is
>>>> rather legacy but there is no good alternative. All this kind of serial
>>>> drivers seems to be OpenCT currently.
>>>
>>> I wonder if it is possible to make virtual CCID device since CCID seems
>>> to be unfortunately the only interface SmartCard guys currently care.
>>
>> I studied scenario and looks like it is possible to implement way like,
>> register virtual USB HCI (virtual motherboard USB controller) then
>> register virtual PC/SC device to that which hooks all calls to HW via
>> Anysee driver. Some glue surely needed for emulate PC/SC. I think there
>> is not any such driver yet. Anyhow, there is virtual USB HCI driver
>> currently in staging which can be used as example, or even use it to
>> register virtual device. That kind of functionality surely needs more
>> talking...
>
> It maybe that smartcard guys care only for CCID, but wouldn't it be an
> overkill to implement an emulation of that for the driver? It can be
> done, of course, but I think it would be much more complicated than
> the current one. Is it really necessary to put such complexity into
> the kernel? In my opinion, this should be handled in user-space.

Only De facto serial smartcard protocol is so called Phoenix/Smartmouse, 
implementing new protocol is totally dead idea. It will never got any 
support.

There is already such drivers, at least Infinity Unlimited USB Phoenix 
driver (iuu_phoenix.c). It uses USB-serial driver framework and some 
small emulation for Phoenix protocol. Look that driver to see which kind 
of complexity it adds. Anysee have *just* same situation.

regards
Antti


-- 
http://palosaari.fi/

  reply	other threads:[~2011-08-29 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17 14:18 Smart card reader support for Anysee DVB devices István Váradi
2011-08-14 23:51 ` Antti Palosaari
2011-08-15 11:14   ` Antti Palosaari
2011-08-17 20:41     ` Antti Palosaari
2011-08-29 14:44       ` István Váradi
2011-08-29 14:50         ` Antti Palosaari [this message]
2011-08-29 15:13           ` István Váradi
2011-08-29 15:23             ` Antti Palosaari
2011-09-02 11:04               ` Bjørn Mork
2011-09-02 13:32                 ` Antti Palosaari
2011-09-28 14:32                   ` Antti Palosaari
2011-09-30 15:36                     ` Antti Palosaari
2011-10-02 21:06                       ` HoP
2011-10-03 17:56                       ` Bjørn Mork
2011-10-03 12:36           ` James Courtier-Dutton
2011-10-03 12:50             ` Antti Palosaari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E5BA751.6090709@iki.fi \
    --to=crope@iki.fi \
    --cc=ivaradi@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.