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: Fri, 17 Sep 2004 18:21:26 +0300 [thread overview]
Message-ID: <1095434486.32091.2.camel@swoop.gemtek.lt> (raw)
In-Reply-To: <Xine.LNX.4.44.0409171056470.7996-100000@thoron.boston.redhat.com>
On Fri, 2004-09-17 at 17:58, James Morris wrote:
> On Thu, 16 Sep 2004, Zilvinas Valinskas wrote:
>
> > I would say Xscale IXP425 has a rather interesting 32, 16 bits
> > read/write results if address is not aligned properly. In the same
> > directory - http://www.gemtek.lt/~zilvinas/crypto/ i've put *.pdf
> > describing what exactly is happening.
>
> 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 ?
Here I use 2.4.27 + IPsec patch (from Herbert Xu) + Xscale bits
(arch/arm - directory is only patched). I can do a full diff between
vanilla 2.4.27 and what I've got if you like and put on web.
>
> - James
next prev parent reply other threads:[~2004-09-17 15:21 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 [this message]
2004-09-17 16:09 ` James Morris
2004-09-28 9:37 ` Zilvinas Valinskas
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=1095434486.32091.2.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).