From owner-freebsd-alpha Wed Mar 14 20:12:46 2001 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 F387937B719 for ; Wed, 14 Mar 2001 20:12:43 -0800 (PST) (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 XAA01854; Wed, 14 Mar 2001 23:12:26 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2F4BuI09827; Wed, 14 Mar 2001 23:11:56 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.16652.75941.750262@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 23:11:56 -0500 (EST) To: "Matthew N. Dodd" Cc: Peter Jeremy , freebsd-alpha@FreeBSD.ORG Subject: Re: EISA support for AS2100 ("Sable") In-Reply-To: References: <20010312081605.A11209@gsmx07.alcatel.com.au> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew N. Dodd writes: > On Mon, 12 Mar 2001, Peter Jeremy wrote: > > I have been offered an AS2100 with a collection of EISA cards, but I > > note that HARDWARE.TXT states "EISA slots are currently unsupported" > > for Sable. Is anyone currently working on this and/or can anyone tell > > me how much effort would be involved in supporting the EISA bus? > > As part of my work on the EISA bus code I intend to look at the Alpha > stuff in more detail at some point in the future. > > As I don't have an Alpha with EISA slots I can't say when in the future > that will be. NetBSD does have support and I'm fairly sure that we don't > need the resource configuration code they use so it may be a simple matter > of looking at their code and writing the correct platform bits for the > 2100. > Matt, I'll be happy to make you an account on the 2100 at BSDI; just say the word. I seem to remember that when we last talked about this, enabling the EISA code on that 2100 led to the fddi adapter being probed properly, but the EISA fddi driver was failing to attach the device. Nobody on the west coast could come up with another EISA board that they could eisacfg into the system & we didn't know if it was a fundamental EISA problem on alpha, or just a problem with the fddi driver.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message