From: Frank Rowand <frank_rowand@hp.com>
To: Alex deVries <adevries@thepuffingroup.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting on PA2.0 machines
Date: Fri, 29 Oct 1999 10:36:24 -0700 [thread overview]
Message-ID: <3819DB18.AC3F55CC@hp.com> (raw)
In-Reply-To: Pine.LNX.4.10.9910290054070.3734-100000@vodka.thepuffingroup.com
Alex deVries wrote:
>
> So I think we've determined that PA2.0 booting problems are related to the
> PDC_BTLB call which isn't implemented in 2.0 processors.
>
> My thought would be to try such a call, and if it fails, then configure
> cache lines in a way specific to 2.0 processors. Am I right?
If the system is a PA 1.1 system then PDC_BLOCK_TLB() should be used.
(PDC_MODEL(Return info), arch_rev reports 1.0, 1.1, or 2.0.) If the
system is a PA 2.0 system then large pages should be specified in the
TLB entries.
> How should we be configuring this?
Just wait for a TLB miss and insert an entry for a very large number of pages
(architected sizes include 4, 16, 64, 256 Kbyte, 1, 4, 16, 64 Mbyte). See
the PA-RISC 2.0 Architecture book by Kane, pp. 3-9 thru 3-14, F-1 thru F-5.
Just as a side note, you can't just insert a block TLB entry and expect it to
exist forever; you have to be able to handle a TLB fault for the address
range and re-insert the entry (or switch to normal entries). See the last
page of the PDC_BLOCK_TLB() description for the explanation of this.
> We've now got some puffins and HP people with 2.0 boxes, so it'd be really
> nice to get these boxes booting.
>
> - Alex
You've just hit the first layer of the onion.
-Frank
prev parent reply other threads:[~1999-10-29 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-29 4:57 [parisc-linux] booting on PA2.0 machines Alex deVries
1999-10-29 17:36 ` Frank Rowand [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=3819DB18.AC3F55CC@hp.com \
--to=frank_rowand@hp.com \
--cc=adevries@thepuffingroup.com \
--cc=frowand@cup.hp.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