Date: Mon, 28 Aug 1995 20:09:13 -0700 (PDT) From: Julian Elischer <julian@ref.tfs.com> To: bde@zeta.org.au (Bruce Evans) Cc: davidg@Root.COM, terry@artisoft.com, hackers@freefall.FreeBSD.org, julian@freefall.FreeBSD.org, terry@freefall.FreeBSD.org Subject: Re: Terry's changes.. Message-ID: <199508290309.UAA15647@ref.tfs.com> In-Reply-To: <199508290231.MAA25986@godzilla.zeta.org.au> from "Bruce Evans" at Aug 29, 95 12:31:38 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > >The SYSINIT stuff is about as conflicting as the PSEUDO_SET stuff for > >statically installed pseudo-devices. It trades the ability to linearly > >read down the init_main.c (which is unclear anyway because of the > >startinit return after fork returning to the calling assembly instead > >of calling an assembly routine at the ens of startinit) for the ability > >to linearly look down the header file kernel.h for gross initialization > >order. It also allows dropping in of binary modules, and because of the > > Couldn't some of it have stayed as direct function calls? It seems > excessive to use an init function just to print the copyright (I > had to introduce one because printf has the wrong type for an > init function). Yes you could, and I guess it's really a judgement call as to what level of granuality you want. If you think of a good granularity, then sure, you might as well do this.. Terry had a good example, which was moving the differnt copyright for the HP/ whatever FP code into that file, so that if it was linked in, the message would be printed at the beginning and if it wasn't the it wouldn't. the #ifdef's in init_main.c would go away.. My thought is that you would be welcome to agregate any functions that you think are never going to be individually removed, or are never going to hae anyone else wanting to put an initialisation BETWEEN them. > > I want to initialize clock interrupts earlier. This requires moving at > least part of initclocks() to machine-dependent code and initializing > curproc = &proc0 later. I don't want any non-determinism in the order > for this. Surely this makes it easier to move.. you just add a SYSINIT line with the appropriately modified value. can we read the cmos clock earlier too? I need it quite early in devfs > > Bruce >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508290309.UAA15647>