linux-kernel - RE: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip

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]

Message-ID: <99B09243E1A5DA4898CDD8B7001114481085E2375D@EXMB04.eu.tieto.com>
Date:	Tue, 29 Mar 2011 11:00:59 +0300
From:	<Waldemar.Rymarkiewicz@...to.com>
To:	<sameo@...ux.intel.com>, <arnd@...db.de>
CC:	<linux-i2c@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<hthebaud@...idefr.com>, <matti.j.aaltonen@...ia.com>,
	<alan@...rguk.ukuu.org.uk>
Subject: RE: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip

>Yes, NFC seems to be a good fit for a new socket family. 
>Especially if we ever want to have a proper NFC p2p support 
>from the kernel.
>Sending HCI commands should be done through a dedicated 
>netlink socket too.
>
>I am currently strting to work on such solution, and I hope to 
>be able to come up with a basic prototype for it in a few weeks.

What about common drivers interface in this case.  Should we go for common /dev/nfcX interface as well?

Waldek--
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/