[RFC] Initial attempt to make ARM use LMB

Grazvydas Ignotas notasas at gmail.com
Fri May 14 06:11:43 EDT 2010


On Fri, May 14, 2010 at 10:24 AM, Shilimkar, Santosh
<santosh.shilimkar at ti.com> wrote:
>> On Thu, May 13, 2010 at 03:01:39PM -0700, Tony Lindgren wrote:
>> > * Russell King - ARM Linux <linux at arm.linux.org.uk> [100513 14:53]:
>> > > On Thu, May 13, 2010 at 02:19:51PM -0700, Tony Lindgren wrote:
>> > > > * Russell King - ARM Linux <linux at arm.linux.org.uk> [100513 10:35]:
>> > > > > And here's a patch which converts the OMAP FB code to use lmb_reserve
>> > > > > instead of poking about with bootmem stuff.  Untested, so I'd like to
>> > > > > hear back whether it works.
>> > > >
>> > > > Did a quick test with the following patches picked from your lmb
>> > > > branch on top of omap for-next branch:
>> > > >
>> > > > ARM: Remove useless linux/bootmem.h includes
>> > > > ARM: Ensure meminfo is sorted prior to sanity_check_meminfo
>> > > > ARM: initial LMB trial
>> > > > ARM: Move platform LMB memory reservations out of generic code
>> > > >
>> > > > and then this patch.
>> > > >
>> > > > It does not boot.. It seems to be related to the patch
>> > > > "ARM: initial LMB trial". If I only apply the first two patches
>> > > > above the system boots.
>> > >
>> > > Hmm, I'm sure it worked for me when I tested it out.  Could you try
>> > > booting with lmb=debug please?
>> >
>> > No other output with that it seems.
>>
>> Hang on, you didn't pick up ARM: Move memory mapping into mmu.c ?
>
> I just gave a try on OMAP3430 and it does boot for me. But fb doesn't
> seems to be working. I have tried this on Tony's "omap-testing"
> branch where the LMB support is pulled in
>
> *********************************************************
> omapfb omapfb: failed to allocate framebuffer
> omapfb omapfb: failed to allocate fbmem
> omapfb omapfb: failed to setup omapfb
> omapfb: probe of omapfb failed with error -12
> twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:
> ***********************************************************

It seems you are using DSS2/CONFIG_FB_OMAP2, looks like this patch is
for DSS1/CONFIG_FB_OMAP.

DSS2 does have a problem on linux-next after 'ARM: Prohibit ioremap()
on kernel managed RAM' because it also uses reserve_bootmem() in
drivers/video/omap2/vram.c and later ioremap on RAM. Perhaps LMB can
be used to fix that too?



More information about the linux-arm-kernel mailing list