All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: 2.6.14-rc2-pa2 ccio patch
Date: Thu, 29 Sep 2005 09:43:08 -0600	[thread overview]
Message-ID: <20050929154308.GA29975@colo.lackof.org> (raw)
In-Reply-To: <200509291513.j8TFDjxN010783@hiauly1.hia.nrc.ca>

On Thu, Sep 29, 2005 at 11:13:45AM -0400, John David Anglin wrote:
> Specifying sr0 will cause fdc to use the space id in sr0.  There's no
> mapping to sr4-7.  This mapping is available when generating PA 2.0
> code with current cvs binutils, but only if you *do not* specify sr0.
> In PA 2.0, there are two different instruction formats for fdc (2 and
> 3-bit space register formats).

Uhm, in my copy of the book, page 7-51 shows two formats, both with
a 2-bit "s" field and clearly indicates a "space_select(s,...)" operation.

>   Only the 2-bit format has the mapping
> to sr4-7.  The 2-bit format is not available when generating PA 1.x code.

page 5-171 of my PA 1.1 book shows only a 2-bit 's' field (and indexed
by register) for FDC. Did you flip to the next page and are by
accident reading the FIC (which only has 3-bit s field) instruction?

> 
> > -	asm volatile("fdc 0(%0)" : : "r" (pdir_ptr));
> > +	asm volatile("fdc %%r0(%%sr0,%0)" : : "r" (pdir_ptr));
> 
> For this to work in PA 1.x, you need to load the space id selected
> by %0 into sr0, or ensure the kernel space id is put in sr0.  Doesn't
> sr4 have the kernel space id in it?

Yes and Yes. But my reading of the PA1.1 arch says it *only* has a 2-bit
s field.

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

       reply	other threads:[~2005-09-29 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050929063554.51BCD494003@palinux.hppa>
     [not found] ` <20050929064709.GA22206@colo.lackof.org>
     [not found]   ` <200509291513.j8TFDjxN010783@hiauly1.hia.nrc.ca>
2005-09-29 15:43     ` Grant Grundler [this message]
2005-09-29 23:21       ` [parisc-linux] Re: 2.6.14-rc2-pa2 ccio patch John David Anglin
2005-10-01  6:50         ` Grant Grundler
2005-10-08 19:30         ` John David Anglin
2005-10-08 19:50         ` John David Anglin
2005-09-29 18:04   ` Joel Soete
     [not found] <IO7AYH$A873EF9A4A4D74961990E3C295F405D8@scarlet.be>
2005-10-11 16:04 ` John David Anglin

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=20050929154308.GA29975@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.