From: Kumar Gala <kumar.gala@freescale•com>
To: "Benjamin Herrenschmidt" <benh@kernel•crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
Chris Friesen <cfriesen@nortel•com>
Subject: Re: new binutils breaks "tlbie" instruction in kernel?
Date: Wed, 2 Feb 2005 23:55:40 -0600 [thread overview]
Message-ID: <3C2E1EF2-75A8-11D9-9151-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1107407613.2363.9.camel@gaston>
Someone should just add some of our asm files into the ppc binutils=20
testsuite, why we cant seem to get a stability on this seems beyond me=20=
:) Well, something else to add to the ppc kernel janitors list.
- kumar
On Feb 2, 2005, at 11:13 PM, Benjamin Herrenschmidt wrote:
> On Wed, 2005-02-02 at 12:39 -0600, Chris Friesen wrote:
> > The "tlbie" instruction has a bit which may be set to indicate=20
> regular
> > or large page size.=A0 This used to be set via an optional second=20
> parameter.
> >
> > Apparently some time between binutils versions 2.15.91.0.2 and
> > 2.15.92.0.2 a change went in to make this second parameter =
mandatory,
> > which breaks the kernel ppc code.
> >
> > What is the recommended way to fix this?=A0 Do all binutils versions
> > understand the second parameter, or will "sufficiently old" versions
> > choke on it?
>
> Wasn't it fixed ?
>
> Ben.
>
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2005-02-03 5:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 18:39 new binutils breaks "tlbie" instruction in kernel? Chris Friesen
2005-02-03 5:13 ` Benjamin Herrenschmidt
2005-02-03 5:55 ` Kumar Gala [this message]
2005-02-03 15:02 ` Chris Friesen
2005-02-04 10:11 ` David Woodhouse
2005-02-04 0:55 ` Segher Boessenkool
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=3C2E1EF2-75A8-11D9-9151-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=cfriesen@nortel$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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