Chaskiel M Grundman wrote:
> the ccid spec supports using an interrupt pipe message to notify
> the host of card insert/remove events, but devices are not required
> to implement that part. Even for devices that do, I don't
> understand enough of how usb and libusb handle interrupt endpoints
> to k
> >
> > I don't know. This is one of the things I don't know about usb apis.
> > Looking at the linux kernel code suggests that it might work, but it is
> > likely to be system dependent.
> >
>
> I don't mind to enable this feature on Linux and use current approach
> for other. It is just that no
On 12/19/08, Chaskiel M Grundman wrote:
> > I thought of polling the client socket and usb fds, so I exit the poll
> > if I got a command or something was sent from the reader.
> > Wouldn't this work?
>
>
> I don't know. This is one of the things I don't know about usb apis.
> Looking at the li
> I thought of polling the client socket and usb fds, so I exit the poll
> if I got a command or something was sent from the reader.
> Wouldn't this work?
I don't know. This is one of the things I don't know about usb apis.
Looking at the linux kernel code suggests that it might work, but it is
li
On 12/19/08, Chaskiel M Grundman wrote:
> > I thought to make the blocking poll() at ct_mainloop()
>
> The only reason ct_mainloop calls ifdhandler_poll_presence is so that the
> status file is updated. If we don't care about the status file anymore,
> then ct_mainloop doesn't need to know if th
> I thought to make the blocking poll() at ct_mainloop()
The only reason ct_mainloop calls ifdhandler_poll_presence is so that the
status file is updated. If we don't care about the status file anymore,
then ct_mainloop doesn't need to know if there's a card inserted or not.
> call a new
> method
On 12/19/08, Chaskiel M Grundman wrote:
> > I would like also to make the openct stop polling for readers if
> > possible (CCID supports this).
>
>
> I assume you mean "stop polling for CARDS".
Via the reader... :)
> the ccid spec supports using an interrupt pipe message to notify the host
>
> I would like also to make the openct stop polling for readers if
> possible (CCID supports this).
I assume you mean "stop polling for CARDS".
the ccid spec supports using an interrupt pipe message to notify the host
of card insert/remove events, but devices are not required to implement
that pa
On Thursday 08 May 2008, Alon Bar-Lev wrote:
> On 5/8/08, Antti Andreimann wrote:
> > I have a patch somewhere in my bitbucket that gets rid
> > of /var/run/openct/status and implements status functions by connecting
> > to existing AF_UNIX sockets instead. It's a bit slower, but It would
> > e
Ühel kenal päeval, N, 2008-05-08 kell 21:24, kirjutas Alon Bar-Lev:
> It sounds great idea.
> But I know nothing about current internals.
> Sockets should be simpler to handle, right?
Ok, I'll see if I can find the patch and posti it for comments in a few
days.
--
Antti Andreimann
Rbox Technica
On 5/8/08, Antti Andreimann <[EMAIL PROTECTED]> wrote:
> I have a patch somewhere in my bitbucket that gets rid
> of /var/run/openct/status and implements status functions by connecting
> to existing AF_UNIX sockets instead. It's a bit slower, but It would
> enable us to eventually write an appl
Ühel kenal päeval, E, 2008-05-05 kell 19:14, kirjutas Alon Bar-Lev:
> When /var/run/openct/status is cleared the api does not recover...
> Anyone have a simple way to solve it before I dig into the code?
I have a patch somewhere in my bitbucket that gets rid
of /var/run/openct/status and impleme
On 5/7/08, Chaskiel M Grundman <[EMAIL PROTECTED]> wrote:
> >
> > Do you want me to fix this and check it in?
> >
>
> please do.
>
Done.
rev 1037.
Thank you!
I could make it work in my complete configuration including disk
encryption using mdev.
Alon.
__
>
> Do you want me to fix this and check it in?
please do.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
On 5/5/08, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> On 5/5/08, Chaskiel Grundman <[EMAIL PROTECTED]> wrote:
> > I have apparently been sitting on a patch that does pts and parameter
> > setting in the proper order for most of a year. (the problem you have seems
> > to be that the existing code
On 5/5/08, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> > 2. When I use software suspend, it looks like sometimes the API
> > "disconnects", so new processes can communicate with readers and
> > current loaded/initialized opensc-pkcs11 instance cannot, any thoughts
> > regarding this?
>
>
> Wh
On 5/5/08, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> Now... Next issues...
> 1. I used openct trunk and your patch, the coldplug does not work...
> "openct-control init" does not run the ifdhandler processes.
Solved.
It requires libusb for coldplug...
I will try to make it use sysfs instead.
>
On 5/5/08, Chaskiel Grundman <[EMAIL PROTECTED]> wrote:
> I have apparently been sitting on a patch that does pts and parameter
> setting in the proper order for most of a year. (the problem you have seems
> to be that the existing code changes the baud rate before doing pts, so the
> card responds
I have apparently been sitting on a patch that does pts and parameter
setting in the proper order for most of a year. (the problem you have
seems to be that the existing code changes the baud rate before doing pts,
so the card responds at the old baud rate) I do not know why I did not
submit th
On 4/25/08, Chaskiel M Grundman <[EMAIL PROTECTED]> wrote:
> On Fri, 25 Apr 2008, Alon Bar-Lev wrote:
>
>
> > Thanks!
> > I tried this... Does not seem to work.
> >
>
> What's your device? What does ifdhandler log?
> can you dump the usb descriptors and send them?
>
Attached.
Look for @ALON.
1.
On Fri, 25 Apr 2008, Alon Bar-Lev wrote:
> Thanks!
> I tried this... Does not seem to work.
What's your device? What does ifdhandler log?
can you dump the usb descriptors and send them?
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
Thanks!
I tried this... Does not seem to work.
Alon.
On 4/25/08, Chaskiel M Grundman <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > Is there a reason why openct supoprt only ccid-1.00?
> > Is it difficult to update it to support newer version?
>
>
> openct only supports 1.00 because that was th
> Hello,
>
> Is there a reason why openct supoprt only ccid-1.00?
> Is it difficult to update it to support newer version?
openct only supports 1.00 because that was the spec that was available when
I originally wrote the code. I have tried to read the 1.10 spec and see
what changed, but I haven
On 4/18/08, Peter Stuge <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 17, 2008 at 02:00:07PM +0300, Alon Bar-Lev wrote:
> > Is there a reason why openct supoprt only ccid-1.00?
>
> Probably because everyone started using Ludovic's ifdhandler with
> pcsc-lite.
But I thought openct meant to provide som
On Thu, Apr 17, 2008 at 02:00:07PM +0300, Alon Bar-Lev wrote:
> Is there a reason why openct supoprt only ccid-1.00?
Probably because everyone started using Ludovic's ifdhandler with
pcsc-lite.
//Peter
___
opensc-devel mailing list
opensc-devel@lists.o
Hello,
Is there a reason why openct supoprt only ccid-1.00?
Is it difficult to update it to support newer version?
Regards,
Alon.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-d
26 matches
Mail list logo
