From owner-freebsd-hackers Thu Jan 23 16:06:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA21757 for hackers-outgoing; Thu, 23 Jan 1997 16:06:53 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA21752 for ; Thu, 23 Jan 1997 16:06:51 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25574; Thu, 23 Jan 1997 16:49:44 -0700 From: Terry Lambert Message-Id: <199701232349.QAA25574@phaeton.artisoft.com> Subject: Re: FreeBSD and VME To: deischen@iworks.InterWorks.org (Daniel M. Eischen) Date: Thu, 23 Jan 1997 16:49:44 -0700 (MST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199701232057.OAA17948@iworks.InterWorks.org> from "Daniel M. Eischen" at Jan 23, 97 02:57:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Has anybody ever done or considered using FreeBSD for VME IO > solutions? A Motorola engineer has used FreeBSD drivers and Interrupt handling on a Motorolla 88k RT system with a VME bus. He wrote his VME drivers, and it's not the full OS, so he can't give out the code. I discissed the VME interrupt handling in detail with him at one time, but I'm probably a bit rusty on it now (though I saved the discussion). If you get tot he point where you are implementing VME handling, then I can probably talk you around one or two pitfalls if you need it (you'll probably know much more about VME than me by then, though). > The VMEbus is interfaced to the PCI bus by the Universe VMEbus > interface chip made by Tundra (formerly Newbridge Microsystems). > Luckily, all the manuals for the chip are available at Tundras > web site (http://www.tundra.com/Tundra/Products/Bus/BPI/Universe.html). > > How hard would it be to create a VMEbus driver for this? The project > under consideration would only need to memory map VME devices, but > having the ability to config a VME device at an address and VME > interrupt priority/vector would be great for future work. Several NetBSD ports use VME code; that would be a good basis for a start. Unfortunately neither NetBSD nor FreeBSD have abstracted bus bridging very well (IMO, anyway), so there will be mapping issues to fight with. Probably asking on one of the NetBSD lists for VME based systems would be your next logical step. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.