From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ali Gholami Rudi Subject: Re: [PATCH 0/2] fbdev: add fillrect and copyarea ioctls Date: Mon, 13 Jul 2009 20:55:59 +0430 Message-ID: <20090713162559.GA1279@lilem.mirepesht> References: <20090713151709.GA1297@lilem.mirepesht> <20090713084058.547e88f0@infradead.org> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20090713084058.547e88f0@infradead.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Arjan van de Ven Cc: fbdev , Andrew Morton , Andrea Righi , Krzysztof Helt , Greg Kroah-Hartman , Geert Uytterhoeven , Philippe De Muyter , linux-kernel@vger.kernel.org Arjan van de Ven wrote: > On Mon, 13 Jul 2009 19:47:09 +0430 > Ali Gholami Rudi wrote: > > Is there any reason for not adding these ioctls to fbdev? I searched > > the net and couldn't any. Anyway, these patches simply implement > > those ioctls. > > > > can we turn this around, is there a reason to add them? > or in other words, how / where would these be used ? User-space programs that use framebuffer directly can use them. I was writing a simple framebuffer virtual terminal (using libfreetype for fonts; like fbterm); scrolling and painting boxes would be faster if there was someway of using hardware accelerated operations. I think other similar programs can benefit, too. Ali