From: Tom Rini Date: Wed, 11 Mar 2015 12:00:28 -0400 Subject: [U-Boot] [PATCH V6 07/11] ARM: OMAP3: Get rid of omap3_gp_romcode_call and replace with omap_smc1 In-Reply-To: References: <1425939129-308-1-git-send-email-nm@ti.com> <1425939129-308-8-git-send-email-nm@ti.com> <20150311154845.GL32541@bill-the-cat> Message-ID: <20150311160028.GR32541@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Mar 11, 2015 at 10:53:41AM -0500, Nishanth Menon wrote: > On Wed, Mar 11, 2015 at 10:48 AM, Tom Rini 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 > > > > Reviewed-by: Tom Rini > > > > 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 -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: