Opened 9 years ago
Closed 9 years ago
#5885 closed task (fixed)
Add [CONFIG_*] entries to "Kernel Configuration" sections and uniformize layout
Reported by: | Pierre Labastie | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.7 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
Adding CONFIG_* information makes it much easier to check whether you have enabled that switch in your kernel configuration. Otherwise, you need to unpack the kernel tarball and run the menu.
Furthermore, there are variations in the way the kernel options are shown (with [*] as shown in the kernel menu, or with ": Y" after the menu entry). I'd be inclined to propose that the actual "menuconfig" layout be used ([*] before the option), but that is not what we have in the template. On the other hand, this is like that on the LFS book kernel page. So please comment on the following proposition for the template:
<screen><literal>Master section ---> Subsection ---> [*/M] Required Option (with dependency) [CONFIG_REQU_OPT_DEP] <*/M> Required Option (without dependency) [CONFIG_REQU_OPT_NODEP] [ ] Incompatible option (with dependency) [CONFIG_INCOMP_OPT_DEP] < > Incompatible option (without dependency) [CONFIG_INCOMP_OPTION]</literal></screen>
That does not take care of the (rare) case where there are prentheses instead of brackets, but I hope developpers will use them when they are needed.
Change History (6)
comment:4 by , 9 years ago
Eventually found some information on internet for Wacom. Not sure it works, though.
comment:5 by , 9 years ago
Eventually, after some work with "real" kernel configuration parameters, here is what I put in the template. Please feel free to comment.
<screen><literal>Master section ---> Subsection ---> [*] Required parameter [CONFIG_REQU_PAR] <*> Required parameter (not as module) [CONFIG_REQU_PAR_NMOD] <*/M> Required parameter (could be a module) [CONFIG_REQU_PAR_MOD] <*/M/ > Optional parameter [CONFIG_OPT_PAR] [ ] Incompatible parameter [CONFIG_INCOMP_PAR] < > Incompatible parameter (even as module) [CONFIG_INCOMP_PAR_MOD]</literal></screen>
Here is a list of pages needing that change (there may still be false positives, sorry). I'll erase them when they are done. If an editor wants to make one of those changes, he or she should add his or her name to the line.