Skip to contentSkip to conversation

using and auditing kernel config fragments

DISCUSSION Tomas Frydrych 3 participants 5 messages Apr 6, 2012

lore
Share & tools
lore
#0 lore raw

Hi,

I am trying to add a kernel config fragment to the yocto 2.6.37 kernel for BeagleBoard, because I need a driver for a rt2800usb dongle.

For some reason which I cannot work out, the rt2800usb options are removed (rather then disabled) from the yocto kernel config, i.e., if I run 'bitbake -c menuconfig linux-yocto', there is very little under Drivers->Net->WLAN. If I run menuconfig in the devshell, there are lots more WLAN drivers available, including the rt2800.

So, I created custom fragment with the appropriate options, which works to the extent it gets picked up, but then the options are removed during the kernel_configme process and end up in the missing_required.cfg, and there is no information I can find anywhere in the logs as to why this is the case. Any ideas how to find out what the problem is?

(I am using yocto master)

Tomas

#1 lore raw
Quoted 5 lines

For some reason which I cannot work out, the rt2800usb options are removed (rather then disabled) from the yocto kernel config, i.e., if I run 'bitbake -c menuconfig linux-yocto', there is very little under Drivers->Net->WLAN. If I run menuconfig in the devshell, there are lots more WLAN drivers available, including the rt2800.

Under Device Drivers -> Network device support -> Wireless LAN, You have to enable Ralink driver support to see the options for CONFIG_RT2800USB

It is not under Device Drivers -> Network device support -> Wireless LAN

It is under Device Drivers -> Network device support -> Wireless LAN -> Ralink driver support

#2 lore raw
Quoted 6 lines
Quoted 5 lines

For some reason which I cannot work out, the rt2800usb options are removed (rather then disabled) from the yocto kernel config, i.e., if I run 'bitbake -c menuconfig linux-yocto', there is very little under Drivers->Net->WLAN. If I run menuconfig in the devshell, there are lots more WLAN drivers available, including the rt2800.

Quoted 8 lines

Under Device Drivers -> Network device support -> Wireless LAN, You have to enable Ralink driver support to see the options for CONFIG_RT2800USB

It is not under Device Drivers -> Network device support -> Wireless LAN

It is under Device Drivers -> Network device support -> Wireless LAN -> Ralink driver support

I forgot to mention - Under Networking Support -> Wireless, you need to enable cfg80211 AND msc80211 (Generic IEEE 802.11 Netowrking Stack)

Then the Ralink driver support shows up under Wireless LAN

#3 lore raw
Quoted 4 lines · Autif Khan

I forgot to mention - Under Networking Support -> Wireless, you need to enable cfg80211 AND msc80211 (Generic IEEE 802.11 Netowrking Stack)

Then the Ralink driver support shows up under Wireless LAN

Thanks, that's the bit I was missing. :)

Tomas

#4 lore raw
In reply to Tomas Frydrych
Quoted 11 lines · Tomas Frydrych

Hi,

I am trying to add a kernel config fragment to the yocto 2.6.37 kernel for BeagleBoard, because I need a driver for a rt2800usb dongle.

For some reason which I cannot work out, the rt2800usb options are removed (rather then disabled) from the yocto kernel config, i.e., if I run 'bitbake -c menuconfig linux-yocto', there is very little under Drivers->Net->WLAN. If I run menuconfig in the devshell, there are lots more WLAN drivers available, including the rt2800.

Quoted 5 lines

So, I created custom fragment with the appropriate options, which works to the extent it gets picked up, but then the options are removed during the kernel_configme process and end up in the missing_required.cfg, and there is no information I can find anywhere in the logs as to why this is the case. Any ideas how to find out what the problem is?

If they end up in missing_required.cfg, it almost always means that a dependency of the options listed in your fragment haven't been specified and hence the option tossed out by lkc.

Looking via menuconfig or via the Kconfigs should show you what the dependencies are, and your .config will show you what was specified and ended up in the configuration. If dependencies are missing, add them to your fragment .. and they should make it to the end.

Cheers,

Bruce

Quoted 8 lines

(I am using yocto master)

Tomas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"