Re: Compiling module into the kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Well, module_init is not being called, since you are now hard-coding the
module-code within the Kernel image.  I don't know the specifics, but
the initialization primitives are different(check the LDD online book).

-- Kashif

On Thu, 2002-06-27 at 11:25, TAJTHY Tamás wrote:
> Dear List,
> 
> I wrote a module (supporting nonstandard rtc devices). I have tested it and 
> it is working nicely.
> 
> I put it under drivers/char directory. I modified Config.in in this directory 
> (CONFIG_RTC_NONSTANDARD). I also modified Makefile in this dir adding 
> 
> obj-$(CONFIG_RTC_NONSTANDARD) += rtc_nostd.o
> 
> I typed
> 
> # make menuconfig
> 
> I set to <M> and I typed
> 
> # make zImage modules
> 
> The module was created and it worked nicely! 
> 
> Now I tried to compile to module into the kernel, so I set <*> in make 
> menuconfig.
> 
> make zImage
> 
> the device was not working. 
> 
> I checked the compiled kernel image and it is bigger, so it seems the module 
> code is compiled into the kernel.
> 
> How can I compile the module code into the kernel and make it run?
> 
> TIA && Good byte!
> 
> 
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive:       http://mail.nl.linux.org/kernelnewbies/
> FAQ:           http://kernelnewbies.org/faq/


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux