From owner-freebsd-current@FreeBSD.ORG Thu Sep 9 19:41:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 3228210656EB; Thu, 9 Sep 2010 19:41:09 +0000 (UTC) Date: Thu, 9 Sep 2010 19:41:09 +0000 From: Alexander Best To: freebsd-current@freebsd.org Message-ID: <20100909194109.GA64914@freebsd.org> References: <20100909191750.GA58228@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100909191750.GA58228@freebsd.org> Subject: Re: {arch}/conf/DEFAULTS and uart X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Sep 2010 19:41:09 -0000 On Thu Sep 9 10, Alexander Best wrote: > hi there, > > except for arm most archs seem to enforce uart support in conf/DEFAULTS. is > this really necessary? shouldn't DEFAULTS only contain vital devices/options > without a kernel on a specific arch won't function at all? jhb just explained to me, that the uart entry in DEFAULTS is not a controller or something like that, but the uart backend to use *if* uart gets defined in the kernel config. sorry for the noise folks. cheers. alex > > cheers. > alex > > -- > a13x -- a13x