From: "Kim, David" <firstname.lastname@example.org> To: Greg KH <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com>, "Magee, Tim" <firstname.lastname@example.org> Subject: RE: nCipher HSM kernel driver submission feedback request Date: Fri, 17 Apr 2020 15:12:02 +0000 [thread overview] Message-ID: <3b28c21fb1ea4fa7802807bc40da99e4@exukdagfar01.INTERNAL.ROOT.TES> (raw) In-Reply-To: <20200323135924.GA7768@kroah.com> > > Again, you are correct. Although it is cryptographic hardware, the > > driver code does not do anything cryptographic. It is just a PCIe driver. > > If this is "just" a PCIe driver, can you use the UIO interface and just talk to > your hardware directly from userspace without any kernel driver needed? > > What exactly does the kernel driver need to do here? > Hi Greg, Apologies for the delay in response but things took a little bit to get to some kind of new normal. Hope things are well for you. We would need to re-write our driver code in order to use the UIO interface and access the hardware directly from userspace. Besides the actual work involved, this would add extra complexity to our code base as we support other operating systems, which we would not be re-writing our drivers for. Therefore, writing a userspace driver is not something we are planning to do at this time. We have worked through all the submission guides and have made our existing driver 'submission ready' as best we can. This is the code we would like to be considered for upstreaming. Should we make it into the linux codebase, we are committed to providing long term community support for it. Regards, Dave David Kim Senior Software Engineer Tel: +44 1223 703449 nCipher Security One Station Square Cambridge CB1 2GA United Kingdom
prev parent reply other threads:[~2020-04-17 15:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-13 9:48 Kim, David 2020-03-13 10:09 ` Greg KH 2020-03-16 10:44 ` Kim, David 2020-03-16 11:23 ` Greg KH 2020-03-23 6:49 ` Jason A. Donenfeld 2020-03-23 13:32 ` Kim, David 2020-03-23 13:59 ` Greg KH 2020-04-17 15:12 ` Kim, David [this message]
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=3b28c21fb1ea4fa7802807bc40da99e4@exukdagfar01.INTERNAL.ROOT.TES \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='RE: nCipher HSM kernel driver submission feedback request' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).