From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Date: Wed, 07 May 2014 09:14:27 +0000 Subject: Re: [PATCH 13/13] video: omap: allow building on !MMU Message-Id: <5369F973.10803@ti.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0" List-Id: References: <1398342509-10243-1-git-send-email-peter.griffin@linaro.org> <1398342509-10243-14-git-send-email-peter.griffin@linaro.org> In-Reply-To: <1398342509-10243-14-git-send-email-peter.griffin@linaro.org> To: Peter Griffin , Arnd Bergmann , Tony Lindgren Cc: linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org, Jean-Christophe Plagniol-Villard , linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 24/04/14 15:28, Peter Griffin wrote: > From: Arnd Bergmann >=20 > 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. >=20 > It does seem equivalent to ioremap_wc though, so we should > be able to just use that instead. >=20 > 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? Tomi --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJTaflzAAoJEPo9qoy8lh71mwEP/ixwXorGiw6rNjAy3+rQ/Ht3 d1rWch/w3Xtu+eSjKLKRDBcIKdo0FjU839RrPvFXd48ooo256tJn1hR/DKiysX2T 52uCv/FBJRHHdVvc7ujtwcKSzxL8y/xa9YYL7N3jFlGxbLUqWOJqKiji5fAR408H PV55iIV8sANH2RoWY5u8JL+UebSkj8GMsapRnf4+Pl30/H+oGRExD+xHEcT5e07/ 6F3P6b/FTkG/esI2XQIFx3df7vqpLf/myW3RtjOPd4yQZW3lW5LNZz4XZOuqunzG MeIX6e+6zFH/JiG/WR/xmeES/gEhTSx9gcOYykbWUDVZZGOp8R6TpsMZFSeLHama 6qNHtS7sYJfupZlyNUHQFvJiQiSe2rIOLIa3MQITuWCvh5vxoNQvGlElpumVIN7+ 817hmLIf5bQsQfOWTM6RwEuqnSA++2DKwOhkA0E+9sWT+ChZJ8AyVQhW0Jq5NrnW 34w17sJZFgXHdYkaDmwQb0TWlITJ3D0CKOpiCWEjo24Z5gAyP/pn/QTNAQQ8iVGD O35y4qDzQnPX6KSaalQMa/HystgqjuKITPmVmfzerxgCFpmjGgwQeIjKKqkrfv4h 7ZeZ8r8TsBLz8+aOPeJro6/cDrf3Z04f/a9s4czesat6F0kfQqi+PDGaH1r+4+XI 5kgARnLt/C5OSbEE+1sw =N6bJ -----END PGP SIGNATURE----- --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: [PATCH 13/13] video: omap: allow building on !MMU Date: Wed, 7 May 2014 12:14:27 +0300 Message-ID: <5369F973.10803@ti.com> References: <1398342509-10243-1-git-send-email-peter.griffin@linaro.org> <1398342509-10243-14-git-send-email-peter.griffin@linaro.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0" Return-path: In-Reply-To: <1398342509-10243-14-git-send-email-peter.griffin@linaro.org> Sender: linux-kernel-owner@vger.kernel.org To: Peter Griffin , Arnd Bergmann , Tony Lindgren Cc: linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org, Jean-Christophe Plagniol-Villard , linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org List-Id: linux-omap@vger.kernel.org --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 24/04/14 15:28, Peter Griffin wrote: > From: Arnd Bergmann >=20 > 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. >=20 > It does seem equivalent to ioremap_wc though, so we should > be able to just use that instead. >=20 > 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? Tomi --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJTaflzAAoJEPo9qoy8lh71mwEP/ixwXorGiw6rNjAy3+rQ/Ht3 d1rWch/w3Xtu+eSjKLKRDBcIKdo0FjU839RrPvFXd48ooo256tJn1hR/DKiysX2T 52uCv/FBJRHHdVvc7ujtwcKSzxL8y/xa9YYL7N3jFlGxbLUqWOJqKiji5fAR408H PV55iIV8sANH2RoWY5u8JL+UebSkj8GMsapRnf4+Pl30/H+oGRExD+xHEcT5e07/ 6F3P6b/FTkG/esI2XQIFx3df7vqpLf/myW3RtjOPd4yQZW3lW5LNZz4XZOuqunzG MeIX6e+6zFH/JiG/WR/xmeES/gEhTSx9gcOYykbWUDVZZGOp8R6TpsMZFSeLHama 6qNHtS7sYJfupZlyNUHQFvJiQiSe2rIOLIa3MQITuWCvh5vxoNQvGlElpumVIN7+ 817hmLIf5bQsQfOWTM6RwEuqnSA++2DKwOhkA0E+9sWT+ChZJ8AyVQhW0Jq5NrnW 34w17sJZFgXHdYkaDmwQb0TWlITJ3D0CKOpiCWEjo24Z5gAyP/pn/QTNAQQ8iVGD O35y4qDzQnPX6KSaalQMa/HystgqjuKITPmVmfzerxgCFpmjGgwQeIjKKqkrfv4h 7ZeZ8r8TsBLz8+aOPeJro6/cDrf3Z04f/a9s4czesat6F0kfQqi+PDGaH1r+4+XI 5kgARnLt/C5OSbEE+1sw =N6bJ -----END PGP SIGNATURE----- --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932292AbaEGJOp (ORCPT ); Wed, 7 May 2014 05:14:45 -0400 Received: from arroyo.ext.ti.com ([192.94.94.40]:51318 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932246AbaEGJOn (ORCPT ); Wed, 7 May 2014 05:14:43 -0400 Message-ID: <5369F973.10803@ti.com> Date: Wed, 7 May 2014 12:14:27 +0300 From: Tomi Valkeinen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Peter Griffin , Arnd Bergmann , Tony Lindgren CC: , , Jean-Christophe Plagniol-Villard , , Subject: Re: [PATCH 13/13] video: omap: allow building on !MMU References: <1398342509-10243-1-git-send-email-peter.griffin@linaro.org> <1398342509-10243-14-git-send-email-peter.griffin@linaro.org> In-Reply-To: <1398342509-10243-14-git-send-email-peter.griffin@linaro.org> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 24/04/14 15:28, Peter Griffin wrote: > From: Arnd Bergmann >=20 > 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. >=20 > It does seem equivalent to ioremap_wc though, so we should > be able to just use that instead. >=20 > 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? Tomi --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJTaflzAAoJEPo9qoy8lh71mwEP/ixwXorGiw6rNjAy3+rQ/Ht3 d1rWch/w3Xtu+eSjKLKRDBcIKdo0FjU839RrPvFXd48ooo256tJn1hR/DKiysX2T 52uCv/FBJRHHdVvc7ujtwcKSzxL8y/xa9YYL7N3jFlGxbLUqWOJqKiji5fAR408H PV55iIV8sANH2RoWY5u8JL+UebSkj8GMsapRnf4+Pl30/H+oGRExD+xHEcT5e07/ 6F3P6b/FTkG/esI2XQIFx3df7vqpLf/myW3RtjOPd4yQZW3lW5LNZz4XZOuqunzG MeIX6e+6zFH/JiG/WR/xmeES/gEhTSx9gcOYykbWUDVZZGOp8R6TpsMZFSeLHama 6qNHtS7sYJfupZlyNUHQFvJiQiSe2rIOLIa3MQITuWCvh5vxoNQvGlElpumVIN7+ 817hmLIf5bQsQfOWTM6RwEuqnSA++2DKwOhkA0E+9sWT+ChZJ8AyVQhW0Jq5NrnW 34w17sJZFgXHdYkaDmwQb0TWlITJ3D0CKOpiCWEjo24Z5gAyP/pn/QTNAQQ8iVGD O35y4qDzQnPX6KSaalQMa/HystgqjuKITPmVmfzerxgCFpmjGgwQeIjKKqkrfv4h 7ZeZ8r8TsBLz8+aOPeJro6/cDrf3Z04f/a9s4czesat6F0kfQqi+PDGaH1r+4+XI 5kgARnLt/C5OSbEE+1sw =N6bJ -----END PGP SIGNATURE----- --dEWaKqBDIhpEP6uWPfrVghDeIlpxe7XL0--