Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423257AbXBUXXB (ORCPT ); Wed, 21 Feb 2007 18:23:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423258AbXBUXXA (ORCPT ); Wed, 21 Feb 2007 18:23:00 -0500 Received: from ug-out-1314.google.com ([66.249.92.169]:6639 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423257AbXBUXW7 (ORCPT ); Wed, 21 Feb 2007 18:22:59 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OsMR2OPoinrvLFMXREBJYMhYT63fTJp/0AcbRfoPKPQWnuBG6CA4bLedbVAPIKWtiHwBgJdpTmW4vyzRi8nr3HuuFq6L8GjHFPmVJclfhpHjctWmMqPfel+2k//17B6SZzQkfrhm4NOUywFgpkS6v3S/3p8jJHcnNeN0rvdPl+I= Message-ID: <45a44e480702211522q6225d4fbx3f7d99fcef5fe93c@mail.gmail.com> Date: Wed, 21 Feb 2007 18:22:58 -0500 From: "Jaya Kumar" To: "James Simmons" Subject: Re: [PATCH 2.6.20 1/1] fbdev,mm: hecuba/E-Ink fbdev driver Cc: "Geert Uytterhoeven" , "Paul Mundt" , "Peter Zijlstra" , "Linux Frame Buffer Device Development" , "Linux Kernel Development" , linux-mm@kvack.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070217104215.GB25512@localhost> <1171715652.5186.7.camel@lappy> <45a44e480702170525n9a15fafpb370cb93f1c1fcba@mail.gmail.com> <20070217135922.GA15373@linux-sh.org> <45a44e480702180331t7e76c396j1a9861f689d4186b@mail.gmail.com> <20070218235741.GA22298@linux-sh.org> <45a44e480702192013s7d49d05ai31e576f0448a485e@mail.gmail.com> <45a44e480702210855t344441c1xf8e081c82ece4e63@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1088 Lines: 25 On 2/21/07, James Simmons wrote: > > Could you make it work without the framebuffer. There are embedded LCD > displays that have internal memory that need data flushed to them. > I'm not sure I understand. What the current implementation does is to use host based framebuffer memory. Apps mmap that memory and draw to that. Then after the delay, that framebuffer is written to the device's memory. That's the scenario for hecubafb where the Apollo controller maintains it's own internal framebuffer. When you say without the framebuffer, if you meant without the host memory, then this method doesn't work. If you mean without the device's internal memory, then yes, I think we can do that, because it would be up to the driver to use the touched pagelist to then perform IO as suitable for its device. Thanks, jaya - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/