From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934475Ab1IOTGH (ORCPT ); Thu, 15 Sep 2011 15:06:07 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:51687 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S934183Ab1IOTGF (ORCPT ); Thu, 15 Sep 2011 15:06:05 -0400 Date: Thu, 15 Sep 2011 20:05:14 +0100 From: Alan Cox To: Florian Tobias Schandinat Cc: Keith Packard , Tomi Valkeinen , linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linaro-dev@lists.linaro.org, "Clark\, Rob" , Archit Taneja Subject: Re: Proposal for a low-level Linux display framework Message-ID: <20110915200514.74bdcd90@lxorguk.ukuu.org.uk> In-Reply-To: <4E723A20.2040002@gmx.de> References: <1316088425.11294.78.camel@lappyti> <1316100594.23214.65.camel@deskari> <4E72320B.6020000@gmx.de> <20110915181802.69ef0d56@lxorguk.ukuu.org.uk> <4E723A20.2040002@gmx.de> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > What is your problem with discontigous framebuffers? (I assume discontigous > refers to the pages the framebuffer is composed of) > Sounds to me like you should implement your own fb_mmap and either map it > contigous to screen_base or implement your own fb_read/write. > In theory you could even have each pixel at a completely different memory > location although some userspace wouldn't be happy when it could no longer mmap > the framebuffer. The mmap side is trivial, the problem is that the fb layer default implementations of blits, fills etc only work on a kernel linear frame buffer. And (for example) there is not enough linear stolen memory on some Intel video for a 1080p console on HDMI even though the hardware is perfectly capable of using an HDTV as its monitor. Nor - on a 32bit box- is there enough space to vremap it. Alan