* Kevin Hilman <khilman@xxxxxx> [120207 13:38]: > Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> writes: > > [...] > > > Another problem oopses the kernel at boot in the voltage domain code, > > which I suspect this has never been boot tested on OMAP34xx CPUs: > > > > omap_vc_init_channel: PMIC info requried to configure vc forvdd_core not populated.Hence cannot initialize vc > > Unable to handle kernel NULL pointer dereference at virtual address 00000000 ... > > [<c03db824>] (omap_vp_init+0x0/0x15c) from [<c03db448>] (omap_voltage_late_init+ > > 0xc4/0xfc) ... > > FWIW, this problem has been fixed for some time, and in my > for_3.3/cleanup/pm branch (and included in Tony's cleanup branch) which > was supposed to be merged for v3.3. Yes sorry I guess I did not realize it was a fix. This was one of the three branches that were left out of the last merge window because it was getting too. I assume you're talking about commit af9a2ed9667b49e7e125eac526d8f655183ce53e? Regards, Tony -- 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