Re: PATCH: ncr/sym drivers and bridges

Paul Jakma (paul@clubi.ie)
Mon, 26 Jul 1999 06:03:55 +0100 (IST)


Hi,

I've been looking into this problem aswell, with lots of help from
Gerald. And it definitely it's due to a funny core_pyxis.c change.

we now map 2GB - 4GB PCI address space to 0 to 2GB
memory address space, and 0-2GB pci space to 2-4GB memory space...
(strange i think).

ie all of the PCI address space is now mapped to memory by the
pyxis chipset, but "cut in 2 and flipped over" rather than
contigiously.

Before we only mapped 1-2GB pci space to 0-1GB memory space.

I noticed that virt_to_phys and phys_to_virt weren't updated. Could
this be the cause? The new mapping doesn't seem 'backwards
compatible' with the old mapping to me.

Best thing to do is back out the changes to
include/asm-alpha/core_pyxis.h and arch/alpha/kernelcore_pyxis.c.

On Sun, 25 Jul 1999, Barrett G. Lyon wrote:

Dave, the only reason I figured it could have been Gerard's driver is
because previously I was using the AIC7xxx driver with a 2940uw and I did
not have the pyxis errors. I moved to a sym based 53c800 card and thats
when the errors began to happen.

It could that there is a 164SX specific error. I might try compiling the
kernel as a 'generic' kernel. If that does fix the error then something
with the 164SX specific code is wack.

Anyway Gerard has done a lot of work and I thank him!

Take it easy,

-- 
Paul Jakma
paul@clubi.ie	http://hibernia.clubi.ie
PGP5 key: http://www.clubi.ie/jakma/publickey.txt
-------------------------------------------
Fortune:
You can do this in a number of ways.  IBM chose to do all of them.
Why do you find that funny?
		-- D. Taylor, Computer Science 350

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/