From: Stan Sieler <sieler@allegro.com>
To: adevries@thepuffingroup.com (Alex deVries)
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] depi?
Date: Sun, 14 Nov 1999 23:36:51 -0800 (PST) [thread overview]
Message-ID: <199911150736.XAA14959@opus.allegro.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9911150307300.7996-100000@vodka.thepuffingroup.com> from "Alex deVries" at Nov 15, 1999 03:08:49 AM
Re:
> ; Get ready for phys->virt transition
> ; First order of business is to adjust some pointers
> depi 3,1,2,%arg0 ; phys->virt(free mem ptr)
> depi 3,1,2, %sp ; phys->virt SP
> depi 3,1,2, %dp ; p2v DP
DEPI is "Deposite Immediate". depi 3,1,2, %arg0
drops the value 3 into the upper 2 bits of register arg0.
IIRC, it's: DEPI immediate_value, right_most_bit#, #bits, target_register
But...strange code. It's setting the upper 2 bits of R26, R30, and R27.
> in head.S?
>
> I don't have a 'depi' in the index of my PA 2.0 assembler book. I have a
> depwi and a depdi though.
>
> - Alex "I shot the sheriff, but I did not shoot the depdi" deVries
>
> --
> Alex deVries <adevries@thepuffingroup.com>
> Vice President Engineering
> The Puffin Group
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.
>
--
Stan Sieler sieler@allegro.com
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
next prev parent reply other threads:[~1999-11-15 7:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 8:08 [parisc-linux] depi? Alex deVries
1999-11-15 7:24 ` Jeffrey A Law
1999-11-15 7:36 ` Stan Sieler [this message]
1999-11-15 8:25 ` Philipp Rumpf
1999-11-15 23:14 ` Frank Rowand
1999-11-16 0:26 ` John David Anglin
1999-11-16 12:39 ` Matthew Wilcox
1999-11-16 17:17 ` Philipp Rumpf
1999-11-16 8:26 ` Philippe Benard
1999-11-16 12:20 ` Alan Cox
1999-11-16 11:53 ` Philippe Benard
1999-11-16 12:58 ` Alan Cox
1999-11-16 15:55 ` John David Anglin
1999-11-17 13:00 ` Philipp Rumpf
1999-11-16 12:35 ` Matthew Wilcox
1999-11-16 16:08 ` Philipp Rumpf
1999-11-16 17:14 ` Alan Cox
1999-11-16 16:47 ` Philipp Rumpf
1999-11-16 17:50 ` Alan Cox
1999-11-17 0:06 ` Grant Grundler
1999-11-17 6:21 ` Philipp Rumpf
1999-11-17 18:57 ` Stan Sieler
1999-11-17 19:29 ` Philipp Rumpf
1999-11-17 20:01 ` Stan Sieler
1999-11-17 20:33 ` Philipp Rumpf
1999-11-16 21:43 ` Frank Rowand
1999-11-17 6:12 ` Philipp Rumpf
1999-11-17 18:56 ` Frank Rowand
1999-11-17 22:05 ` Philipp Rumpf
1999-11-17 22:39 ` John David Anglin
1999-11-17 22:52 ` Philipp Rumpf
1999-11-17 23:37 ` Stan Sieler
1999-11-18 0:09 ` Philipp Rumpf
1999-11-18 0:43 ` Frank Rowand
1999-11-18 1:35 ` Frank Rowand
1999-11-18 5:33 ` John David Anglin
1999-11-18 8:02 ` Philippe Benard
1999-11-18 20:37 ` John David Anglin
1999-11-18 22:38 ` Frank Rowand
1999-11-19 4:12 ` Philipp Rumpf
1999-11-19 9:08 ` Philippe Benard
1999-11-17 23:02 ` Frank Rowand
1999-11-17 23:25 ` Philipp Rumpf
1999-11-17 8:14 ` Philippe Benard
1999-11-15 8:19 ` Philipp Rumpf
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=199911150736.XAA14959@opus.allegro.com \
--to=sieler@allegro.com \
--cc=adevries@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
/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