Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: [resend] 2.4: Support R4000 as a distinct CPU type
Date: Wed, 2 Oct 2002 15:47:53 +0200	[thread overview]
Message-ID: <20021002154753.F17373@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1021001163617.13606J-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Tue, Oct 01, 2002 at 06:17:11PM +0200

On Tue, Oct 01, 2002 at 06:17:11PM +0200, Maciej W. Rozycki wrote:

>  Here is a new version that takes your recent mips64 cache code rearrange
> into account.  OK to apply?

I'm not sure if that's really a good idea.  Technically it's ok but I expect
users of the R4000 to missconfigure their kernels.  So I wonder if it might
be more appropriate to have just automatically enabled this workaround for
systems that are affected?  If we keep it user-selectable then we at least
want a safety check somewhere in the startup code telling users to rebuild
their code with the workaround enabled.

Having this workaround enabled by default would also ensure Linux
distributions ship working code - you don't want users having to recompile
their whole distribution ...

>  BTW, how about renaming r5k-sc.c to sc-r5k.c for consistency?

Yes.  Though there's a bit of confusion hidden there - the Indy SC code
is named ip22-sc.c - but that at least in a different directory.

  Ralf

  reply	other threads:[~2002-10-02 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 16:17 [resend] 2.4: Support R4000 as a distinct CPU type Maciej W. Rozycki
2002-10-02 13:47 ` Ralf Baechle [this message]
2002-10-02 14:18   ` Maciej W. Rozycki

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=20021002154753.F17373@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    /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