* Hector Oron <hector.o...@gmail.com> [2011-04-15 23:30]: > > - Why is network support system specific? > > Maybe it is wrong in the patch config, I really struggled with > configurations. I cross compile an uImage, test it on my system so I > got a working config, but when trying to port that to debian kernel I > really do not understand it very much. Help is appreciated.
The idea is to have a minimal config file. If it's listed in armel/config, you don't need to list it in armel/config.xxx. If it's listed in config/config, you don't need to list it in armel/config.xxx (the only exception I make to this rule is for stuff that's really crucial for a platform; in that case, I list it anyway since config/config could change and break the platform). If an option is selected by another option, you only need to list the latter (for example, ARCH_KIRKWOOD selects CPU_FEROCEON and PCI, so there's no need to add these two options to the config file). So basically: take the config file you sent and check if the options are listed in armel/config.xxx. or config/config. If they are there, drop them from your config. For example, the config you submitted contains CONFIG_NET=y but this is already listed in config/config so you can drop it. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
