From: rubisher <rubisher@scarlet.be>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: James.Bottomley@HansenPartnership.com, soete.joel@scarlet.be,
grundler@parisc-linux.org, linux-parisc@vger.kernel.org,
kyle@parisc-linux.org, matthew@wil.cx
Subject: Re: Yet another ccio fix idea?
Date: Sat, 15 Mar 2008 12:03:05 +0000 [thread overview]
Message-ID: <47DBBAF9.8070205@scarlet.be> (raw)
In-Reply-To: <20080314153512.0AEAC4E6A@hiauly1.hia.nrc.ca>
John David Anglin wrote:
>>> The depw will operate on the left word. Looks like it should be
>>>
>>> asm volatile("depw %1,31,12,%R0" : "+r" (pa) : "r" (hints));
>
> Sorry, the `R' to access the right half of pa is needed when generating
> 32-bit code. The original form might be ok when generating 64-bit
> code but I'd have to check the arch. With 64-bit code, you might need
> to use depd. The other approach might be to change pa to u32.
>
> Dave
Ok if I have some time next week I will check.
Tx,
r.
next prev parent reply other threads:[~2008-03-15 12:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 8:30 Yet another ccio fix idea? rubisher
2008-03-14 15:35 ` John David Anglin
2008-03-15 12:03 ` rubisher [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-14 14:18 rubisher
2008-03-12 9:16 rubisher
2008-03-12 11:47 ` James Bottomley
2008-03-12 12:51 ` John David Anglin
2008-03-12 19:52 ` John David Anglin
2008-03-14 3:57 ` Grant Grundler
2008-03-14 6:02 ` Grant Grundler
2008-03-15 19:32 ` rubisher
2008-03-10 17:16 rubisher
2008-03-10 17:26 ` John David Anglin
2008-03-14 5:53 ` Grant Grundler
2008-03-09 13:55 Joel Soete
2008-03-09 17:46 ` Grant Grundler
2008-03-09 17:48 ` Grant Grundler
2008-03-10 19:59 ` James Bottomley
2008-03-10 20:37 ` John David Anglin
2008-03-14 3:50 ` Grant Grundler
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=47DBBAF9.8070205@scarlet.be \
--to=rubisher@scarlet.be \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@parisc-linux.org \
--cc=kyle@parisc-linux.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=soete.joel@scarlet.be \
/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.