From: tom_gall@vnet.ibm.com
To: greyham@research.canon.com.au
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [Fwd: Help with string.S]
Date: Fri, 18 Aug 2000 13:48:13 +0000 [thread overview]
Message-ID: <399D3E9D.FB6F2AD2@vnet.ibm.com> (raw)
In-Reply-To: 399D210E.9CA9913A@rochcivictheatre.org
> Hi Tom,
>
> Thanks for the response...
Hi Graham,
Happy to help.
> Graham Stoney wrote:
> > I tried dropping in the new improved version from linux-2.4.0-test7-pre4,
> > and none of the 8xx mods are in there: it'l only work for 32 byte cache
> > lines.
>
> tom_gall@vnet.ibm.com writes:
> > That's not right. Which version of linux-2.4.0-x do you have? I'm sure Paul's,
> > Cort's and and I know for sure mine work for more than 32 byte cache lines
> > because 2 of my boxes have 128 byte cache lines and there's support in there
> > for it. (Paul wrote it... awesome stuff)
>
> I'm talking about linux-2.4.0-test7-pre4, from:
> http://www.kernel.org/pub/linux/kernel/v2.4/linux-2.4.0-test6.tar.bz2
> plus:
> http://www.kernel.org/pub/linux/kernel/testing/test7-pre4.gz
Ah! That's why....
ftp.kernel.org generally lags behind the PowerPC development tree. For the
latest there are a few sources to choose from. Generally the differences are
based on what people are working on.
Cort's Tree: www.fsmlabs.com/linuxppcbk.html
Paul's Tree: linuxcare.com.au/paulus/kernels.html
My Tree: fsmlabs.com/~tgall
Take a look at http://linuxppc.org ... very good collection of PowerPC info...
> Yes, in sysdeps/powerpc/memset.S. This is easily enough solved by nuking it,
> and allowing glibc to use the generic C version.
Yes, exactly.
> > > It sounds like a few people have at least had a shot at adding support
> > > for other than 32 byte cache lines, but none have propagated into the
> > > official kernels; how does that happen anyway?
> >
> > By official are you meaning Linus' ?
>
> Yes. Do I need to run BitKeeper to keep up with the latest ppc changes?
> They don't seem to be making it in to Linus's kernel...
I wouldn't say you *NEED* to run BK, as rsync works just fine.
Regards,
Tom
--
Tom Gall - PowerPC Linux Team "Where's the ka-boom? There was
Linux Technology Center supposed to be an earth
(w) tom_gall@vnet.ibm.com shattering ka-boom!"
(w) 507-253-4558 -- Marvin Martian
(h) tgall@uswest.net
http://oss.software.ibm.com/developerworks/opensource/linux
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2000-08-18 13:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <399D210E.9CA9913A@rochcivictheatre.org>]
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=399D3E9D.FB6F2AD2@vnet.ibm.com \
--to=tom_gall@vnet.ibm.com \
--cc=greyham@research.canon.com.au \
--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).