* Vagrant Cascadian <vagr...@freegeek.org> [2011-04-15 15:45]: > i was kind of confused to see hamradio stuff defined in > debian/config/armel/config
Most generic options are defined in config/config. However, for reasons that are unknown to me, some options that I would personally consider generic are not listed in config/config but in the arch config files (it's probably just historic reasons and never got cleaned up). CONFIG_HAMRADIO is not defined in config/config but in kernelarch-x86/config. Since we also want it on ARM, I went ahead and added it to the ARM config. However, imho it would be very valuable to go through these options and discuss with the team whether it would make sense to move them to config/config instead. This would simplify all the arch configs. Another thing to mention is that you can add comments with #. As you create a new config, it would be great if you could document why certain options are enabled. For example, config.orion5x has: #. Needed e.g. on QNAP devices CONFIG_MTD_CFI_INTELEXT=y #. Needed e.g. on the D-Link DNS-323 CONFIG_MTD_CFI_AMDSTD=y -- 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
