lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 7 May 2010 14:02:48 +0100
From:	Alan Cox <alan@...ux.intel.com>
To:	Juergen Beisert <jbe@...gutronix.de>
Cc:	linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Jiri Slaby <jslaby@...e.cz>
Subject: Re: Driver for a SmartCard interface on a SoC

On Fri, 7 May 2010 15:18:50 +0200
Juergen Beisert <jbe@...gutronix.de> wrote:

> Hi,
> 
> most SmartCard readers are external devices, connected via USB or
> serial lines. So, they do not need special in-kernel drivers.
> 
> My SmartCard interface is part of a SoC (i.MX25 CPU). So, I need an
> in-kernel driver. Where would be the best place in the kernel tree,
> to add a driver for this kind of device? Maybe "drivers/char"?
> To exchange data with the plugged in SmartCard, only a couple of
> IOCTLs are required (detecting if a card is plugged in, socket power
> on/off, send reset to the card, configuring the communication
> parameters). Data exchange with the SmartCard can be done with simple
> read/write.

I'd say drivers/char if its a generic char device, but if its MX25
specific code entirely then drivers/platform or arch/.../platform.

The other question is one of API - it's going to best if the API isn't
MX25 specific but could reasonably be expected to work with other
future devices. A fake tty interface is probably overkill for that but
it would be good to get general review of any API.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ