Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] openssl: switch to the ocf-linux package
Date: Tue, 20 Mar 2012 23:44:44 +0100	[thread overview]
Message-ID: <201203202344.45078.arnout@mind.be> (raw)
In-Reply-To: <1332249830-25248-3-git-send-email-gustavo@zacarias.com.ar>

On Tuesday 20 March 2012 14:23:50 Gustavo Zacarias wrote:
> Remove builtin OCF support from the openssl package into a new package.
> Even though ocf support is just a header file we'd rather have it in a
> separate package because of unrelated version bumps and to fetch it from
> source.
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

 One small detail below.

> ---
>  package/openssl/Config.in                |    9 +-
>  package/openssl/ocf-cryptodev-20101223.h |  480 ------------------------------
>  package/openssl/openssl.mk               |   10 +-
>  3 files changed, 9 insertions(+), 490 deletions(-)
>  delete mode 100644 package/openssl/ocf-cryptodev-20101223.h
> 
> diff --git a/package/openssl/Config.in b/package/openssl/Config.in
> index 3e09d88..6ba644a 100644
> --- a/package/openssl/Config.in
> +++ b/package/openssl/Config.in
> @@ -25,9 +25,14 @@ config BR2_PACKAGE_OPENSSL_ENGINES
>  config BR2_PACKAGE_OPENSSL_OCF
>         bool "openssl ocf support"
>         depends on BR2_PACKAGE_OPENSSL
> +       select BR2_PACKAGE_OCF_LINUX
>         help
>           Enable openssl cryptodev (OCF) hardware acceleration support.
> -         This requires kernel patches from the ocf-linux project otherwise
> -         you'll just have a bigger openssl library that works as usual.
> +         This requires the ocf linux kernel extension or you to provide a
> +         pre-patched kernel that includes it.

 Better call it "Open Cryptographic Framework (OCF) kernel extension" so
it's consistent with the BR2_LINUX_KERNEL_EXT_OCF_LINUX prompt.  Perhaps
even refer to that config option so people can search for it.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-03-20 22:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 13:23 [Buildroot] ocf-linux patchset Gustavo Zacarias
2012-03-20 13:23 ` [Buildroot] [PATCH 1/2] ocf-linux: new package Gustavo Zacarias
2012-03-20 22:36   ` Arnout Vandecappelle
2012-03-20 13:23 ` [Buildroot] [PATCH 2/2] openssl: switch to the ocf-linux package Gustavo Zacarias
2012-03-20 22:44   ` Arnout Vandecappelle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-05-04 19:23 [Buildroot] [PATCH 0/0] OCF-Linux Gustavo Zacarias
2012-05-04 19:23 ` [Buildroot] [PATCH 2/2] openssl: switch to the ocf-linux package Gustavo Zacarias

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=201203202344.45078.arnout@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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