From: bskmohan@gmail.com (sri)
To: kernelnewbies@lists.kernelnewbies.org
Subject: building a specific driver in kernel src tree
Date: Mon, 9 May 2011 11:35:46 +0530 [thread overview]
Message-ID: <BANLkTi=NAnNxJ3v7U84OeV6gZMM4NnOiSg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=W1fXLSKSWnHiegNfawPH0zt9fCA@mail.gmail.com>
the config had it as CONFIG_E1000=y
Does =y or =m make any difference?
still not working.
On Mon, May 9, 2011 at 11:32 AM, Jeff Kirsher
<jeffrey.t.kirsher@intel.com>wrote:
> On Sun, May 8, 2011 at 22:49, sri <bskmohan@gmail.com> wrote:
> > Hi,
> >
> > As part of learning, I have added few debug statements to the code at
> > drivers/net/e1000/e1000_main.c (e1000_probe function).
> > Now to compile this, am doing make -C
> /lib/modules/2.6.18-194.el5PAE/build
> > M=`pwd` modules under drivers/net/e1000 dir.
> >
> > That is not compiling anything. But the same thing when I do in
> > drivers/net/e1000e, it is compiling and creating e1000e.ko file.
> >
>
> Check your kernel config file (which is .config) to make sure that
> CONFIG_E1000=m
>
> Then you should be able to run ` make drivers/net/e1000` to build the
> e1000 driver as a module
>
> > Any help on how to get e1000.ko?
> >
> > --Sri
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
> >
>
>
>
> --
> Cheers,
> Jeff
>
--
--
Krishna Mohan B
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110509/22e91dd3/attachment.html
next prev parent reply other threads:[~2011-05-09 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 5:49 building a specific driver in kernel src tree sri
2011-05-09 6:02 ` Jeff Kirsher
2011-05-09 6:05 ` sri [this message]
2011-05-09 6:19 ` Jeff Kirsher
2011-05-09 6:20 ` sri
[not found] ` <BANLkTim=tbUjLVWaVvnfXxXzJOAXD2epbg@mail.gmail.com>
2011-05-09 7:23 ` sri
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='BANLkTi=NAnNxJ3v7U84OeV6gZMM4NnOiSg@mail.gmail.com' \
--to=bskmohan@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).