Hi, On Thu, 14 Feb 2008, Russell King wrote:
> > > Yes, I read that and didn't get the answer to the question above. It's > > > unclear how: > > > > > > config CPU_FREQ_INTEGRATOR > > > tristate "CPUfreq driver for ARM Integrator CPUs" > > > depends on ARCH_INTEGRATOR && CPU_FREQ > > > > > > being under CPU_FREQ rather than ARCH_INTEGRATOR > > > > The doc says it looks at "the previous entry" and ARCH_INTEGRATOR isn't > > exactly the previous entry. > > Neither is CPU_FREQ "the previous entry". The documentation is unclear. > [..] > Well, I still don't have the necessary understanding to work out how > CPU_FREQ is preferred over ARCH_INTEGRATOR, even with your statements > that "it is the case". So I'm not in a position to improve the > documentation except by adding a sentence to suggest people ask you > about it. The best thing right now in such cases is to use menuconfig/xconfig and actually look at it. xconfig can even show the hidden entries, so it's also easier to answer why some entry isn't becoming a child entry. I can provide a technical explanation of what's happening, but it's likely to be even more confusing, I really have no good idea on how to translate what is quite easily visible in xconfig to actual written documentation. bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
