lkml.org 
[lkml]   [2001]   [Oct]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: crc32 cleanups
On Sat, 13 Oct 2001, Keith Owens wrote:
> Does not work if all the code that uses crc32 is in a module. No
> references from the main kernel so crc32 is not included by the linker.

So make the CRC32 code a module itself ?

> ???! __initcall entries are executed in the order that they are linked
> into the kernel. The linkage order is controlled by the order that
> Makefiles are processed during kbuild and by line order within each
> Makefile. There is definitely a priority order for __initcall code.

That is in practice an unuseable "priority" (I'd like to consider that a
highly stochastic variable :)

Not to mention that as an individual sub-project maintainer you can't go
around changing higher level makefiles all the time just to get your
particular initcall chain in order (again, in practice).

You could _conceivably_ build an initcall dependency system by adding some
"initcall_requires" macros which put the dependant other calls into
another linker table, which the kernel would resolve at boot.

/BW

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:08    [W:0.095 / U:0.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site