From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Tom Zanussi <tom.zanussi@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: e100 driver does not build
Date: Wed, 31 Aug 2011 21:26:52 -0400 [thread overview]
Message-ID: <4E5EDF5C.6030605@windriver.com> (raw)
In-Reply-To: <1314832701.29348.32.camel@elmorro>
On 11-08-31 7:18 PM, Tom Zanussi wrote:
>
> On Wed, 2011-08-31 at 16:04 -0700, Saxena, Rahul wrote:
>> I am unable to get the e100 driver to build for my BSP.
>>
>> I have configured to build it as a module. I do not see the e100.ko
>> file being generated nor does
>>
>> CONFIG_E100 appear in the generated .config file in my build area.
>>
>>
>>
>> However I do see the driver source file e100.c in
>> tmp/work/bspname-poky-linux/linux-yocto-3.0.3+git1
>> +xxxx ../linux/drivers/net
>>
>>
>>
>> I do not have any problems with other drivers (igb, E1000 etc) that I
>> have configured in exactly similar way.
>>
>>
>>
>> Any insight on this issue ?
>>
>
> It's probably missing another option it depends on e.g. is
> CONFIG_NET_PCI and CONFIG_MII enabled in your .config?
This is most likely what it is.
Out of curiosity, how did you enable the option ? Via a config fragement
(.cfg file) or via menuconfig .. or something else?
If you tried to set something via a fragment and it doesn't make it to
the final .config, you should see a warning during the kernel build
phase.
Cheers,
Bruce
>
> Tom
>
>>
>>
>> Thanks
>>
>> Rahul
>>
>>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2011-09-01 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 23:04 e100 driver does not build Saxena, Rahul
2011-08-31 23:18 ` Tom Zanussi
2011-09-01 1:26 ` Bruce Ashfield [this message]
[not found] <4FF5AC937153B0459463C1A88EB478F2012E1E54F9@orsmsx505.amr.corp.intel.com>
2011-09-01 18:11 ` Saxena, Rahul
2011-09-01 18:20 ` Bruce Ashfield
2011-09-01 18:21 ` Tom Zanussi
2011-09-01 18:34 ` Saxena, Rahul
2011-09-01 18:40 ` Tom Zanussi
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=4E5EDF5C.6030605@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=tom.zanussi@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.