Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Philipp Rumpf <prumpf@suse.de>
Cc: Matthew Wilcox <Matthew.Wilcox@genedata.com>,
	Hannu Martikka <martikka@stybba.ntc.nokia.com>,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] vmlinux in C360
Date: Wed, 7 Jul 1999 18:05:26 +0200	[thread overview]
Message-ID: <19990707180526.F386@mencheca.ch.genedata.com> (raw)
In-Reply-To: <19990707172338.C29058@suse.de>; from Philipp Rumpf on Wed, Jul 07, 1999 at 05:23:38PM +0200

On Wed, Jul 07, 1999 at 05:23:38PM +0200, Philipp Rumpf wrote:
> > > I have problems with Linux on C360. Here is what I tried:
> > 
> > According to http://www.hp.com/unixwork/hpc360/page6.htm, the C360
> > has a PA-8500 CPU which is PA-RISC version 2.0.  This port is
> > currently only targetting the PA-RISC 1.1 family of processors since
> > this is where most of the demand is.  In time, I'm sure we will
> > support the PA-RISC 2.0 series of processors, but we don't right now.
> 
> Still, I _think_ we should be able to run the kernel on PA2.0 in narrow mode.
> 
> As soon as I can get my hands on a PA2.0 box, I can test that.

I think you're right for the moment.  The TLB instructions are 
different between the two variants though; maybe there's some other
stuff?

I guess the bootloader needs to force the W bit to 0?  I note that on
an interruption, the W bit is set to the value of the default width
bit, but how to set the default width bit is implementation defined. 
Anyone care to hint at how to set the default width bit too?

-- 
"A `puffin shuttle' also runs in the summer when the cute, meaty birds
are abundant on nearby cliffs."

Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

  reply	other threads:[~1999-07-07 16:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-07  6:23 [parisc-linux] Whee! Dino is recognized Alex deVries
1999-07-07 10:05 ` [parisc-linux] vmlinux in C360 Hannu Martikka
1999-07-07 10:12   ` Matthew Wilcox
1999-07-07 15:23     ` Philipp Rumpf
1999-07-07 16:05       ` Matthew Wilcox [this message]
1999-07-08 17:28         ` Jim Hull
1999-07-09 13:11           ` Hannu Martikka
1999-07-07 14:56   ` Alex deVries
1999-07-07 22:27   ` Helge Deller
1999-07-08  2:15     ` Alex deVries
1999-07-07 17:33 ` [parisc-linux] Whee! Dino is recognized Grant Grundler
1999-07-07 18:07   ` Alex deVries
1999-07-07 18:07     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
1999-07-08  5:30 [parisc-linux] vmlinux in C360 Mike Hibler
1999-07-08 12:53 ` Helge Deller
1999-07-09 12:49   ` Hannu Martikka

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=19990707180526.F386@mencheca.ch.genedata.com \
    --to=matthew.wilcox@genedata.com \
    --cc=martikka@stybba.ntc.nokia.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=prumpf@suse.de \
    /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