From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antonino Daplas Subject: Re: Framebuffer with banked memory Date: 31 Oct 2002 19:04:32 +0800 Sender: linux-fbdev-devel-admin@lists.sourceforge.net Message-ID: <1036062186.638.23.camel@daplas> References: <20021031040228.12091.qmail@web14205.mail.yahoo.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Received: from [203.167.79.9] (helo=willow.compass.com.ph) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 187DAz-0007HQ-00 for ; Thu, 31 Oct 2002 03:07:49 -0800 In-Reply-To: <20021031040228.12091.qmail@web14205.mail.yahoo.com> Errors-To: linux-fbdev-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: alain volmat Cc: fbdev On Thu, 2002-10-31 at 12:02, alain volmat wrote: > > What about adding fb_write / fb_read function in the > framebuffer (device dependant) driver. The same way as > for fb_mmap. I saw that at the beginning of fb_mmap in > fbmem.c, there is a test to see if the device driver > contains its own fb_mmap function, if so the device > driver fb_mmap will be used instead of the "generic" > fb_mmap. What about doing the same thing for fb_write > / fb_read. > I've seen a post by James sometimes ago about adding fb_write and fb_read to info->fbops. Tony ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en