From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] ocf: new package
Date: Fri, 21 Oct 2011 12:56:48 +0200 [thread overview]
Message-ID: <20111021125648.107342fd@skate> (raw)
In-Reply-To: <e2cbdc0fad426d5b9cab3fe2c085d35e@zacarias.com.ar>
Le Fri, 21 Oct 2011 07:33:12 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> Fair enough, though it won't break anything if it's enabled and you
> lack OCF support on the kernel side.
> Similar to what would happen if you don't load the appropiate modules
> or lack hardware support.
Yeah, it's not a hard dependency, just a documentation comment on how
to take advantage of it.
> > So basically, it's just a header that needs to be installed?
> >
> > Thomas
>
> Yes.
> For the moment we've got OpenSSL and maybe Openswan that uses OCF.
> Of course anything that links to OpenSSL uses OCF when it's properly
> enabled on supporting hardware.
Ok, thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-10-21 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 17:48 [Buildroot] [PATCH 1/4] pppd: bugfixes and enhancements Gustavo Zacarias
2011-10-20 17:48 ` [Buildroot] [PATCH 2/4] ocf: new package Gustavo Zacarias
2011-10-21 6:53 ` Thomas Petazzoni
2011-10-21 10:33 ` Gustavo Zacarias
2011-10-21 10:56 ` Thomas Petazzoni [this message]
2011-10-20 17:48 ` [Buildroot] [PATCH 3/4] openssl: split out ocf Gustavo Zacarias
2011-10-20 17:48 ` [Buildroot] [PATCH 4/4] openswan: new package Gustavo Zacarias
2011-10-21 6:51 ` [Buildroot] [PATCH 1/4] pppd: bugfixes and enhancements Thomas Petazzoni
2011-10-21 10:37 ` 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=20111021125648.107342fd@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.