Bruce, this is a long list of "invalids". Normally I'd take it, being x86, but given that there are a good number of generic items in the list, I wanted to see if you would have a look.

Yep. Let me take this first. It's part of the overall work I'm doing for 1.4 anyway.

Have you sync'd with Amy on this ? She was actively working on this a few days ago. I just want
to be sure that two people aren't doing the same thing.

If there are spare cycles, the h/w references getting bumped to 3.8 needs to be considered.

(In reply to comment #3)
> Have you sync'd with Amy on this ? She was actively working on this a few
> days ago. I just want
> to be sure that two people aren't doing the same thing.
> 

Yes, I've talked with Amy, She is supposed to be working on OVP, so she let us take it.

> If there are spare cycles, the h/w references getting bumped to 3.8 needs to
> be considered.

*env
branch master:10f40af173ec51cd6de130eb60511a9f1b444448
conf/local.conf
MACHINE ?= "atom-pc"

*problem
1, When kernel version is 3.4.34(default)
atom-pc.conf:
PREFERRED_VERSION_linux-yocto ?= "3.4%"

log.do_kernel_configcheck:
NOTE: validating kernel config, see log.do_kernel_configcheck for details
[non-hardware (11)]: meta/cfg/standard/atom-pc/specified_non_hdw.cfg
   This BSP sets config options that are possibly non-hardware related.

[invalid (1)]: meta/cfg/standard/atom-pc/invalid.cfg
   This BSP sets config options that are not offered anywhere within this kernel

specified_non_hdw.cfg:
CONFIG_ATH9K
CONFIG_ATH9K_COMMON
CONFIG_ATH9K_HW
CONFIG_CRC_CCITT
CONFIG_DRM
CONFIG_DRM_I915
CONFIG_DRM_I915_KMS
CONFIG_DRM_KMS_HELPER
CONFIG_STAGING
CONFIG_WEXT_PRIV
CONFIG_WIRELESS_EXT

invalid.cfg:
CONFIG_RT2860

2, When kernel version is 3.8.1
atom-pc.conf:
PREFERRED_VERSION_linux-yocto ?= "3.8%"

log.do_kernel_configcheck:
NOTE: validating kernel config, see log.do_kernel_configcheck for details
DEBUG: [non-hardware (4)]: meta/cfg/standard/atom-pc/specified_non_hdw.cfg
   This BSP sets config options that are possibly non-hardware related.

[invalid (1)]: meta/cfg/standard/atom-pc/invalid.cfg
   This BSP sets config options that are not offered anywhere within this kernel

specified_non_hdw.cfg:
CONFIG_CRC_CCITT
CONFIG_STAGING
CONFIG_WEXT_PRIV
CONFIG_WIRELESS_EXT

invalid.cfg:
CONFIG_RT2860

*analysis

1, Atom-pc defines the hardware-specific features in atom-pc-wifi.cfg:
  1 CONFIG_WIRELESS_EXT=y
  2 CONFIG_WEXT_PRIV=y
  3 
  4 CONFIG_ATH9K_HW=y
  5 CONFIG_ATH9K_COMMON=y
  6 CONFIG_ATH9K=y
  7 
  8 CONFIG_STAGING=y
  9 CONFIG_RT2860=y
 10 
 11 CONFIG_CRC_CCITT=y

2, CONFIG_RT2860 is invalid, because it is found in Linux kernels:
2.6.29–2.6.32, 2.6.33–2.6.39, and it is obsolete now. Use
CONFIG_RT2800PCI instead. 
drivers/net/wireless/rt2x00/Kconfig:
 56 config RT2800PCI
 ...
 66     ---help---
 67       This adds support for rt27xx/rt28xx/rt30xx wireless chipset family.
 68       Supported chips: RT2760, RT2790, RT2860, RT2880, RT2890, RT3052,
 69                RT3090, RT3091 & RT3092

3, STAGING is the menuconfig of RT2860, The menuconfig of current
RT2800PCI is RT2X00. Use CONFIG_RT2X00 instead of CONFIG_STAGING.

4, CONFIG_ATH9K_HW and CONFIG_ATH9K_COMMON could be removed,
because ATH9K has selected them.
drivers/net/wireless/ath/ath9k/Kconfig:
 18 config ATH9K
 ...
 21     select ATH9K_HW
 ...
 25     select ATH9K_COMMON

5, CONFIG_CRC_CCITT could be removed, because RT2800PCI has
selected it.
drivers/net/wireless/rt2x00/Kconfig:
 56 config RT2800PCI
 ...
 64         select CRC_CCITT

6, CONFIG_WIRELESS_EXT and CONFIG_WEXT_PRIV do nothing which means
they don't exist in the configure file `.config', maybe they could
be removed. I am not sure about the two params.

7, The reason why kernel 3.8 has less non-hardware warning then 3.4:
`drivers/net/wireless/ath/ath9k/Kconfig' and
`drivers/gpu/drm/Kconfig' are newly added in hardware.kcf.

http://cateee.net/lkddb/web-lkddb/RT2860.html
http://cateee.net/lkddb/web-lkddb/RT2800PCI.html
http://lxr.linux.no/linux/drivers/net/wireless/ath/ath9k/Kconfig
http://lxr.linux.no/linux/drivers/net/wireless/rt2x00/Kconfig

*solution
1, When Kernel version is 3.4.34(default)
diff --git a/meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg b/meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg
index e6cbc950..7226c08 100644
--- a/meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg
+++ b/meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg
@@ -1,11 +1,4 @@
-CONFIG_WIRELESS_EXT=y
-CONFIG_WEXT_PRIV=y
-
-CONFIG_ATH9K_HW=y
-CONFIG_ATH9K_COMMON=y
 CONFIG_ATH9K=y
 
-CONFIG_STAGING=y
-CONFIG_RT2860=y
-
-CONFIG_CRC_CCITT=y
+CONFIG_RT2X00=y
+CONFIG_RT2800PCI=y

diff --git a/meta/cfg/kernel-cache/bsp/atom-pc/hardware.kcf b/meta/cfg/kernel-cache/bsp/atom-pc/hardware.kcf
new file mode 100644
index 0000000..8700349
--- /dev/null
+++ b/meta/cfg/kernel-cache/bsp/atom-pc/hardware.kcf
@@ -0,0 +1,2 @@
+drivers/gpu/drm/Kconfig
+drivers/net/wireless/ath/ath9k/Kconfig

2, When Kernel version is 3.8.1

diff --git a/meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg b/meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg
index e6cbc950..7226c08 100644
--- a/meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg
+++ b/meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg
@@ -1,11 +1,4 @@
-CONFIG_WIRELESS_EXT=y
-CONFIG_WEXT_PRIV=y
-
-CONFIG_ATH9K_HW=y
-CONFIG_ATH9K_COMMON=y
 CONFIG_ATH9K=y
 
-CONFIG_STAGING=y
-CONFIG_RT2860=y
-
-CONFIG_CRC_CCITT=y
+CONFIG_RT2X00=y
+CONFIG_RT2800PCI=y

diff --git a/meta-yocto-bsp/conf/machine/atom-pc.conf b/meta-yocto-bsp/conf/machine/atom-pc.conf
index e97b173..1c9a94f 100644
--- a/meta-yocto-bsp/conf/machine/atom-pc.conf
+++ b/meta-yocto-bsp/conf/machine/atom-pc.conf
@@ -10,7 +10,7 @@ MACHINE_FEATURES = "screen keyboard pci usbhost ext2 ext3 x86 wifi acpi alsa"
 KERNEL_IMAGETYPE = "bzImage"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "3.4%"
+PREFERRED_VERSION_linux-yocto ?= "3.8%"
 PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
 XSERVER ?= "xserver-xorg \
            xserver-xorg-extension-glx \

Hi Bruce, 

Would you please give some suggestions about the following questions?

Q1, Which kernel version will be choosed, 3.4(current for atom-pc) or 3.8?
Q2, Is it correct to remove CONFIG_WEXT_PRIV and CONFIG_WIRELESS_EXT in atom-pc-wifi.cfg?

Thansk,
Hongxu

If not already, atom-pc will be moved to 3.8.

right. We are refreshing the h/w references to 3.8, now that the latest -stable
and -rt changes are in place.

Atom-pc is one of the easiest to move, so as part of this cleanup. Focuson 3.8
and with confirmed boot tests, we'll bump it to 3.8.

re: Q2, Is it correct to remove CONFIG_WEXT_PRIV and CONFIG_WIRELESS_EXT in atom-pc-wifi.cfg?

It is acceptable. If the options are no longer available in 3.8, then we should pull them out of the
fragments. We want the warnings to tell us this, so we'll follow the advice :)

Merged into master:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=9c22995dd4af48aa22d8abbe01113d9f34a51dad

Please verify.