From owner-freebsd-ppc@freebsd.org Sat Sep 19 02:13:07 2015 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8144A03041 for ; Sat, 19 Sep 2015 02:13:07 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 678491FB5 for ; Sat, 19 Sep 2015 02:13:07 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by ioiz6 with SMTP id z6so73938258ioi.2 for ; Fri, 18 Sep 2015 19:13:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references; bh=a3hhRsk+3zyWuPFVCd08Byt57oLOwatk7yJ+WLDbp1Y=; b=NNPAGvcAZ70lzqOw8lb3qNWjgyShXtMYZnX7ROwJeKH0ncW66Yq64C70p4q6KBpQws tnPwnF1DHjTlvsS+HD7HK6dPn8R3vtpZJFhGAtCLwI0jVJHY9TDuDy+/xJBdvIWVOyeH 0rJnnWVbmQWAw61yOn01Kkg0MQNiNKqTF+umTxlRUx9N2bExERQcrX/79/5BbLBTyFPP pAdM/bpxPoaPqTOYTBsZ/3v7DqbMhrVvUheajwufGgC5BHLsM3BKU3Mp9/lt9grWRwkq HfMcHDsZIAHV9dqzEoc3Fv3mY8T3qzoEUj79eynj5Q4HtaOK6lETBOoBRtDnCy0e2xBv xxuw== X-Received: by 10.107.149.129 with SMTP id x123mr16119244iod.68.1442628783957; Fri, 18 Sep 2015 19:13:03 -0700 (PDT) Received: from [172.17.163.32] (74-95-103-49-Minnesota.hfc.comcastbusiness.net. [74.95.103.49]) by smtp.gmail.com with ESMTPSA id p76sm5041096ioi.42.2015.09.18.19.13.02 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 18 Sep 2015 19:13:03 -0700 (PDT) Cc: "freebsd-ppc@FreeBSD.org" Message-Id: <89BA95FA-DECE-4726-8FA7-4C8F87EABD50@gmail.com> From: Justin Hibbits To: John Clark In-Reply-To: <64B238BE-97FD-44B1-A4FF-DAD6DCDFA7A9@aim.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: Freescale P1020 PCIE and device enumeration problem. Date: Fri, 18 Sep 2015 21:13:02 -0500 References: <64B238BE-97FD-44B1-A4FF-DAD6DCDFA7A9@aim.com> X-Mailer: Apple Mail (2.936) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 02:13:07 -0000 On Aug 29, 2013, at 1:11 PM, John Clark wrote: > Of and on I've been working on getting FreeBSD up and running on a > P1020WLAN evaluation board. With some help and some hackerage I've > been able to get the board up enough to use one of the ethernet tsec > devices to mount an NFS root. > > I've moved on to look at getting the drivers up for my PCIE devices, > and seem to be having problems both 'conceptually', and more > specifically how FreeBSD enumerates devices on the PCIE bus. > > The file powerpc/mpc85xx/pci_fdt.c seems to correctly 'find' the > PCIE, and there is a 'pcib0' allocated, there does not seem to be > any further bus probing to find the PCIE devices. > > They exist, as my linux port does find the devices and calls the > driver init functions, leading to useable devices when linux is > fully booted. > > I have noticed in other ports, say for the mips processor, the use > of 'hints' seems to be a popular way to indicate devices on the bus. > However, I've also read that the DTS files are the preferred way to > indicate the existence of devices. However, in the case of linux, > the DTS files have no listing for the actual devices on the PCIE > bus, just the config info for accessing the PCIE register regions. > > If someone has some illuminating remarks on this topic I'd > appreciate it. > > Thanks, > John Clark. Hi John, I know this is a _very_ old email, but I just found it when cleaning out my inbox of ancient mails. Earlier this year (May, I think?) I committed a PCI bridge driver for the mpc85xx-like family. It works only with 32-bit addresses, but as long as your device tree does only use 32-bit addresses, not multicell, it should work fine for this. - Justin