Re: e100 driver does not build

Bruce Ashfield <bruce.ashfield@...>

On 11-09-01 2:11 PM, Saxena, Rahul wrote:
Yes, the problem was due to missing dependent options..
I had incorrectly assumed that dependent options would get pulled in
or perhaps a error would be generated.
A warning can (and will) be generated for options that are
set by a BSP and don't end up in a final .config, but that's only
if you've placed them in a .cfg file and fed them through the
config auditing steps of the linux-yocto build (this is automatic).

dependencies won't be set automatically, it's the opposite,
you must ensure they are set or a particular Kconfig value must
select them.

It worked after I added following 3 options stated as dependent options
in a Kernel configuration database that I saw:


I am still iterating to check if all three of the above are really needed or
or if just the CONFIG_NET_PCI option is needed.

I had enabled the option using a .cfg file. Also checking again to see if a warning
gets generated when the dependent options are not included.

BTW what does a message such as following in the .config file mean ?

"CONFIG_xxxxx is not set"
It should be:

# CONFIG_foo is not set

And that is should be read as "config foo is disabled"



-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@...]
Sent: Wednesday, August 31, 2011 6:27 PM
To: Zanussi, Tom
Cc: Saxena, Rahul; yocto@...
Subject: Re: [yocto] e100 driver does not build

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






yocto mailing list
yocto mailing list

Join to automatically receive all group messages.