e: [PATCH 02/14] omap: Map only available sram memory
>
> > Looks like for you " is_sram_locked" function is failing. There was a
> patch
> > in my series from Vikram which was fixing this API.
> >
> > Do you have this patch applied when you are trying
* Tony Lindgren [101004 17:26]:
> * Grazvydas Ignotas [101004 16:35]:
> > > Looks like for you " is_sram_locked" function is failing. There was a
> > > patch
> > > in my series from Vikram which was fixing this API.
> > >
> > > Do you have this patch applied when you are trying this out ?
> > >
* Grazvydas Ignotas [101004 16:35]:
> > Looks like for you " is_sram_locked" function is failing. There was a patch
> > in my series from Vikram which was fixing this API.
> >
> > Do you have this patch applied when you are trying this out ?
> > http://www.spinics.net/linux/lists/arm-kernel/msg986
> Looks like for you " is_sram_locked" function is failing. There was a patch
> in my series from Vikram which was fixing this API.
>
> Do you have this patch applied when you are trying this out ?
> http://www.spinics.net/linux/lists/arm-kernel/msg98697.html
Well it looks like this only happens o
; linux-arm-
> ker...@lists.infradead.org; Russell King - ARM Linux
> Subject: RE: [PATCH 02/14] omap: Map only available sram memory
>
> > -Original Message-
> > From: Grazvydas Ignotas [mailto:nota...@gmail.com]
> > Sent: Monday, October 04, 2010 2:34 PM
> > To: S
e: [PATCH 02/14] omap: Map only available sram memory
>
> >> >
> >> > This hangs OMAP3 pandora:
> >> >
> >> > [ 0.00] Linux version
> >> > 2.6.36-rc6-next-20101001-2-ge76bb53-dirty (no...@pixelinis) (gcc
> >> >
>> >
>> > This hangs OMAP3 pandora:
>> >
>> > [ 0.00] Linux version
>> > 2.6.36-rc6-next-20101001-2-ge76bb53-dirty (no...@pixelinis) (gcc
>> > version 4.3.3 (Sourcery G++ Lite 2009q1-20
>> > [ 0.00] CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7),
>> cr=10c53c7f
>> > [ 0.000
e: [PATCH 02/14] omap: Map only available sram memory
>
> * Grazvydas Ignotas [101001 13:07]:
> > On Fri, Sep 17, 2010 at 12:47 PM, Santosh Shilimkar
> > wrote:
> > > Currently we map 1 MB section while setting up SRAM on OMAPs.
> > > The actual physcal OCM
* Grazvydas Ignotas [101001 13:07]:
> On Fri, Sep 17, 2010 at 12:47 PM, Santosh Shilimkar
> wrote:
> > Currently we map 1 MB section while setting up SRAM on OMAPs.
> > The actual physcal OCM RAM available on OMAP SOCs is in order
> > of KBs. This patch maps only available sram and removes some
>
On Fri, Sep 17, 2010 at 12:47 PM, Santosh Shilimkar
wrote:
> Currently we map 1 MB section while setting up SRAM on OMAPs.
> The actual physcal OCM RAM available on OMAP SOCs is in order
> of KBs. This patch maps only available sram and removes some
> non necessary cpu_is_xxx checks.
>
> On the ne
> -Original Message-
> From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
> Sent: Friday, September 17, 2010 3:46 PM
> To: Shilimkar, Santosh
> Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
> Subject: Re: [PATCH 02/14] omap: Map only ava
On Fri, Sep 17, 2010 at 03:17:46PM +0530, Santosh Shilimkar wrote:
> Currently we map 1 MB section while setting up SRAM on OMAPs.
> The actual physcal OCM RAM available on OMAP SOCs is in order
physical
> of KBs. This patch maps only available sram and removes some
> non necessary cpu_is_xxx che
Currently we map 1 MB section while setting up SRAM on OMAPs.
The actual physcal OCM RAM available on OMAP SOCs is in order
of KBs. This patch maps only available sram and removes some
non necessary cpu_is_xxx checks.
On the newer ARMs with speculation, this is dangerous and can
result in untracea
13 matches
Mail list logo