[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140508215338.GE2198@atomide.com>
Date: Thu, 8 May 2014 14:53:38 -0700
From: Tony Lindgren <tony@...mide.com>
To: Tomi Valkeinen <tomi.valkeinen@...com>
Cc: Peter Griffin <peter.griffin@...aro.org>,
Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
linaro-kernel@...ts.linaro.org,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
linux-fbdev@...r.kernel.org, linux-omap@...r.kernel.org,
Aaro Koskinen <aaro.koskinen@....fi>,
Janusz Krzysztofik <jmkrzyszt@...il.com>
Subject: Re: [PATCH 13/13] video: omap: allow building on !MMU
* Tomi Valkeinen <tomi.valkeinen@...com> [140507 02:15]:
> On 24/04/14 15:28, Peter Griffin wrote:
> > From: Arnd Bergmann <arnd@...db.de>
> >
> > The omap lcdc driver has an elaborate mmap_kern function
> > to map the frame buffer into kernel address space as
> > write-combined. This uses functions that are only available
> > on MMU-enabled builds.
> >
> > It does seem equivalent to ioremap_wc though, so we should
> > be able to just use that instead.
> >
> > This patch is build-tested only, it needs to be run on real
> > hardware before applying.
>
> I don't have omap1 boards, and I don't know anyone that has. I don't
> even know if the omap1 fb is working or not...
>
> Tony, any idea of omap1's fb? Are you able to test this?
I have three omap1 boards in my rack that I use for my boot
testing. Tried to enable framebuffer but so far no luck on
any of them. So I'm not much of a help here. Looks like the
patch should work though..
Aaro & Janusz, care to take a look at the patch in this
thread?
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists