On Tue, Mar 19, 2019 at 07:14:37AM -0400, Tom Rini wrote:
> The ISW_ENTRY_ADDR Kconfig option under mach-omap2 isn't a SoC specific
> notion but rather "where is our previous stage loaded in memory?"
> option. Make use of this on ARCH_KEYSTONE rather than SPL_TEXT_BASE for
> our HS builds that
On Thu, Mar 21, 2019 at 11:02:37AM +0530, Lokesh Vutla wrote:
> Hi Tom,
>
> On 20/03/19 8:09 PM, Tom Rini wrote:
> > On Wed, Mar 20, 2019 at 07:03:52PM +0530, Lokesh Vutla wrote:
> >>
> >>
> >> On 19/03/19 4:44 PM, Tom Rini wrote:
> >>> The ISW_ENTRY_ADDR Kconfig option under mach-omap2 isn't a
Hi Tom,
On 20/03/19 8:09 PM, Tom Rini wrote:
> On Wed, Mar 20, 2019 at 07:03:52PM +0530, Lokesh Vutla wrote:
>>
>>
>> On 19/03/19 4:44 PM, Tom Rini wrote:
>>> The ISW_ENTRY_ADDR Kconfig option under mach-omap2 isn't a SoC specific
>>> notion but rather "where is our previous stage loaded in
On Wed, Mar 20, 2019 at 07:03:52PM +0530, Lokesh Vutla wrote:
>
>
> On 19/03/19 4:44 PM, Tom Rini wrote:
> > The ISW_ENTRY_ADDR Kconfig option under mach-omap2 isn't a SoC specific
> > notion but rather "where is our previous stage loaded in memory?"
> > option. Make use of this on
On 19/03/19 4:44 PM, Tom Rini wrote:
> The ISW_ENTRY_ADDR Kconfig option under mach-omap2 isn't a SoC specific
> notion but rather "where is our previous stage loaded in memory?"
> option. Make use of this on ARCH_KEYSTONE rather than SPL_TEXT_BASE for
> our HS builds that are not using SPL
The ISW_ENTRY_ADDR Kconfig option under mach-omap2 isn't a SoC specific
notion but rather "where is our previous stage loaded in memory?"
option. Make use of this on ARCH_KEYSTONE rather than SPL_TEXT_BASE for
our HS builds that are not using SPL anyhow.
Cc: Vitaly Andrianov
Cc: Andrew F. Davis
6 matches
Mail list logo