From: murtuja bharmal <murtuja_bharmal@yahoo.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
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 02:40:32 -0800 (PST) [thread overview]
Message-ID: <815347.48604.qm@web36702.mail.mud.yahoo.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711280453330.3612@localhost.localdomain>
--- "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
> 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
>
========================================================================
>
Hello Robert,
I think I am not very much clear. Let me try to
clarify more.
My intention is not build or port kernel driver
without using KBUILD.
I know about driver porting and Writing makefile using
KBUILD.
I don't have any issue about that.
I just want understand the whole process for clearity
thats it.
unfortunately I didn't get any answer from linux-doc
and linux-admin about this issue.
Let me try to understand KBUILD internal architecture
more by self.
Any Way.
Thanks for your view.
Murtuja Bharmal
____________________________________________________________________________________
Be a better pen pal.
Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/
next prev parent reply other threads:[~2007-11-28 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 8:09 Linux 2.6 kernel module compilation without using KBUILD 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
2007-11-28 10:40 ` murtuja bharmal [this message]
2007-11-28 10:59 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2007-11-28 6:11 murtuja bharmal
2007-11-28 10:00 ` Adam T. Bowen
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=815347.48604.qm@web36702.mail.mud.yahoo.com \
--to=murtuja_bharmal@yahoo.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.