On Fri, Oct 12, 2012 at 04:54:34PM +0100, Russell King - ARM Linux wrote: > For those who don't bother looking at my kautobuild boot tests on the OMAP > boards I have, here's the errors which get spat out at boot time. Note > that some of these I've reported in the past, and one of them is missing > a newline character at the end of its string. > > twd: can't register interrupt 45 (-22) > twd_local_timer_register failed -22 > omap_hwmod: mcpdm: cannot be enabled for reset (3) > omap-gpmc omap-gpmc: error: clk_get > omap-gpmc: probe of omap-gpmc failed with error -2 > Error setting wl12xx data: -38 > omap_hsmmc omap_hsmmc.1: Failed to get debounce clk > omap_hsmmc omap_hsmmc.0: Failed to get debounce clk > omap_hsmmc omap_hsmmc.4: Failed to get debounce clk > twl6040-codec twl6040-codec: ASoC: Failed to create Capture debugfs file > omap_vc_i2c_init: I2C config for vdd_iva does not match other channels (0). > omap_vc_i2c_init: I2C config for vdd_mpu does not match other channels (0).Power Management for TI OMAP4. > mmc1: host does not support reading read-only switch. assuming write-enable. Here's the latest set of error like messages, thanks to the kautobuild system: omap_hwmod: mcpdm: cannot be enabled for reset (3) Error setting wl12xx data: -38 omap_hsmmc omap_hsmmc.1: Failed to get debounce clk omap_hsmmc omap_hsmmc.0: Failed to get debounce clk omap_hsmmc omap_hsmmc.4: Failed to get debounce clk omap_vc_i2c_init: I2C config for vdd_iva does not match other channels (0). omap_vc_i2c_init: I2C config for vdd_mpu does not match other channels (0).Power Management for TI OMAP4. mmc1: host does not support reading read-only switch. assuming write-enable. This looks much better compared to the previous set, but we could still do with getting a "\n" on at least one of those messages... -- 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
