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_at_FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck_at_rinet.ru *** ------------------------------------------------------------------------Received on Fri Jul 04 2008 - 07:59:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:32 UTC