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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 31 Dec 2020 14:22:45 +0900 From: Bongsu Jeon <bongsu.jeon2@...il.com> To: Jakub Kicinski <kuba@...nel.org> Cc: davem@...emloft.net, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, linux-nfc@...ts.01.org, Bongsu Jeon <bongsu.jeon@...sung.com> Subject: Re: [PATCH net-next] nfc: Add a virtual nci device driver On Tue, Dec 29, 2020 at 6:16 AM Jakub Kicinski <kuba@...nel.org> wrote: > > On Mon, 28 Dec 2020 18:45:07 +0900 Bongsu Jeon wrote: > > From: Bongsu Jeon <bongsu.jeon@...sung.com> > > > > A NCI virtual device can be made to simulate a NCI device in user space. > > Using the virtual NCI device, The NCI module and application can be > > validated. This driver supports to communicate between the virtual NCI > > device and NCI module. > > > > Signed-off-by: Bongsu Jeon <bongsu.jeon@...sung.com> > > net-next is still closed: > > http://vger.kernel.org/~davem/net-next.html > > Please repost in a few days. > > As far as the patch goes - please include some tests for the NCI/NFC > subsystem based on this virtual device, best if they live in tree under > tools/testing/selftest. thank you for your answer. I think that neard(NFC deamon) is necessary to test the NCI subsystem meaningfully. The NCI virtual device in user space can communicate with neard through this driver. Is it enough to make NCI virtual device at tools/nfc for some test?
Powered by blists - more mailing lists