netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zilvinas Valinskas <zilvinas@gemtek.lt>
To: James Morris <jmorris@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: Crypto tests via tcrypt.o modules failes
Date: Tue, 28 Sep 2004 12:37:09 +0300	[thread overview]
Message-ID: <1096364229.5548.6.camel@swoop.gemtek.lt> (raw)
In-Reply-To: <Xine.LNX.4.44.0409171209190.8510-100000@thoron.boston.redhat.com>

Hello, 

apparently IPsec and crypto algorithms are ok on IXP 425 (big endian)
system. Not sure what exactly went wrong - I've rm -rf / whole tree , 
applied patches and result - it works .. (I could suspect dependencies
somehow had been broken and not all files were compiled - as a result
miscompilation ? ...)

Anyway, linux 2.4.27 + ipsec (from Herbert) + IXP 425 bits (from
ucLinux) seems is working fine (all crypto modules, not sure only about
cast5 and cast6 algos - as I am not using them here ...)

Zilvinas Valinskas
  

On Fri, 2004-09-17 at 12:09 -0400, James Morris wrote:
> On Fri, 17 Sep 2004, Zilvinas Valinskas wrote:
> 
> > > I've had a report that all is well on an Xscale PXA (SoC) system, with a 
> > > 2.6.7-rc2 kernel.  Are there any significant differences between that and 
> > > what you have?
> > 2.4.27 and 2.6.7-rc2 I think quite different - can you tell me which
> > parts to check for differencies ?
> 
> It should work on either kernel (btw, the PXA is little endian, so they 
> are different).
> 

      reply	other threads:[~2004-09-28  9:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 18:11 Crypto tests via tcrypt.o modules failes Zilvinas Valinskas
2004-09-16 19:25 ` James Morris
2004-09-17  7:49   ` Zilvinas Valinskas
2004-09-16 19:29 ` James Morris
2004-09-17  7:43   ` Zilvinas Valinskas
2004-09-17  7:56   ` Zilvinas Valinskas
2004-09-17 14:58 ` James Morris
2004-09-17 15:21   ` Zilvinas Valinskas
2004-09-17 16:09     ` James Morris
2004-09-28  9:37       ` Zilvinas Valinskas [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=1096364229.5548.6.camel@swoop.gemtek.lt \
    --to=zilvinas@gemtek.lt \
    --cc=jmorris@redhat.com \
    --cc=netdev@oss.sgi.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 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).