From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC/PATCH 0/3] cryptodev
Date: Fri, 30 Jun 2017 16:36:21 +0200 [thread overview]
Message-ID: <20170630143621.pvtqwd44u7k4xunz@pengutronix.de> (raw)
In-Reply-To: <20170624134751.gfpub6mrshdwz6cd@lenoch>
Hi,
On Sat, Jun 24, 2017 at 03:47:51PM +0200, Ladislav Michl wrote:
> This serie adds support for cryptodev hardware acceleration.
> However, there's one issue unresolved: cryptodev module
> loading.
> As we have three different modutils implementations available
> and also supporting systemd and sysv init it is a bit messy
> to generate proper config to load cryptodev at boot time.
> So we could either leave module loading to BSP or do something
> on ptxdist level. Thoughts?
I'm not sure I like this. Keeping up to date with crypto stuff is hard
enough as it is. I don't like adding a out-of-tree kernel module into the
mix.
I wouldn't mind the options for gnutls and openssl but those require
crypto/cryptodev.h, right? Where is this coming from anyways?
cryptodev.install is empty, so not from there.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-06-30 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 13:47 Ladislav Michl
2017-06-24 13:48 ` [ptxdist] [PATCH 1/3] cryptodev: new package Ladislav Michl
2017-06-24 13:49 ` [ptxdist] [PATCH 2/3] openssl: add cryptodev support Ladislav Michl
2017-06-24 13:49 ` [ptxdist] [PATCH 3/3] gnutls: " Ladislav Michl
2017-06-30 14:36 ` Michael Olbrich [this message]
2017-06-30 19:25 ` [ptxdist] [RFC/PATCH 0/3] cryptodev Ladislav Michl
2017-07-02 20:30 ` Clemens Gruber
2017-07-02 22:03 ` Alexander Dahl
2017-07-03 6:56 ` Robert Schwebel
2017-07-03 7:29 ` Alexander Dahl
2017-07-10 14:11 ` Ladislav Michl
2017-07-17 8:56 ` Michael Olbrich
2017-07-11 8:56 ` Ladislav Michl
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=20170630143621.pvtqwd44u7k4xunz@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox