linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: yiding_wang@agilent.com
Cc: rddunlap@osdl.org, sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.72 module loading issue
Date: Thu, 24 Jul 2003 23:08:48 +0200	[thread overview]
Message-ID: <20030724210848.GB1176@mars.ravnborg.org> (raw)
In-Reply-To: <334DD5C2ADAB9245B60F213F49C5EBCD05D55226@axcs03.cos.agilent.com>

On Thu, Jul 24, 2003 at 11:11:24AM -0600, yiding_wang@agilent.com wrote:
> Hello Randy,
> 
> Thanks for the response.  I did not get time to look into this till now.  The way you suggested is to add module build process into kernel build.  This requires a user to build a loadable module with kernel together.  What I really want to is to have module build alone but include kernel symbols and variables so it will not have problem when loading.  The benefit of doing it is to make user and developer easy to change the code and rebuild without experiencing the kernel rebuild process every time.  I read those two documents and they mainly talking about how to build module with kernel together.

Please break your lines - they are very long..

It is well known that building drivers outside the kernel tree is not
supported in 2.6.0-test yet. This is one of the two issues remaining before
kbuild is ready. You will see them present on Andrew Morton's must-fix
list.

> In2.4.x, there is a "Rules.make" which has all needed symbols and variables defined.  I just includes that file for my module build and everything works perfectly.  Now in 2.5.x, those structure has been changed and the "rule" files seem to be relocated under "scripts" and being changed too.  I am trying to make use of those "rules" to make module build and load simpler compare with build module with kernel each time.
> 
> Any ideas?

Wait a little more, and it will be possible to build modules in a clean
way outside the kernel tree.

	Sam

  reply	other threads:[~2003-07-24 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 17:11 2.5.72 module loading issue yiding_wang
2003-07-24 21:08 ` Sam Ravnborg [this message]
2003-07-24 23:27   ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2003-07-23  6:29 yiding_wang
2003-07-22 22:27 yiding_wang
2003-07-23  3:14 ` Randy.Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030724210848.GB1176@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=yiding_wang@agilent.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).