Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: question about driver built-in kernel
Date: Thu, 17 Nov 2005 17:18:34 -0700
Message-ID: <08A354A3A9CCA24F9EE9BE13600CFBC501A31910@wcosmb07.cos.agilent.com>
Thread-Topic: question about driver built-in kernel
Thread-Index: AcXr1EDVuNTRj+e7QMyAOpBcIxCIsgAASNew
From: <yiding_wang@agilent.com>
To: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1278
Lines: 14

We have two driver modules to support our hardware for some applications. Both modules worked fine as loadable modules. Now I need to build both drivers in kernel 2.6.11-8. I have changed configuration file and make file. Both drivers are built OK with kernel together. Now I have two concerns:

1, Because both drivers were loaded as module before, the entry point for both driver is "init_module()". Since both drivers are built in kernel, the entry name is conflicting. Changing one entry point name will make driver built OK. However, I am concerned that loading kernel will not pick up the driver with changed entry point name. What is the best way to handle this situation?

2, One of built-in driver requires to be loaded before the second one. Because these two drivers are not belong to any existing group, such as network, scsi, where is the best place these two driver can be specified for loading sequence? I checked init.d and rc* files but did not figure out proper place to handle the requirement.

Many Thanks!

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