On Tue, May 03, 2016 at 01:37:41PM -0500, Derald Woods wrote:
> On Sun, May 1, 2016 at 12:09 PM, Derald D. Woods
> wrote:
>
> > On 05/01/2016 08:58 AM, Tom Rini wrote:
> >
> >> On Sat, Apr 30, 2016 at 07:12:28PM -0500, Derald D. Woods wrote:
> >>
> >>> On 04/28/2016
On Sun, May 1, 2016 at 12:09 PM, Derald D. Woods
wrote:
> On 05/01/2016 08:58 AM, Tom Rini wrote:
>
>> On Sat, Apr 30, 2016 at 07:12:28PM -0500, Derald D. Woods wrote:
>>
>>> On 04/28/2016 06:34 PM, Tom Rini wrote:
>>>
On Thu, Apr 28, 2016 at 05:55:17PM -0500,
On 05/01/2016 08:58 AM, Tom Rini wrote:
On Sat, Apr 30, 2016 at 07:12:28PM -0500, Derald D. Woods wrote:
On 04/28/2016 06:34 PM, Tom Rini wrote:
On Thu, Apr 28, 2016 at 05:55:17PM -0500, Adam Ford wrote:
I am hoping to look at this tomorrow at work. Any suggested toolchain you
recommend?
On Sat, Apr 30, 2016 at 07:12:28PM -0500, Derald D. Woods wrote:
> On 04/28/2016 06:34 PM, Tom Rini wrote:
> >On Thu, Apr 28, 2016 at 05:55:17PM -0500, Adam Ford wrote:
> >
> >>I am hoping to look at this tomorrow at work. Any suggested toolchain you
> >>recommend?
> >gcc-4.9.x fails (too large),
On 04/28/2016 06:34 PM, Tom Rini wrote:
On Thu, Apr 28, 2016 at 05:55:17PM -0500, Adam Ford wrote:
I am hoping to look at this tomorrow at work. Any suggested toolchain you
recommend?
gcc-4.9.x fails (too large), gcc-5.3.x succeeds, gcc-6.x is also likely
fine but I haven't started using
On Wed, Apr 27, 2016 at 5:46 PM, Tom Rini wrote:
> While the OMAP3 has 64KiB of SRAM, per the TRM the download area is only
> from 0x4020 to 0x4020F000 and exceeding that will cause failure to
> boot. Further, we need to make sure that we don't run into
>
On Thu, Apr 28, 2016 at 05:55:17PM -0500, Adam Ford wrote:
> I am hoping to look at this tomorrow at work. Any suggested toolchain you
> recommend?
gcc-4.9.x fails (too large), gcc-5.3.x succeeds, gcc-6.x is also likely
fine but I haven't started using those SDKs I just made today.
--
Tom
I am hoping to look at this tomorrow at work. Any suggested toolchain you
recommend?
On Apr 28, 2016 5:45 PM, "Tom Rini" wrote:
> On Wed, Apr 27, 2016 at 06:46:36PM -0400, Tom Rini wrote:
>
> > While the OMAP3 has 64KiB of SRAM, per the TRM the download area is only
> > from
On Wed, Apr 27, 2016 at 06:46:36PM -0400, Tom Rini wrote:
> While the OMAP3 has 64KiB of SRAM, per the TRM the download area is only
> from 0x4020 to 0x4020F000 and exceeding that will cause failure to
> boot. Further, we need to make sure that we don't run into
> SRAM_SCRATCH_SPACE_ADDR as
While the OMAP3 has 64KiB of SRAM, per the TRM the download area is only
from 0x4020 to 0x4020F000 and exceeding that will cause failure to
boot. Further, we need to make sure that we don't run into
SRAM_SCRATCH_SPACE_ADDR as once SPL is running we will write values
there and would corrupt
10 matches
Mail list logo