From: David McCullough <David_Mccullough@securecomputing.com>
To: Nawang Chhetan <nawang.chhetan@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: OCF Support on linux 2.6.
Date: Tue, 17 Jul 2007 09:51:33 +1000 [thread overview]
Message-ID: <20070716235133.GA27925@securecomputing.com> (raw)
In-Reply-To: <70a419b80707160248g57943dd3p6ed57fda2405014e@mail.gmail.com>
Jivin Nawang Chhetan lays it down ...
> Hi All,
>
> I am trying to integrate OCF-linux with Quicksec on linux 2.6 kernels.
> Many versions of OCF-Linux have been released but wtihout clear
> demarcation of 2.6 kernel versions they support. All they mention is
> support for kernel verison 2.6.11 and later and the README within the
> distributions states it can be easily modified to support recent
> version of kernels( which is true, I did it for 2.6.17.7 )
> My Question here is that:
> Is there any good OCF-Linux documentation available ?
Only whats on the website. Your best bet is to ask.
The current releases work for kernels up to 2.6.18 without
any major issues. I should be doing a release this week with
everything up to 2.6.22 supported fully. Just finishing off the
testing.
> What is/are the version of 2.6 kernel, the OCF-Linux is most
> stable/tested/developed for ?
> Further I tried to use SafeXcel-1141 hardware accelerator ( which is
> claimed to be supported) with OCF-Linux, but inserting the module
> safe.ko (after ocf.ko and cryptodev.ko ) hangs the machine (Kernel
> version 2.6.17.6 .).
> Do I need to insmod the SafeXcel-1141 driver too ?
I have used the safenet driver on SuperH and ARM platforms. It works
fine there. I don't have any way to test it on x86 though.
It should work fine on 2.6.17, load everything with debug enabled
and see what happens.
If you are running on an x86_64 system, disable all the code in
"random.c" however, it was broken on 64bits arches in older versions.
Cheers,
Davidm
--
David McCullough, david_mccullough@securecomputing.com, Ph:+61 734352815
Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com
next prev parent reply other threads:[~2007-07-17 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 9:48 OCF Support on linux 2.6 Nawang Chhetan
2007-07-16 23:51 ` David McCullough [this message]
2007-07-17 7:20 ` Nawang Chhetan
2007-07-18 0:14 ` David McCullough
2007-07-18 3:37 ` Nawang Chhetan
2007-07-18 4:15 ` David McCullough
2007-07-18 11:40 ` Nawang Chhetan
2007-07-18 23:57 ` David McCullough
2007-07-24 12:35 ` Nawang Chhetan
2007-07-24 23:21 ` David McCullough
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=20070716235133.GA27925@securecomputing.com \
--to=david_mccullough@securecomputing.com \
--cc=linux-crypto@vger.kernel.org \
--cc=nawang.chhetan@gmail.com \
/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.