Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Michael Ang <mang@thepuffingroup.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: Matthew Wilcox <willy@thepuffingroup.com>,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] NCR driver
Date: Wed, 19 Jan 2000 11:44:49 -0500	[thread overview]
Message-ID: <3885EA01.88E1513B@thepuffingroup.com> (raw)
In-Reply-To: 200001190634.WAA19934@milano.cup.hp.com

I've gotten the tulip driver to find it's device on the A180, but the
PCI I/O address is being reported incorrectly at some point.  The
pci_ioaddr reported is way too low, so I suspect that there is a Dino
related offset that needs to be added somewhere.  I'm digging into the
Dino code to find the right place to add the offset, and any hints/help
is appreciated.

Here's the output from the tulip driver with debugging turned on:
Found Digital DS21142/3 Tulip at I/O 0x1ff00.

PCI bus walking should work fine.  You can see the devices found by
defining DEBUG in drivers/pci/pci.c, and the vendor and device ids are
listed in devlist.h

	- Mike.

Grant Grundler wrote:
> 
> Someone else could start trying to make PCI NCR SCSI also work under Dino.
> Dino code does detect PCI devices and tulip (100BT) driver has started
> talking to it's device. Need to enable CONFIG_GSC_DINO from the default
> ".config". This requires an A, B, or C-class machine to test though.

  parent reply	other threads:[~2000-01-19 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-19  5:56 [parisc-linux] NCR driver Matthew Wilcox
2000-01-19  6:34 ` Grant Grundler
2000-01-19  7:47   ` Matthew Wilcox
2000-01-19 16:44   ` Michael Ang [this message]
2000-01-19 17:15     ` 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=3885EA01.88E1513B@thepuffingroup.com \
    --to=mang@thepuffingroup.com \
    --cc=grundler@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