Date: Fri, 25 Sep 1998 10:50:24 -0700 From: Jason Thorpe <thorpej@nas.nasa.gov> To: Bill Paul <wpaul@skynet.ctr.columbia.edu> Cc: hackers@FreeBSD.ORG Subject: Re: RealTek + memory mapped registers + SMP == ?*%^(#!! Message-ID: <199809251750.KAA23227@lestat.nas.nasa.gov>
next in thread | raw e-mail | index | archive | help
On Fri, 25 Sep 1998 12:56:42 -0400 (EDT) Bill Paul <wpaul@skynet.ctr.columbia.edu> wrote: > Can anyone think of a reason why this would happen? The machine also > has two Intel EtherExpress Pro 100B adapters, and the fxp driver, which > also uses memory mapped access, works fine. I suspect that there's > just something bogus about the RealTek chip that's causing it, but I > don't know what. What can I say? PC hardware sucks! :-) Seriously, though, some chips just don't do memory-mapped access properly, or sometimes have problems when used with some PCI-Host bridges or some PCI-PCI bridges. (E.g. on my main NetBSD development system, I have a PCI expansion backplane which uses DC21050s; memory-mapped access behind that bridge simply Loses on my system, a PPro w/ a 82441 PCI-Host bridge. It works fine on an Alpha and on a PPro system w/ an 82454 PCI-Host bridge.) What we (NetBSD) do in the case of the device losing (i.e. TI ThunderLAN in TI laptop docking stations) is just quirk the device and say - "Ok, you get to use i/o-mapped access. Sorry!" In the case of a bridge losing, we quirk the chipset and disable either memory- or i/o-mapped access via flags in the PCI device attach args. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809251750.KAA23227>