Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Use a sensible tlbex default for unknown CPUs
Date: Thu, 25 Oct 2007 17:53:13 +0100	[thread overview]
Message-ID: <20071025165313.GE3994@networkno.de> (raw)
In-Reply-To: <20071025161023.GA24715@linux-mips.org>

Ralf Baechle wrote:
> On Thu, Oct 25, 2007 at 04:59:12PM +0100, Thiemo Seufer wrote:
> 
> > currently the kernel panics when it boots on an unknown CPU model
> > (with an unknown PRID). Based on the assumption that the majority
> > of newly supported CPU will conform to Release 2 standard, I wrote
> > the appended patch which handles unknown CPUs as R2. It isn't
> > completely bulletproof, as (yet unsupported) non-R1/R2 CPUs may
> > use the AT config bits for different purposes. I still think this
> > is good enough a test.
> > 
> > This patch allows me to boot Linux on a "generic" MIPS64R2 Qemu
> > without making up a potentially conflicting PRID. All-zeroes
> > like for other undefined fields does fine.
> 
> It's a little more elegant with cpu_has_mips_r2.  So how about below patch.

Fine with me.


Thiemo

  reply	other threads:[~2007-10-25 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 15:59 [PATCH] Use a sensible tlbex default for unknown CPUs Thiemo Seufer
2007-10-25 16:10 ` Ralf Baechle
2007-10-25 16:53   ` Thiemo Seufer [this message]
2007-10-25 17:08 ` Maciej W. Rozycki
2007-10-25 20:56   ` Thiemo Seufer
2007-10-26  9:31     ` Maciej W. Rozycki
2007-10-28 23:39     ` Ralf Baechle

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=20071025165313.GE3994@networkno.de \
    --to=ths@networkno.de \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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