Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] a500.out16
Date: Thu, 02 Nov 2000 08:12:47 -0800	[thread overview]
Message-ID: <200011021612.IAA28541@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Thu, 02 Nov 2000 10:48:33 PST." <20001102104833.G32715@linuxcare.com>


This is why I do NOT like our current scheme of using host
physical addresses to access I/O space.

Richard Hirst wrote:
...
> I'd guess that the NCR registers are being cached:
> 
> 
> static int __init ncr_regtest (struct ncb* np)
> {
>         register volatile u_int32 data;
>         /*
>         **      ncr registers may NOT be cached.
>         **      write 0xffffffff to a read only register area,
>         **      and try to read it back.
>         */
>         data = 0xffffffff;
>         OUTL_OFF(offsetof(struct ncr_reg, nc_dstat), data);
>         data = INL_OFF(offsetof(struct ncr_reg, nc_dstat));

If INL_OFF and OUTL_OFF are broken, they will very likely point
to something in memory - page zero. And happily scribble over
it gsc_write(xxx).

We don't cache I/O space. Never.
Something is definitely broken on this code path.

I'll look at this once I find out what I broke on the j5k/c3k boot path
in lba_pci.c. jsm already restored the previous version of lba_pci.c
so folks can still boot 32-bit on c3k/j5k.

grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

      reply	other threads:[~2000-11-02 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02  8:21 [parisc-linux] a500.out16 Grant Grundler
2000-11-02 10:43 ` Richard Hirst
2000-11-02 11:30   ` Richard Hirst
2000-11-02 12:01     ` Matthew Wilcox
2000-11-02 16:42       ` Grant Grundler
2000-11-02 12:07   ` Richard Hirst
2000-11-02 10:48 ` Richard Hirst
2000-11-02 16:12   ` Grant Grundler [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=200011021612.IAA28541@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=rhirst@linuxcare.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