Gadiyar, Anand wrote: > I get some "mux: Unknown ball ..." messages booting > v2.6.33-rc1 from Linux' tree (built with the omap3_defconfig). > > This was on a 3630 SDP. > > Won't be looking at this for a while, so just reporting it. > > - Anand > > 0x588 > [ 0.000000] mux: Unknown ball offset 0x58a > [ 0.000000] mux: Unknown ball offset 0x58c > [ 0.000000] mux: Unknown ball offset 0x58e > [ 0.000000] mux: Unknown ball offset 0x590 > [ 0.000000] mux: Unknown ball offset 0x578 > [ 0.000000] mux: Unknown ball offset 0x57a > [ 0.000000] mux: Unknown ball offset 0x57c > [ 0.000000] mux: Unknown ball offset 0x57e > [ 0.000000] mux: Unknown ball offset 0x580 > [ 0.000000] mux: Unknown ball offset 0x582 > [ 0.000000] mux: Unknown ball offset 0x584 > [ 0.000000] mux: Unknown ball offset 0x586 > [ 0.000000] mux: Unknown ball offset 0x570 > [ 0.000000] mux: Unknown ball offset 0x572 > [ 0.000000] mux: Unknown ball offset 0x40 > [ 0.000000] mux: Unknown ball offset 0x0 > [ 0.000000] mux: Unknown ball offset 0x2 > > .... > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html Try this in you .config CONFIG_OMAP_PACKAGE_CBB=y CONFIG_OMAP_PACKAGE_CUS=y CONFIG_OMAP_PACKAGE_CBP=y
-- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
