Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Mar 2014 07:38:33 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Ian Lepore <ian@FreeBSD.org>
Cc:        freebsd-arm <freebsd-arm@FreeBSD.org>, freebsd-arch <freebsd-arch@FreeBSD.org>
Subject:   Re: option NEW_PCIB
Message-ID:  <58AB4C66-4267-414D-80D4-B97FF86A94A5@bsdimp.com>
In-Reply-To: <1394200335.1149.370.camel@revolution.hippie.lan>
References:  <1394200335.1149.370.camel@revolution.hippie.lan>

next in thread | previous in thread | raw e-mail | index | archive | help

On Mar 7, 2014, at 6:52 AM, Ian Lepore <ian@FreeBSD.org> 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=92s 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=92t already have numbers assigned. It should be =
enabled on
ARM, but the required resource isn=92t defined on arm, and some of the =
other
required glue doesn=92t 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 =91standard=92.

Warner




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58AB4C66-4267-414D-80D4-B97FF86A94A5>