public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: mru@users.sourceforge.net (Måns Rullgård)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Writing modules for 2.5
Date: 15 Apr 2003 13:28:21 +0200	[thread overview]
Message-ID: <p73adesxane.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <yw1x7k9w9flm.fsf@zaphod.guide.suse.lists.linux.kernel>

mru@users.sourceforge.net (Måns Rullgård) writes:

> What magic needs to be done when writing modules for linux 2.5.x?
> Insmod tells me "Invalid module format" and the kernel log says "No
> module found in object".  I've tried to mimic the foo.mod.c stuff in
> the kernel tree, but I can't figure out the right way to do it.

Welcome to the wonderful new world of in kernel module loading, finally
with understandable error messages. Now bad error reporting is not limited
to netlink anymore.

You need -DKBUILD_BASENAME=name

Also you need module_init/module_exit declarations.

-Andi

       reply	other threads:[~2003-04-15 11:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yw1x7k9w9flm.fsf@zaphod.guide.suse.lists.linux.kernel>
2003-04-15 11:28 ` Andi Kleen [this message]
2003-04-15 12:00   ` Writing modules for 2.5 Måns Rullgård
2003-04-15 12:05     ` Andi Kleen
2003-04-15 12:05   ` Måns Rullgård
2003-04-15 11:35     ` Alan Cox
2003-04-15 12:39       ` Måns Rullgård
2003-04-15 12:57         ` Russell King
2003-04-15 13:24           ` Dave Jones
2003-04-15 15:42           ` Måns Rullgård
2003-04-15 21:31             ` Russell King
2003-04-15 14:24         ` Alan Cox
2003-04-15 12:15     ` Andreas Henriksson
2003-04-15 12:30       ` Måns Rullgård
2003-04-15 12:58       ` Russell King
2003-04-15 11:15 Måns Rullgård
2003-04-15 14:24 ` Jonathan Corbet
2003-04-15 20:43 ` Sam Ravnborg

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=p73adesxane.fsf@oldwotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@users.sourceforge.net \
    /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