On Tuesday 17 May 2011 22:35:09 Steve Calfee wrote: > I think the generally accepted method of doing stuff like this is to > have the ifdeffery in a header file where a inline code segment is > defined if it applies to the processor being built. If the code does not > apply to the model being built, a null #define is used, which does not > take any space. We have for example omap2plus_defconfig, which include support for wide range of OMAP based devices, with different CPUs (OMAP2/3/4). So we need to have runtime distinction of the CPU we are running (since we run the same kernel binary on OMAP2/3/4). -- Péter -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
