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 bilbo.ozlabs.org (Postfix) with ESMTPS id 53EB1B7107 for ; Thu, 2 Jul 2009 08:16:12 +1000 (EST) Subject: Re: PCI device support in Open Firmware (device tree syntax) From: Benjamin Herrenschmidt To: Johnny Hung In-Reply-To: References: <20090629165133.GC1323@b07421-ec1.am.freescale.net> <2ea1731b0906292329t30cdc9a6q1fc36dc2273a2931@mail.gmail.com> Content-Type: text/plain Date: Thu, 02 Jul 2009 08:15:57 +1000 Message-Id: <1246486557.14483.16.camel@pasglop> Mime-Version: 1.0 Cc: Marco Stornelli , linuxppc-dev@lists.ozlabs.org, linux-embedded@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > You are right. u-boot do PCI device BAR resources assign and flat > device tree describe PCI device interrupt-map. I use "lspci -s xxx -x" > for the PCI device, the resources was assigned properly. Note that the device-tree -can- contain PCI devices, but it's not mandatory. If your bootloader does the probing and configuration of the PCI bus, it might be a good idea for that bootloader to also create the PCI device nodes in the tree, since this will allow in a near future the kernel to "instanciate" them from that tree instead of probing with config space, which is faster and more reliably. (Currently only ppc64 does that but it will become generic soon). Cheers, Ben.