From: Dan Malek <dan@netx4.com>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Help with string.S
Date: Sat, 08 Jul 2000 18:57:39 -0400 [thread overview]
Message-ID: <3967B1E3.80CAC746@embeddededge.com> (raw)
I found the source of the 4xx and 8xx troubles in the 2.4.xx kernel.
The functions in arch/ppc/lib/string.S are broken for anything other
than 32-byte cache lines. I am making the changes, but it would be
nice to have someone else look at this as well. There are lots of
assumptions outside of the apparent parameters that the cache is
32-bytes.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-08 22:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-08 22:57 Dan Malek [this message]
2000-07-08 23:57 ` Help with string.S Dan Malek
2000-07-10 6:14 ` Daniel Marmier
2000-07-10 15:17 ` David Edelsohn
2000-07-10 22:42 ` Dan Malek
2000-07-11 5:50 ` Daniel Marmier
2000-07-13 18:52 ` Dan Malek
2000-07-11 10:06 ` Adrian Cox
2000-07-11 15:53 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-08-16 7:26 Graham Stoney
2000-08-16 16:22 ` tom_gall
2000-08-17 0:50 ` Graham Stoney
2000-08-17 19:28 ` Dan Malek
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=3967B1E3.80CAC746@embeddededge.com \
--to=dan@netx4.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).