Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: willy@thepuffingroup.com
Cc: huck@cup.hp.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] lasi scsi driver
Date: Sat, 04 Mar 2000 21:49:49 -0800	[thread overview]
Message-ID: <200003050549.VAA03562@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Sat, 04 Mar 2000 14:49:38 PST." <20000304144938.A9944@thepuffingroup.com>

willy@thepuffingroup.com wrote:
> That isn't necessarily a problem.  The interface requires the allocation
> of pages which are coherent.  On recent architectures, it's possible to
> allocate pages which are actually IO coherent.  On earlier architectures,
> the same interface would return uncached pages.  The question is
> whether there are any implementations which can do neither of the two
> possibilities.

That's basically correct. Let's start talking about implementations.

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
 - V-class (EPIC/SAGA) is probably supportable with some limitations
)

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.

o PA-7300LC systems *might* support uncacheable memory and subcacheline...
  (Could anyone definitively answer this for any PA-7300LC box?)

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.)

In summary, the number of "unsupportable" systems isn't as big
as I first thought.

thanks,
grant

Grant Grundler
Unix Development Lab
+1.408.447.7253

  reply	other threads:[~2000-03-05  6:47 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 [this message]
2000-03-05 14:29       ` [parisc-linux] uncacheable memory willy
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=200003050549.VAA03562@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=huck@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=willy@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