* Re: e100 driver does not build [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 0 siblings, 2 replies; 8+ messages in thread From: Saxena, Rahul @ 2011-09-01 18:11 UTC (permalink / raw) To: yocto@yoctoproject.org 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. It worked after I added following 3 options stated as dependent options in a Kernel configuration database that I saw: CONFIG_ISA CONFIG_EISA CONFIG_NET_PCI 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" Thanks Rahul -----Original Message----- From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] Sent: Wednesday, August 31, 2011 6:27 PM To: Zanussi, Tom Cc: Saxena, Rahul; yocto@yoctoproject.org 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 >> 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: e100 driver does not build 2011-09-01 18:11 ` e100 driver does not build Saxena, Rahul @ 2011-09-01 18:20 ` Bruce Ashfield 2011-09-01 18:21 ` Tom Zanussi 1 sibling, 0 replies; 8+ messages in thread From: Bruce Ashfield @ 2011-09-01 18:20 UTC (permalink / raw) To: Saxena, Rahul; +Cc: yocto@yoctoproject.org 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: > > CONFIG_ISA > CONFIG_EISA > CONFIG_NET_PCI > > 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" Bruce > > > Thanks > Rahul > > -----Original Message----- > From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] > Sent: Wednesday, August 31, 2011 6:27 PM > To: Zanussi, Tom > Cc: Saxena, Rahul; yocto@yoctoproject.org > 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 >>> 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 > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: e100 driver does not build 2011-09-01 18:11 ` e100 driver does not build Saxena, Rahul 2011-09-01 18:20 ` Bruce Ashfield @ 2011-09-01 18:21 ` Tom Zanussi 2011-09-01 18:34 ` Saxena, Rahul 1 sibling, 1 reply; 8+ messages in thread From: Tom Zanussi @ 2011-09-01 18:21 UTC (permalink / raw) To: Saxena, Rahul; +Cc: yocto@yoctoproject.org On Thu, 2011-09-01 at 11:11 -0700, 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. > It worked after I added following 3 options stated as dependent options > in a Kernel configuration database that I saw: > > CONFIG_ISA > CONFIG_EISA > CONFIG_NET_PCI > > 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. > Note that it's also part of the intel-1xxxx feature, which is basically there for reusability - they were all together in a bunch of BSPs so I moved them into a feature. I'm wondering whether we want to break them up or at least create a separate e100 feature. > BTW what does a message such as following in the .config file mean ? > > "CONFIG_xxxxx is not set" > It means that config option was never set or got turned off because of unmet depencies. Tom > > Thanks > Rahul > > -----Original Message----- > From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] > Sent: Wednesday, August 31, 2011 6:27 PM > To: Zanussi, Tom > Cc: Saxena, Rahul; yocto@yoctoproject.org > 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 > >> 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 > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: e100 driver does not build 2011-09-01 18:21 ` Tom Zanussi @ 2011-09-01 18:34 ` Saxena, Rahul 2011-09-01 18:40 ` Tom Zanussi 0 siblings, 1 reply; 8+ messages in thread From: Saxena, Rahul @ 2011-09-01 18:34 UTC (permalink / raw) To: Zanussi, Tom; +Cc: yocto@yoctoproject.org Yes, I had noticed that it is part of intel-1xxxx feature also. I tend to think that it is better to separate out CONFIG_E100 option from intel-1xxxx I think that platforms that want 1G/10G enabled would not need 10/100 driver >> It means that config option was never set or got turned off because of unmet depencies << However I am not sure if this works in all cases as I did not see "# CONFIG_E100 is not set" even when its dependent configurations were not satisfied Rahul -----Original Message----- From: Zanussi, Tom Sent: Thursday, September 01, 2011 11:22 AM To: Saxena, Rahul Cc: yocto@yoctoproject.org Subject: Re: [yocto] e100 driver does not build On Thu, 2011-09-01 at 11:11 -0700, 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. > It worked after I added following 3 options stated as dependent options > in a Kernel configuration database that I saw: > > CONFIG_ISA > CONFIG_EISA > CONFIG_NET_PCI > > 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. > Note that it's also part of the intel-1xxxx feature, which is basically there for reusability - they were all together in a bunch of BSPs so I moved them into a feature. I'm wondering whether we want to break them up or at least create a separate e100 feature. > BTW what does a message such as following in the .config file mean ? > > "CONFIG_xxxxx is not set" > It means that config option was never set or got turned off because of unmet depencies. Tom > > Thanks > Rahul > > -----Original Message----- > From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] > Sent: Wednesday, August 31, 2011 6:27 PM > To: Zanussi, Tom > Cc: Saxena, Rahul; yocto@yoctoproject.org > 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 > >> 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 > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: e100 driver does not build 2011-09-01 18:34 ` Saxena, Rahul @ 2011-09-01 18:40 ` Tom Zanussi 0 siblings, 0 replies; 8+ messages in thread From: Tom Zanussi @ 2011-09-01 18:40 UTC (permalink / raw) To: Saxena, Rahul; +Cc: yocto@yoctoproject.org On Thu, 2011-09-01 at 11:34 -0700, Saxena, Rahul wrote: > Yes, I had noticed that it is part of intel-1xxxx feature also. > > I tend to think that it is better to separate out CONFIG_E100 option from intel-1xxxx > I think that platforms that want 1G/10G enabled would not need 10/100 driver > Yeah, makes sense. I can do that if you want, or you can - either way is fine with me... Tom > >> It means that config option was never set or got turned off because of > unmet depencies << > > However I am not sure if this works in all cases as I did not see > "# CONFIG_E100 is not set" even when its dependent configurations were not satisfied > > Rahul > > -----Original Message----- > From: Zanussi, Tom > Sent: Thursday, September 01, 2011 11:22 AM > To: Saxena, Rahul > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] e100 driver does not build > > On Thu, 2011-09-01 at 11:11 -0700, 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. > > It worked after I added following 3 options stated as dependent options > > in a Kernel configuration database that I saw: > > > > CONFIG_ISA > > CONFIG_EISA > > CONFIG_NET_PCI > > > > 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. > > > > Note that it's also part of the intel-1xxxx feature, which is basically > there for reusability - they were all together in a bunch of BSPs so I > moved them into a feature. I'm wondering whether we want to break them > up or at least create a separate e100 feature. > > > BTW what does a message such as following in the .config file mean ? > > > > "CONFIG_xxxxx is not set" > > > > It means that config option was never set or got turned off because of > unmet depencies. > > Tom > > > > > Thanks > > Rahul > > > > -----Original Message----- > > From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] > > Sent: Wednesday, August 31, 2011 6:27 PM > > To: Zanussi, Tom > > Cc: Saxena, Rahul; yocto@yoctoproject.org > > 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 > > >> 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 > > > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > ^ permalink raw reply [flat|nested] 8+ messages in thread
* e100 driver does not build @ 2011-08-31 23:04 Saxena, Rahul 2011-08-31 23:18 ` Tom Zanussi 0 siblings, 1 reply; 8+ messages in thread From: Saxena, Rahul @ 2011-08-31 23:04 UTC (permalink / raw) To: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 520 bytes --] 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 ? Thanks Rahul [-- Attachment #2: Type: text/html, Size: 2546 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: e100 driver does not build 2011-08-31 23:04 Saxena, Rahul @ 2011-08-31 23:18 ` Tom Zanussi 2011-09-01 1:26 ` Bruce Ashfield 0 siblings, 1 reply; 8+ messages in thread From: Tom Zanussi @ 2011-08-31 23:18 UTC (permalink / raw) To: Saxena, Rahul; +Cc: yocto@yoctoproject.org 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? Tom > > > Thanks > > Rahul > > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: e100 driver does not build 2011-08-31 23:18 ` Tom Zanussi @ 2011-09-01 1:26 ` Bruce Ashfield 0 siblings, 0 replies; 8+ messages in thread From: Bruce Ashfield @ 2011-09-01 1:26 UTC (permalink / raw) To: Tom Zanussi; +Cc: yocto@yoctoproject.org 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2011-09-01 18:40 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <4FF5AC937153B0459463C1A88EB478F2012E1E54F9@orsmsx505.amr.corp.intel.com>
2011-09-01 18:11 ` e100 driver does not build 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
2011-08-31 23:04 Saxena, Rahul
2011-08-31 23:18 ` Tom Zanussi
2011-09-01 1:26 ` Bruce Ashfield
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.