From: willy@thepuffingroup.com
To: Grant Grundler <grundler@cup.hp.com>
Cc: huck@cup.hp.com, parisc-linux@thepuffingroup.com
Subject: [parisc-linux] uncacheable memory
Date: Sun, 5 Mar 2000 09:29:01 -0500 [thread overview]
Message-ID: <20000305092901.E9944@thepuffingroup.com> (raw)
In-Reply-To: <200003050549.VAA03562@milano.cup.hp.com>; from Grant Grundler on Sat, Mar 04, 2000 at 09:49:49PM -0800
On Sat, Mar 04, 2000 at 09:49:49PM -0800, Grant Grundler wrote:
> HP systems have three I/O MMU's which are I/O coherent: U2/Uturn,
> Astro/Ike, and Epic/SAGA. AFAIK, all systems using one on them have
> the processor(s) connected to a "Runway" bus. This limits what
> processor model those systems can have: PA-7200, -8000, -8200, or -8500.
>
> (Caveats:
> - T-class has something similar to U2 which is NOT I/O coherent
According to the hwdb, the T600 has two `Java BC Summit Port (IOA)'.
And you're the only one in possession of a T-class :-). All the devices
in the T600 seem to be special devices so the drivers would have to
be freshly written anyway. I don't see a PCI adapter in the T-class,
can one be fitted? I assume Summit is the name of a bus, like Runway
only different?
> In personal conversations, two knowledgable folks have suggested
> the following:
> o PA-7100LC systems support uncacheable memory and subcacheline access.
> So these boxes should be supportable.
that's good, that's a fair chunk of those machines which people have (712,
725/100, 715/later, E-class, early D-class).
> o PA-7300LC systems *might* support uncacheable memory and subcacheline...
> (Could anyone definitively answer this for any PA-7300LC box?)
According to the 7300LC ERS, section 1.1.2 (Integrated Caches and TLB)
`Uncached memory pages are supported via the TLB U-bit.' Then section
1.2.2, (Differences from the PA7100LC) `Uncacheable pages are still
supported. Note: PA7100LC did not require the U bit to be set on TLB
entries for I/O pages, but the PA7300LC does (this was always an
architural requirement).'
I think that's enough for us to go on.
> o PA-7000 systems are pretty much SOL.
> (But they could be perfectly useful if folks add cache flushing to
> the few device drivers needed for graphics and stuff off of LASI.)
how about PA7100/7150 systems? (715/early, 735, 755, later Nova servers)
They will also need explicit cache flushing added, I guess.
next prev parent reply other threads:[~2000-03-05 15:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-02 20:42 [parisc-linux] lasi scsi driver Gyula Matics
2000-03-02 21:19 ` Grant Grundler
2000-03-02 21:44 ` Gyula Matics
2000-03-03 0:50 ` [parisc-linux] Lasi Ethernet - update Helge Deller
2000-03-03 2:55 ` Bdale Garbee
2000-03-03 13:14 ` [parisc-linux] Lasi Ethernet - update (fixed!) Helge Deller
2000-03-03 1:34 ` [parisc-linux] lasi scsi driver Helge Deller
2000-03-03 15:52 ` willy
2000-03-03 19:10 ` Jerry Huck
2000-03-04 19:49 ` willy
2000-03-05 5:49 ` Grant Grundler
2000-03-05 14:29 ` willy [this message]
2000-03-05 15:57 ` [parisc-linux] uncacheable memory (D370) rob hoppe
2000-03-05 16:05 ` willy
2000-03-06 6:26 ` uncacheable memory Grant Grundler
2000-03-05 18:34 ` [parisc-linux] lasi scsi driver Philipp Rumpf
2000-03-05 18:46 ` Philipp Rumpf
2000-03-05 21:05 ` Thomas Bogendoerfer
2000-03-07 19:33 ` Jerry Huck
2000-03-07 23:45 ` Philipp Rumpf
2000-03-08 0:33 ` 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=20000305092901.E9944@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=grundler@cup.hp.com \
--cc=huck@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