From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 5F299DE2BF for ; Tue, 17 Jul 2007 01:05:58 +1000 (EST) In-Reply-To: <20070716132902.118450@gmx.net> References: <20070716075317.15260@gmx.net> <20070716132902.118450@gmx.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: From: Segher Boessenkool Subject: Re: Legacy ISA registers/interrupts in PCI device tree node Date: Mon, 16 Jul 2007 17:05:49 +0200 To: "Gerhard Pircher" Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >>> I wonder, if there is a recommended way to specify ISA register >>> addresses and interrupts for a PCI device (unlike for a PCI2ISA >>> bridge)? >> >> The PCI binding describes the required way to do this. > Hmm, I must reread the PCI binding spec. It didn't seem to contain any > information about this. You can describe address regions in "reg" that aren't corresponding to any PCI BAR. There is also a facility to describe subtractive decoding (though I don't think you need this). >> Yes, it should, even if you don't use this in the Linux >> kernel yet. > Well, I still have to wire up the IDE interrupts in the platform setup > code, right? Sure, if you want those interrupts to work, anyway ;-) Segher