From owner-freebsd-alpha Fri Jul 28 7:20:24 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 549D937BC2E for ; Fri, 28 Jul 2000 07:20:20 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA14903; Fri, 28 Jul 2000 10:20:16 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA72275; Fri, 28 Jul 2000 10:20:16 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 28 Jul 2000 10:20:15 -0400 (EDT) To: mjacob@feral.com Cc: "'FreeBSD Alpha mailing list'" Subject: RE: fxp0 hangs my AXPpci33 In-Reply-To: References: <14721.35393.181226.803212@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14721.38433.540697.393972@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > I'm reluctant to commit it because I don't really understand why it > > works. It was just a shot-in-the-dark kind of thing.. > > > > Does anybody have any ideas why using I/O port access should work, > > while using the memory mapped access wouldn't? Matt, Doug? > > > > > > The only thing I can think of is that memory mapped access is > > generally broken on the apecs/lca.. But the NCR driver works, and it > > uses memory mapped access.. > > > > They're not the same kind of device at all. > > So, why does I/O access also break on Qlogic cards on alphas? They work just > peachy on i386. And there are many fine cards that work fine with I/O instead > of mem access on alpha.... I thought the i/o problem was only for devices behind ppb's that don't support I/O space access. The problem is caused by our ppb/bus code not realizing the bridge doesn't support i/o space access & offering it as an option.. > Look- I've had the > > if (getenv_int("isp_mem_map", &bitmap)) { > if (bitmap & (1 << unit)) { > m1 = PCIM_CMD_MEMEN; > m2 = PCIM_CMD_PORTEN; > } > } > bitmap = 0; > if (getenv_int("isp_io_map", &bitmap)) { > if (bitmap & (1 << unit)) { > m1 = PCIM_CMD_PORTEN; > m2 = PCIM_CMD_MEMEN; > } > } > > stuff in isp_pci since newbus came in. Somebody should add the same to if_fxp > (or some more general selector solution) and make this an alpha HARDWARE.TXT > entry ("On AXPpci33/Multia, fxp needs to be set for mem_only mapping"). That's what I was planning to do.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message