Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: Helge Deller <deller@gmx.de>, parisc-linux@puffin.external.hp.com
Subject: Re: [parisc-linux] dino maintainer?
Date: Wed, 15 Nov 2000 08:06:32 -0800	[thread overview]
Message-ID: <200011151606.IAA13228@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 15 Nov 2000 09:58:35 PST." <20001115095835.I32715@linuxcare.com>

Richard Hirst wrote:
> On Tue, Nov 14, 2000 at 08:10:42AM -0800, Grant Grundler wrote:
> > The bug is normal for card-mode Dino - not for Built-in Dino.
> > I think Helge has the GSC 100BT card which is a card-mode Dino on-board
> > with one (or two) Tulip(s) behind it.

Helge confirmed he has no such card.
I think the PDC simply isn't programming the Dino IO_ADDR_EN
since there are no PCI devices in his B160.

Helge's B160 has a old rev of Dino PCI host bus adapter chip.
It's possible to have "silent" data corruption caused by older
revs of dino - 3.0 and older.
The latest PDC Revisions (5.x and later) know this and won't permit
the system to be booted unless the only devices on the PCI bus are
known graphics interface cards.

> > The warning is a reminder one can NOT use MMIO accesses to those
> > PCI devices and *only* I/O Port space (eg inb/outb).
> > 
> > If someone wants to fix the warning so it's quiet for card-mode
> > devices...see is_card_dino(d) in dino_driver_callback() for an
> > example.

This is still correct for card-mode dino.

> > FYI - card-mode dino was used for several different networking
> > interfaces but not SCSI interfaces.
> 
> But Helge has problems with the sym53c8xx driver on a B160L.  Is
> that a PCI card driven via Dino? 

I doubt it now. If Helge could send richard "in io" output, I think
that would clarify what's in the B160.

> And if so, are you saying he needs
> to build his kernel with CONFIG_SCSI_NCR53C8XX_IOMAPPED=y so it
> doesn't try to use MMIO?

no. no SCSI was ever implement on a card-mode dino board.
No reason to since they already had Zalon or open slots.

grant

> Helge, it might be worth trying to switch on CONFIG_SCSI_NCR53C8XX_IOMAPPED
> anyway just to see what happens.  Otherwise someone needs to start
> adding printk debug to figure out what is happening.  I can't do
> that as I don't have a sym53c8xx pci card.
> 
> Richard

  reply	other threads:[~2000-11-15 16:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 18:47 [parisc-linux] kernel merge Paul Bame
2000-11-10 21:28 ` bame
2000-11-11  2:18   ` Randolph Chung
2000-11-13  0:25   ` bame
2000-11-13  2:20     ` bame
2000-11-13  7:32       ` Helge Deller
2000-11-13 12:13   ` Richard Hirst
2000-11-13 22:54     ` sym53c8xx-driver (was: Re: [parisc-linux] kernel merge) Helge Deller
2000-11-13 23:27       ` Richard Hirst
2000-11-14  0:13         ` Helge Deller
2000-11-14 10:17           ` Richard Hirst
2000-11-14 13:11             ` Helge Deller
2000-11-14 16:10             ` [parisc-linux] dino maintainer? Grant Grundler
2000-11-15  9:58               ` Richard Hirst
2000-11-15 16:06                 ` Grant Grundler [this message]
2000-11-15 16:50                 ` Alex deVries
2000-11-15 16:17                   ` Grant Grundler
2000-11-15 22:19                 ` Richard Hirst
2000-11-14 10:29   ` [parisc-linux] kernel merge Matthew Wilcox
2000-11-14 17:02     ` Paul Bame
2000-11-14 17:14     ` Paul Bame

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=200011151606.IAA13228@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=deller@gmx.de \
    --cc=parisc-linux@puffin.external.hp.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