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
| ||
|
Date: Mon, 17 Jul 2006 16:10:41 +0530 (IST) From: Subbu <subbu@...ken.com> To: linux-kernel@...r.kernel.org, linux-net@...r.kernel.org cc: linuxanimesh@...iffmail.com, subbu2k_av@...oo.com Subject: Compiling Driver code for 2.6 kernel 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). 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. I understand the compilation for 2.6 is different. How i can generate .ko which is required for 2.6. 1) Is a simple Makefile changes for 2.4 to 2.6 enough..?? then what needs to done in my GNUmakefile(not the kernel source) 2) Is it required to use kernel source GNUMakefile as given in examples *** 3) Is it o.k to compile individual 'c' files with .obj and linked to module.o Please help me in this regards THanx in advance Subbu "SASKEN RATED Among THE Top 3 BEST COMPANIES TO WORK FOR IN INDIA - SURVEY 2005 conducted by the BUSINESS TODAY - Mercer - TNS India" SASKEN BUSINESS DISCLAIMER This message may contain confidential, proprietary or legally Privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, Disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email - 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/
Powered by blists - more mailing lists