From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gx0-f157.google.com (mail-gx0-f157.google.com [209.85.217.157]) by ozlabs.org (Postfix) with ESMTP id 17B9DDE08E for ; Sat, 18 Apr 2009 03:13:01 +1000 (EST) Received: by gxk1 with SMTP id 1so1617836gxk.9 for ; Fri, 17 Apr 2009 10:12:58 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <49E8B69A.8010005@embeddedarm.com> References: <49E8B69A.8010005@embeddedarm.com> From: Grant Likely Date: Fri, 17 Apr 2009 11:12:43 -0600 Message-ID: Subject: Re: Example dts file To: Eddie Dawydiuk Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Apr 17, 2009 at 11:04 AM, Eddie Dawydiuk wrote: > Hello, > > I'm working on creating a dts file for a custom board based on the Yosemite > AMCC 440EP evaluation board. We have an FPGA connected to the PCI bus, and > I'm a bit unsure how to describe this in the dts file. The FPGA implements > an SD card core, RTC core, Nand core... Can anyone point me to an example > dts file I can refer to? If it is attached to the PCI bus, then you don't need to describe it in the .dts file. PCI can reliably probe for devices. Your driver should know what devices are present based on the PCI vendor and device IDs. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.