From: Willy Tarreau <willy@w.ods.org>
To: Massimo De Beni <maxdb82@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Make my own modules for kernel 2.4.32
Date: Tue, 31 Jan 2006 21:08:35 +0100 [thread overview]
Message-ID: <20060131200835.GA7142@w.ods.org> (raw)
In-Reply-To: <f4fb6a4d0601310239o5cf95887y@mail.gmail.com>
Hi,
On Tue, Jan 31, 2006 at 11:39:25AM +0100, Massimo De Beni wrote:
> Hi all,
> I'm a newbye to kernel 'modding' and I've a question that may seems
> outdated... The situation is this:
> I worked to get a Set Top Box to work with the latest stable 2.4
> kernel, the way is clear but the box need some modules to be loaded at
> boot in order to get the video and audio device to work (modules that
> are not shipped in kernels 2.4...); now I'm building those modules
> separatly, compiling directly the drivers source codes with 'make',
> and then I insert the .o with 'insmod'.
> I would create a better system in which one could compile those
> modules directly on the 'make menuconfig' of the kernel, so I'm
> modifying the various Makefiles && config files, but I'm a bit
> confused... Any good hint?
You have to add an 'obj-m' entry to the Makefile located in the same
directory as your driver, and make it depend on an option which will
be enabled in some Config.in (in the same directory if possible).
You should look at any driver provided as a patch for the kernel, it
will be fairly easier for you to understand what they touch. And don't
forget one important thing : always ensure that the kernel still builds
with your module disabled. Also, don't forget to add an entry in the
Configure.help file.
> Thanks in advance...!
Regards,
Willy
prev parent reply other threads:[~2006-01-31 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 10:39 Make my own modules for kernel 2.4.32 Massimo De Beni
2006-01-31 20:08 ` Willy Tarreau [this message]
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=20060131200835.GA7142@w.ods.org \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxdb82@gmail.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