* 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 DISCONTIGMEM/SPARSEMEM becau
[PATCH] ARM: OMAP2+: Fix oops with LPAE and more than 2GB of memory
>
> 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
ssible beyond 2GB for the DMA hardware. I'll
> > post an updated patch with the 2GB limit for dma_zone_size after some
> > more tests.
> >
> > For the dma-ranges, looks like I have not hit that one yet. Which drivers
> > did you run into problem
+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 2015 04:43 AM, 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 2015 04:43 AM, Tony Lindgren wrote:
> >>> On boards with more than 2GB of RAM booting goes wrong with thing
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 we're getting lots of
* 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 than 2GB of RAM booting goes wr
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
working
a
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 warnings:
> > >
* 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 drivers/bus/omap_l3_noc.c:147
> > l3_int
* 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 drivers/bus/omap_l3_noc.c
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 Cus
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()
> 44
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