From owner-freebsd-sparc64@FreeBSD.ORG Thu Apr 22 10:10:48 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6076916A4CE; Thu, 22 Apr 2004 10:10:48 -0700 (PDT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1342043D5C; Thu, 22 Apr 2004 10:10:48 -0700 (PDT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (localhost [127.0.0.1]) i3MHAl8o015271; Thu, 22 Apr 2004 13:10:47 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i3MHAlHZ015270; Thu, 22 Apr 2004 13:10:47 -0400 (EDT) Date: Thu, 22 Apr 2004 13:10:47 -0400 From: Ken Smith To: harti@freebsd.org Message-ID: <20040422171047.GB13967@electra.cse.Buffalo.EDU> References: <20040422185744.J62077@130-149-145-43.dialup.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040422185744.J62077@130-149-145-43.dialup.cs.tu-berlin.de> User-Agent: Mutt/1.4.1i cc: sparc64@freebsd.org Subject: Re: RTC on ultra-10 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Apr 2004 17:10:48 -0000 On Thu, Apr 22, 2004 at 06:59:33PM +0200, Harti Brandt wrote: > has anybody an idea why the eeprom does not attach on my ultra-10? The > result is that I have no RTC. Attached is the verbose boot and the config. Yup, version 1.238 of src/sys/dev/pci/pci.c. :-) I've been told Thomas is working on a patch so I stopped looking into it. Warner has also been told that this broke a few things, I'm not sure if he's working on it though. This is third-hand info that originated at Thomas, and might be suffering from interpretation on my part: This version of pci.c pre-allocates PCI resources at the point the PCI-to-Ebus bridge attaches. However this range of resources that gets pre-allocated includes the devices which then want to be attached via the Ebus so when the attach routine for these Ebus devices gets run the attach fails because the resources they want are already "claimed". Any inaccuracies in that are due to me and not Thomas... :-) -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |