linux-kernel - Re: Compiling Driver code for 2.6 kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 17 Jul 2006 12:47:18 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Subbu <subbu@...ken.com>
Cc:	linux-kernel@...r.kernel.org, linux-net@...r.kernel.org,
	linuxanimesh@...iffmail.com, subbu2k_av@...oo.com
Subject: Re: Compiling Driver code for 2.6 kernel

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/