From owner-freebsd-arm@FreeBSD.ORG Mon Mar 10 19:01:55 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BA1D1E39; Mon, 10 Mar 2014 19:01:55 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8E2089B; Mon, 10 Mar 2014 19:01:55 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2E41AB9A0; Mon, 10 Mar 2014 15:01:53 -0400 (EDT) From: John Baldwin To: "John-Mark Gurney" Subject: Re: option NEW_PCIB Date: Mon, 10 Mar 2014 14:20:16 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <1394200335.1149.370.camel@revolution.hippie.lan> <201403100945.20298.jhb@freebsd.org> <20140310175249.GH32089@funkthat.com> In-Reply-To: <20140310175249.GH32089@funkthat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201403101420.16117.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 10 Mar 2014 15:01:53 -0400 (EDT) Cc: freebsd-arm , Ian Lepore , freebsd-arch@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Mar 2014 19:01:55 -0000 On Monday, March 10, 2014 1:52:49 pm John-Mark Gurney wrote: > John Baldwin wrote this message on Mon, Mar 10, 2014 at 09:45 -0400: > > On Friday, March 07, 2014 9:38:33 am Warner Losh wrote: > > > > > > On Mar 7, 2014, at 6:52 AM, Ian Lepore wrote: > > > > > > > Every architecture has "option NEW_PCIB" in its conf/DEFAULTS except arm > > > > and mips. Is that on purpose? What are the implications of adding it? > > > > Or maybe more importantly, what are the implications of it not being > > > > there? > > > > > > This is John Baldwin?s option for his reworked PCI bridge code. He did that as > > > a fallback in case he really messed up something. It introduces renumbering > > > of busses that don?t already have numbers assigned. It should be enabled on > > > ARM, but the required resource isn?t defined on arm, and some of the other > > > required glue doesn?t seem to be implemented for arm yet, which is why things > > > are the way they are at the moment. I think John intends for the option to go > > > away, and everything it covers will be ?standard?. > > > > Yes. I just added a page on the wiki about NEW_PCIB explaining the changes > > each platform needs for it in a bit more detail on Friday: > > > > https://wiki.freebsd.org/NEW_PCIB > > > > I have posted patches in the past to arm@ to handle step 2 in the NEW_PCIB > > base requirements for arm@ but haven't been able to get folks to test them. > > I just recently made a new pass through sys/arm in a p4 tree to refresh this. > > I haven't even compiled these yet, but you can find the patch here: > > > > http://people.freebsd.org/~jhb/patches/arm_activate2.patch > > Do you need a fully work system, or is booting fine? If you need a > fully working system, then I need some help figure out my panic.. I sent > email to alc and kib a few days ago about it, but I haven't heard anything > back.. it's a problem w/ vm_page... > > If booting is fine, I can test on my AVILA board I have now.. Well, the system needs to boot far enough to actually use memory and I/O port resources for PCI devices. That probably means getting to at least single user and being able to pass a network packet, etc. -- John Baldwin