On Mon, 2004-07-05 at 17:52, Wolfgang Grandegger wrote: > On 07/05/2004 05:22 PM Philippe Gerum wrote: > > On Mon, 2004-07-05 at 17:17, Gilles Chanteperdrix wrote: > >> Wolfgang Grandegger wrote: > >> > $ grep LATENCY config.log > >> > #define CONFIG_RTAI_SCHED_8254_LATENCY > >> > #define CONFIG_RTAI_SCHED_APIC_LATENCY > >> > >> These constants do not have the same name in Kconfig and configure.in, > >> hence the problems you see. > >> > >> I saw and fixed the same problem for CONFIG_RTAI_HW_NRCPUS but did not > >> see that some other constants had the problem. > > > > RTAI_HW_* is fusion stuff. I checked in vesuvio, and all seems to be ok > > in this respect. However, PPC did not define those symbols in Kconfig; > > Wolfgang, did you add them as strings (and not bools) there? > > I copied and modified the definition: > > config RTAI_SCHED_8254_LATENCY > string "8254 tuning latency (ns)" > default 4700 > > from i386/Kconfig. But the problem is that in "configure.in" around the > latency value checks there is: > > if test "$CONFIG_X86" = y; then > ... > fi >
Ok, I understand now. I overlooked that. > Well, at least CONFIG_RTAI_SCHED_8254_LATENCY is useful as general timer > latency value for non-x86 archs as well because they are used indirectly > by the scheduler. > Ok, so let's kill the X86 test then. I've removed it in the CVS. > Wolfgang. > > > > > > -- Philippe.
