From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 09:59:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89D9E106567E for ; Fri, 4 Jul 2008 09:59:20 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 1122D8FC23 for ; Fri, 4 Jul 2008 09:59:19 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m649xItd082653; Fri, 4 Jul 2008 13:59:18 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Fri, 4 Jul 2008 13:59:18 +0400 (MSD) From: Dmitry Morozovsky To: Marcel Moolenaar In-Reply-To: Message-ID: <20080704135827.H35668@woozle.rinet.ru> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Fri, 04 Jul 2008 13:59:18 +0400 (MSD) Cc: Alexey Shuvaev , freebsd-current@freebsd.org Subject: Re: puc(4) man page update? 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: Fri, 04 Jul 2008 09:59:20 -0000 On Tue, 1 Jul 2008, Marcel Moolenaar wrote: MM> > - I have spent few hours figuring out why serial interfaces MM> > covered by puc(4) do not come up at boot time. The issue was I tried MM> > to use kernel module instead of compiling puc(4) into the kernel. MM> > Will it be good to have explicit note about it in the man page? MM> MM> Well, no. There's a very simple rule: MM> MM> If driver C is a child of a driver P and driver P is MM> loaded as a module, then driver C must be loaded as MM> a module as well. MM> MM> In this case uart(4) and ppc(4) are children of puc(4) MM> and both are compiled into the kernel by default. So, MM> you must either compile puc(4) into the kernel or MM> build uart(4) and puc(4) as modules as well. MM> MM> In other words: there's no problem with puc(4) being MM> loaded as a module. It's a generic problem with our MM> modules vs. compiled-in case. doesn't splitting uart out of kernel broke serial console? Last time I checked it did. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------