From: Massimo De Beni <maxdb82@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Make my own modules for kernel 2.4.32
Date: Tue, 31 Jan 2006 11:39:25 +0100 [thread overview]
Message-ID: <f4fb6a4d0601310239o5cf95887y@mail.gmail.com> (raw)
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?
Thanks in advance...!
next reply other threads:[~2006-01-31 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 10:39 Massimo De Beni [this message]
2006-01-31 20:08 ` Make my own modules for kernel 2.4.32 Willy Tarreau
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=f4fb6a4d0601310239o5cf95887y@mail.gmail.com \
--to=maxdb82@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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