mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: murtuja bharmal <murtuja_bharmal@yahoo.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: Linux 2.6 kernel module compilation without using KBUILD
Date: Wed, 28 Nov 2007 04:56:42 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0711280453330.3612@localhost.localdomain> (raw)
In-Reply-To: <180651.51647.qm@web36715.mail.mud.yahoo.com>

On Wed, 28 Nov 2007, murtuja bharmal wrote:

> Hello Sam,
>
> My intention is to just understand whole process of making kernel
> module. Actually I am working on one project in which I have to port
> lots of 2.4 kernel module in 2.6 kernel. So I thought lets first try
> to understand, what is going behind KBUILD. I also gone through
> linux/Documentation/kbuild/ but didn't get very much information.
> Even after running it on Verbose Mode, I am not very much clear.
>
> Thanks
> Murtuja Bharmal

you'd probably be better off asking this on the kernel newbies list
rather than the main kernel list.  and, as an intro to porting 2.4 to
2.6 modules, you might want to start here:

http://lwn.net/Articles/driver-porting/

and, as others have suggested, you're probably better off just
figuring out the 2.6 kbuild structure.  trying to do this manually
without kbuild is just making this way more difficult than it has to
be.

rday

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

  reply	other threads:[~2007-11-28  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28  8:09 murtuja bharmal
2007-11-28  9:00 ` Sam Ravnborg
2007-11-28  9:53   ` murtuja bharmal
2007-11-28  9:56     ` Robert P. J. Day [this message]
2007-11-28 10:40       ` murtuja bharmal
2007-11-28 10:59     ` 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=alpine.LFD.0.9999.0711280453330.3612@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=murtuja_bharmal@yahoo.com \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®