Horst von Brand wrote:
>
> Jeff Garzik <garzik@havoc.gtf.org> said:
> > On Fri, Feb 01, 2002 at 03:03:13PM +0000, Alan Cox wrote:
> > > > If you have a dependency concern, you put yourself in the
> > > > right initcall group. You don't depend ever on the order within the
> > > > group, thats the whole idea. You can't depend on that, so you must
> > > > group things correctly.
>
> > > This was proposed right back at the start. Linus point blank vetoed it.
>
> > My ideal would be to express dependencies in driver.conf (when that is
> > implemented), and that will in turn affect the link order by
> > autogenerating part of vmlinux.lds. Until then, initcall groups are
> > fine with me...
>
> Not _one_ central file telling everything, please! Let each driver declare
> what it needs and provides, and sort it out from there.
"driver.conf" is a reference is a metadata file per driver or
per-subdirectory, not one big file.
Linus suggested this back in December. See the links I posted.
> Why do I have this uneasy feeling it would somehow overlap with CML2's job?
It could either (a) generate CML2 or (b) make CML2 irrelevant, depending
on the implementation.
Jeff
-- Jeff Garzik | "I went through my candy like hot oatmeal Building 1024 | through an internally-buttered weasel." MandrakeSoft | - goats.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Feb 07 2002 - 21:00:41 EST