From owner-freebsd-sparc64@FreeBSD.ORG Mon May 10 01:32:06 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 A501716A4CE for ; Mon, 10 May 2004 01:32:06 -0700 (PDT) Received: from ida.interface-business.de (ida.interface-business.de [193.101.57.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3434D43D4C for ; Mon, 10 May 2004 01:32:06 -0700 (PDT) (envelope-from j@ida.interface-business.de) Received: by ida.interface-business.de (Postfix, from userid 107) id 326497A69; Mon, 10 May 2004 10:32:04 +0200 (MET DST) Date: Mon, 10 May 2004 10:32:04 +0200 From: Joerg Wunsch To: sparc64@freebsd.org Message-ID: <20040510103204.B77963@ida.interface-business.de> References: <20040509171444.B63877@ida.interface-business.de> <20040509213455.GA744@timesink.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20040509213455.GA744@timesink.dyndns.org>; from t.moestl@tu-bs.de on Sun, May 09, 2004 at 11:34:55PM +0200 X-Phone: +49-351-31809-14 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Organization: interface systems GmbH, Dresden cc: Thomas Moestl Subject: Re: ebus resource allocation error? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 08:32:06 -0000 As Thomas Moestl wrote: > From e450 firmware property dumps I have lying around it seems > likely that 0x7e5 is the power failure notification interrupt of one > of the Psycho PCI bridges. The Psycho driver does not allocate it > with RF_SHAREABLE (and neither does your code), thus the error. Hmm, now that you mention it, it seems OFW indeed assigns this IRQ to two devices: $ /sbin/dmesg|fgrep 2021 ebus0: addr 0x1400724000-0x1400724003 irq 2034,2021 (no driver attached) ebus0: addr 0x1400600000-0x1400600003 irq 2021,2024 (no driver attached) However, due to the `no driver attached' message, I wouldn't even have guessed that the psycho code attached a vector to it. What's the second IRQ for, maybe it indicates a failed power supply? Wouldn't it make more sense to have a separate power driver attaching to it? (The IO regs assigned to belong to the power auxio bits described in the PCIO docs.) > Would an envctrl driver actually need this interrupt, or does this > just indicate that envctrl is the device that really triggers power > failure interrupts? I have no idea about it yet. The SUNW,envctrl hardware supposedly uses a Philips PCF8584 to drive the I²C bus, which can indeed trigger an interrupt. I didn't have a clue at all why there are two IRQs. Most likely the envctrl driver would have no use for the powerfail interrupt, but except for implied knowledge, how would I know which is the `correct' IRQ to attach to? Btw., how do I dump the OFW properties, other than by manually descending through the entire /devices hiearchy? I guess it could be done using a FORTH command, but my FORTH knowledge has been seriously rotten away. ;-) -- J"org Wunsch Unix support engineer joerg_wunsch@interface-systems.de http://www.interface-systems.de/~j/