From: Arjan van de Ven <arjan@infradead.org>
To: Subbu <subbu@sasken.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
linuxanimesh@rediffmail.com, subbu2k_av@yahoo.com
Subject: Re: Compiling Driver code for 2.6 kernel
Date: Mon, 17 Jul 2006 12:47:18 +0200 [thread overview]
Message-ID: <1153133258.3062.20.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.GSO.4.64.0607171557040.15797@sunm21.sasken.com>
On Mon, 2006-07-17 at 16:10 +0530, Subbu wrote:
>
> Hi,
>
> Please Help me as i am newbie to 2.6 kernel.
>
> I have My driver code for 2.4.20 kernel(Here i generate .o with 100's
> of .objs linked together).
wow that's a lot; I suspect you're going to want to consolidate that
somewhat when you send your driver for inclusion into the kernel.org
kernel
> I have a main GNUMakefile linked with 10's of individual make files
> w.r.t different directories
>
> i am able to compile my source code and able to link all individual
> modules and generate final module.o (2.6). but i am not sure how to
> genrate .ko from the module.o i have.
see Documentation/kbuild directory, it has many examples on this
but... it sounds like you oversplit your module... do you have a pointer
to the source of it? Maybe I can give some useful suggestions on how to
organize it...
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2006-07-17 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 10:58 kernel thread priority Subbu
2006-07-07 12:34 ` linux-os (Dick Johnson)
2006-07-17 10:40 ` Compiling Driver code for 2.6 kernel Subbu
2006-07-17 10:47 ` Arjan van de Ven [this message]
2006-07-20 8:16 ` Memory allocation Failure problem with kmalloc Subbu
2006-07-20 8:27 ` Jesper Juhl
2006-07-20 10:54 ` Jan Engelhardt
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=1153133258.3062.20.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linuxanimesh@rediffmail.com \
--cc=subbu2k_av@yahoo.com \
--cc=subbu@sasken.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
all inboxes | Powered by JetHome®