From: rob hoppe <hoppe@mindspring.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] uncacheable memory (D370)
Date: Sun, 05 Mar 2000 10:57:16 -0500 [thread overview]
Message-ID: <38C283DC.83968072@mindspring.com> (raw)
In-Reply-To: 20000305092901.E9944@thepuffingroup.com
> > - T-class has something similar to U2 which is NOT I/O coherent
>
I have a chance at a T-500. Is it of use?
>
> 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?)
>
Where does the D-370 dual processor fit here?
--
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/ _/
_/ Rob Hoppe _/
_/ 770-995-5099 _/
_/ 770-560-1050 cell _/
_/ 770-338-5885 fax _/
_/ _/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
next prev parent reply other threads:[~2000-03-05 16:55 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 ` [parisc-linux] uncacheable memory willy
2000-03-05 15:57 ` rob hoppe [this message]
2000-03-05 16:05 ` [parisc-linux] uncacheable memory (D370) 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=38C283DC.83968072@mindspring.com \
--to=hoppe@mindspring.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 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.