From mboxrd@z Thu Jan  1 00:00:00 1970
From: gaspa@yattaweb.it (Gasparini Andrea)
Date: Mon, 11 Apr 2011 22:19:46 +0200
Subject: order of call to built-in modules
In-Reply-To: <BANLkTikCZAUzjempBfOk+UOeHOM1PXM53A@mail.gmail.com>
References: <BANLkTikCZAUzjempBfOk+UOeHOM1PXM53A@mail.gmail.com>
Message-ID: <BANLkTik=z2HWnrDaqQtugGtt5i-MzEYARQ@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Hi David

On Mon, Apr 11, 2011 at 10:04 PM, David Shwatrz <dshwatrz@gmail.com> wrote:
> HI,
> The macros module_init() and module_exit() are used both in case
> a source is built-in (the code is called from the init stage) or as a
> kernel module (implementing a init_module symbol).
>
> In case 2 of /built-in/ modules ?I am wondering if it is
> possible to know by advance the order used to call the various
> module_init() entry points. Is it possible to fix this order?
> rgs,

If I recall correctly, the order is given by the Makefile, so to have
a driver being initialized before another one, you have to remangle
your Makefile tree to match the order you want.

Hope it helps.
bye
--
-gaspa-