Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Missing opcodes in PA 2.0
Date: Sun, 17 Jul 2005 10:31:25 -0400	[thread overview]
Message-ID: <1121610685.5034.1.camel@mulgrave> (raw)
In-Reply-To: <200507162350.j6GNo79q012011@hiauly1.hia.nrc.ca>

On Sat, 2005-07-16 at 19:50 -0400, John David Anglin wrote:
> I've been reviewing the opcode table for gas an noticed that the
> following opcodes appear to have disappeared from PA 2.0:
> 
> { "idtlba",     0x04001040, 0xfc00ffff, "x,(b)", pa10, 0},
> { "idtlba",     0x04001040, 0xfc003fff, "x,(s,b)", pa10, 0},
> { "iitlba",     0x04000040, 0xfc001fff, "x,(S,b)", pa10, 0},
> { "idtlbp",     0x04001000, 0xfc00ffff, "x,(b)", pa10, 0},
> { "idtlbp",     0x04001000, 0xfc003fff, "x,(s,b)", pa10, 0},
> { "iitlbp",     0x04000000, 0xfc001fff, "x,(S,b)", pa10, 0},
> 
> I'm interested in knowing if PA 2.0 processors still support these
> opcodes.

These I know ... the answer's no ... that's why we have pa1.1 and pa2.2
specific paths in the tlb miss handler.

The rest I've no idea

James


_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

      reply	other threads:[~2005-07-17 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-16 23:50 [parisc-linux] Missing opcodes in PA 2.0 John David Anglin
2005-07-17 14:31 ` James Bottomley [this message]

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=1121610685.5034.1.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.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