From: "Markus Rechberger" <markus.rechberger@amd.com>
To: "Éric Piel" <Eric.Piel@tremplin-utc.net>,
"Oliver Neukum" <oliver@neukum.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: O2micro smartcard reader driver.
Date: Mon, 19 Feb 2007 13:15:55 +0100 [thread overview]
Message-ID: <45D994FB.2080606@amd.com> (raw)
On 2/19/07, Éric Piel <Eric.Piel@tremplin-utc.net> wrote:
> 02/17/2007 04:55 AM, Markus Rechberger wrote/a écrit:
> > Hi Eric,
> >
> > I committed your code to linuxtv.org to review and modify it there.
> > http://linuxtv.org/hg/~mrechberger/chipcardreader
> >
> > one thing I noticed is the error handling in ozscr_probe.
> >
> > I'll continue the rest during the next few days, I'd like to see it as
> > soon as possible in the upstream kernel before some kernel api changes
> > again which affects your current driver.
>
> Hi Markus,
>
> Thank you very much for finding new bugs ;-) Actually, right now I've
> just moved and don't have internet at home which is kind of slowing down
> development... Anyway, I'll check if I have some more fixes on my
> computer than on my website. Also, it would be good to double check some
> lines which I've commented XXX. In particular, IIRC there were some
> suspicious sleep saying it was sleeping a microsecond and sleeping one
> millisecond!
as user noone cares if it's 1 ns or 1 ms, since that part seems to work
as it is just leave it.
>
> I'm also a bit concerned about the userspace "driver" for pscd which
> comes with the original driver once the patch will be part of the
> default kernel. Maybe this userspace part could become part of the
> pscdlite distribution.
>
I couldn't find the sources of the userspace library, the link on
musclecard.com is dead (and there's no backup on archive.org)
> Wrt the module having always a usecount value of 1, it was worrying me
> too at the begining until I noticed it decreased back to 0 once the card
> is "ejected" (pccardctl eject 1). Although a bit surprising, I don't
> think it's a bug, is it?
this is where the pcmcia/pccard framework bug becomes relevant. The
usecount is no bug, but the lockup (which got explained in the other
mail) is one
>
> See you,
> Eric
>
>
--
Markus Rechberger
Operating System Research Center
AMD Saxony LLC & Co. KG
next reply other threads:[~2007-02-19 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 12:15 Markus Rechberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-27 17:28 O2micro smartcard reader driver Laurent Bigonville
2006-11-28 10:13 ` Eric Piel
2006-11-28 11:49 ` Oliver Neukum
2006-12-12 21:28 ` Eric Piel
2006-12-12 22:05 ` Oliver Neukum
2007-02-16 23:36 ` Markus Rechberger
2007-02-17 3:55 ` Markus Rechberger
2007-02-19 11:04 ` Éric Piel
2006-11-28 12:19 ` Andreas Jellinghaus
2006-11-28 20:50 ` Laurent Bigonville
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=45D994FB.2080606@amd.com \
--to=markus.rechberger@amd.com \
--cc=Eric.Piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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.