Hello,

My company is going to propose a patch to fix this problem.  We are in
dire need of this functionality to be implemented in a public release
with 1 months timeframe.  Does anybody have any rough estimate as to
when OpenSC version 12.1 will be released?

Thanks,
Brian Thomas

-----Original Message-----
From: opensc-devel-boun...@lists.opensc-project.org
[mailto:opensc-devel-boun...@lists.opensc-project.org] On Behalf Of
Douglas E. Engert
Sent: Monday, January 17, 2011 11:19 AM
To: opensc-devel@lists.opensc-project.org
Subject: Re: [opensc-devel] OpenSC 12 with minidriver



On 1/17/2011 10:49 AM, Peter Stuge wrote:
> Brian Thomas wrote:
>> To meet our customer's deadline we cannot perform a modification to
>> OpenSC due to the amount of V&V efforts associated with it.
>
> All you need to do is send a clean patch with a commit message that
> makes sense. But I guess that's too much. :\

It looks like its more then deleting a single line. The OpenSC cardmod
code has some #ifdefs L640 to add code to address this problem, and
provides its own  sc_get_cardmod_driver.

Just commenting out line 622 might work for Brian's needs but will break
OpenSC for use without his mini-driver.

Maybe the code need to be more flexible, and use a weak external
reference
to see if a mini-driver is calling it, and use a routine provided by
the min-driver.

>
>
> //Peter
> _______________________________________________
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>

-- 

  Douglas E. Engert  <deeng...@anl.gov>
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to