Date: Sat, 5 Jul 2008 01:12:47 +0400 (MSD) From: Dmitry Morozovsky <marck@rinet.ru> To: Marcel Moolenaar <xcllnt@mac.com> Cc: Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de>, freebsd-current@freebsd.org Subject: Re: puc(4) man page update? Message-ID: <20080705011154.G97379@woozle.rinet.ru> In-Reply-To: <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <EFBC6852-012F-4207-A4CE-B407CF92F25E@mac.com> <20080704135827.H35668@woozle.rinet.ru> <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 4 Jul 2008, Marcel Moolenaar wrote: MM> > doesn't splitting uart out of kernel broke serial console? Last time I MM> > checked MM> > it did. MM> MM> Yes, it does. The serial console is setup/initialized and MM> used before pre-loaded modules are linked and/or usable. MM> We don't have the support in place that allows you to boot MM> without console until pre-loaded modules are initialized, MM> at which time add a low-level console device is setup. MM> It's not that hard to do, I think. MM> MM> So, currently low-level console drivers, such as dcons(4), MM> sio(4) and uart(4) need to be compiled into the kernel. MM> Consequently any devices/busses to which any of these can MM> attach must be compiled into the kernel as well. Of these MM> acpi(4) and puc(4) are good examples. acpi(4) is a good MM> example because we use hints to work around the issue and MM> have sio(4) attach to isa(4) instead... Well, than, what is the reason to keep puc(4) out of GENERIC then? ;-P Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080705011154.G97379>