On Saturday 17 October 2015 12:53 AM, Tony Lindgren wrote:
> * Lokesh Vutla [151015 08:21]:
[..snip..]
>>>
>
> 8< --From c37732f6cea23d15fa357cf698833c03ce05 Mon
> Sep 17 00:00:00 2001
> Date: Fri, 16 Oct 2015 12:16:21 -0700
> Subject: [PATCH] ARM:
* Lokesh Vutla [151019 07:03]:
>
> Since there is a big hole with in the memory space, we might also need
> to enable SPARSEMEM ?
No from what I remember that depends on section sizes and smaller
chunks of physical memory. For example, on the old Psions we had to
use
* Lokesh Vutla [151015 08:21]:
> +Richard
>
> On Thursday 15 October 2015 07:35 PM, Tony Lindgren wrote:
> > * Lokesh Vutla [151015 01:02]:
> >> Hi Tony,
> >>
> >> On Wednesday 14 October 2015 09:32 PM, Tony Lindgren wrote:
> >>> * Lokesh Vutla
Hi Tony,
On Wednesday 14 October 2015 09:32 PM, Tony Lindgren wrote:
> * Lokesh Vutla [151013 20:53]:
>> Hi Tony,
>>
>> On Wednesday 14 October 2015 04:43 AM, Tony Lindgren wrote:
>>> On boards with more than 2GB of RAM booting goes wrong with things not
>>> working
>>> and
* Lokesh Vutla [151015 01:02]:
> Hi Tony,
>
> On Wednesday 14 October 2015 09:32 PM, Tony Lindgren wrote:
> > * Lokesh Vutla [151013 20:53]:
> >> Hi Tony,
> >>
> >> On Wednesday 14 October 2015 04:43 AM, Tony Lindgren wrote:
> >>> On boards with more than 2GB
+Richard
On Thursday 15 October 2015 07:35 PM, Tony Lindgren wrote:
> * Lokesh Vutla [151015 01:02]:
>> Hi Tony,
>>
>> On Wednesday 14 October 2015 09:32 PM, Tony Lindgren wrote:
>>> * Lokesh Vutla [151013 20:53]:
Hi Tony,
On Wednesday 14 October
* Lokesh Vutla [151013 20:53]:
> Hi Tony,
>
> On Wednesday 14 October 2015 04:43 AM, Tony Lindgren wrote:
> > On boards with more than 2GB of RAM booting goes wrong with things not
> > working
> > and we're getting lots of l3 warnings:
> >
> > WARNING: CPU: 0 PID: 1 at
* Arnd Bergmann [151014 02:20]:
> On Tuesday 13 October 2015 16:13:20 Tony Lindgren wrote:
> > On boards with more than 2GB of RAM booting goes wrong with things not
> > working
> > and we're getting lots of l3 warnings:
> >
> > WARNING: CPU: 0 PID: 1 at
On Tuesday 13 October 2015 16:13:20 Tony Lindgren wrote:
> On boards with more than 2GB of RAM booting goes wrong with things not working
> and we're getting lots of l3 warnings:
>
> WARNING: CPU: 0 PID: 1 at drivers/bus/omap_l3_noc.c:147
> l3_interrupt_handler+0x260/0x384()
> 4400.ocp:L3
On Wednesday 14 October 2015 09:17:56 Tony Lindgren wrote:
> * Arnd Bergmann [151014 02:20]:
> > On Tuesday 13 October 2015 16:13:20 Tony Lindgren wrote:
> > > On boards with more than 2GB of RAM booting goes wrong with things not
> > > working
> > > and we're getting lots of l3
* Suman Anna [151014 13:32]:
> On 10/14/2015 03:12 PM, Arnd Bergmann wrote:
> > On Wednesday 14 October 2015 09:17:56 Tony Lindgren wrote:
> >> * Arnd Bergmann [151014 02:20]:
> >>> On Tuesday 13 October 2015 16:13:20 Tony Lindgren wrote:
> On boards with more
On 10/14/2015 03:12 PM, Arnd Bergmann wrote:
> On Wednesday 14 October 2015 09:17:56 Tony Lindgren wrote:
>> * Arnd Bergmann [151014 02:20]:
>>> On Tuesday 13 October 2015 16:13:20 Tony Lindgren wrote:
On boards with more than 2GB of RAM booting goes wrong with things not
Hi Tony,
On Wednesday 14 October 2015 04:43 AM, Tony Lindgren wrote:
> On boards with more than 2GB of RAM booting goes wrong with things not working
> and we're getting lots of l3 warnings:
>
> WARNING: CPU: 0 PID: 1 at drivers/bus/omap_l3_noc.c:147
> l3_interrupt_handler+0x260/0x384()
>
On boards with more than 2GB of RAM booting goes wrong with things not working
and we're getting lots of l3 warnings:
WARNING: CPU: 0 PID: 1 at drivers/bus/omap_l3_noc.c:147
l3_interrupt_handler+0x260/0x384()
4400.ocp:L3 Custom Error: MASTER MMC6 TARGET DMM1 (Idle): Data Access in
User mode
14 matches
Mail list logo