Re: changes required for making modular driver -> a buitl-in one

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

 



hi Anupam,
u've answered my question with another question of urs...who's answer
i don't know :P!!

what i meant was that are there any code level changes that would be
required to be done in my driver to make it work as a built-in
driver??? but i guess i have got the my answer now. thanks!

-mandeep


On Tue, 2004-10-05 at 15:23, Anupam Kapoor wrote:
> On Tue, 05 Oct 2004 10:30:47 +0530, Mandeep Sandhu
> <mandeep_sandhu@xxxxxxxxxxx> wrote:
> > hi list,
> > 
> > just a small Q. what are the changes required for making a modular
> > driver a built-in one??? Are the entry/exit points of a module
> > ([init/cleanup]_module) called for a built-in one too? I think the
> > answer wud be no....but i'm not too sure. What fxn.s are called
> > for initialization for a built-in driver?
> how is a non-trivial initialization/cleanup going to happen if your
> init/exit function is not called ?
> 
> kind regards
> anupam
> 
> > 
> > TIA,
> > -mandeep

--
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