On Wed, Mar 11, 2015 at 11:00 AM, Tom Rini <tr...@konsulko.com> wrote: > On Wed, Mar 11, 2015 at 10:53:41AM -0500, Nishanth Menon wrote: >> On Wed, Mar 11, 2015 at 10:48 AM, Tom Rini <tr...@konsulko.com> wrote: >> > On Mon, Mar 09, 2015 at 05:12:05PM -0500, Nishanth Menon wrote: >> > >> >> omap_smc1 is now generic enough to remove duplicate >> >> omap3_gp_romcode_call logic that omap3 introduced. >> >> >> >> As part of this change, move to using the generic lowlevel_init.S for >> >> omap3 as well. >> >> >> >> Signed-off-by: Nishanth Menon <n...@ti.com> >> > >> > Reviewed-by: Tom Rini <tr...@konsulko.com> >> > >> > But I've always wondered, does OMAP3 not actually pass in the same info >> > in the same location / manner as OMAP4 and later? >> >> For smc call, the calls are similar, but the parameters change > > Right, sorry but I mean for boot params as that's what's still being > omap3-specific in lowlevel_init.S
There seemed to be differences w.r.t bootdevice detection logic which seems to be extensive in omap3 :( had'nt dug too much there :( -- --- Regards, Nishanth Menon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
