All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: James Simmons <jsimmons@www.infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>,
	"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: Mapping the framebuffer into kernel space
Date: Thu, 12 May 2005 13:38:45 -0400	[thread overview]
Message-ID: <9e47339105051210385a41e54e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0505121648020.19137@pentafluge.infradead.org>

On 5/12/05, James Simmons <jsimmons@www.infradead.org> wrote:
> 
> > > > Could you generically rewrite fb_read/write to just use the image blitter?
> > >
> > > Yes.
> >
> > No.
> >
> > The imageblit routines convert between chunked pixels and the actual frame
> > buffer representation.
> > fb_{read,write}() access the raw frame buffer.
> 
> That means that we will never uses the hardware acceleration ever in this
> case :-( It will always be slow!!!!
> 
> > Probably the best solution is to set up a small ioremap()'ed window that can be
> > moved in fb_{read,write}() (assumed moving such a window is much cheaper than
> > ioremap() + iounmap()).
> 
> Does such functionality exist? Second can you do the same thing with
> request_region? We need to so fbcon and /dev/fb don't step on each other
> toes.

Before we get too far into this, has anyone determined if any user
space app exists that does read/write from fbdev? I can't see a real
need to keep this feature if no one is using it. If no one is using
it, it would be much simpler just to remove the functions.

-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id\x16281&op=click

  reply	other threads:[~2005-05-12 17:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29  3:55 Mapping the framebuffer into kernel space Jon Smirl
2005-05-02 17:43 ` James Simmons
     [not found]   ` <9e473391050504104529f1f080@mail.gmail.com>
2005-05-04 18:08     ` James Simmons
     [not found]       ` <9e47339105050416415f4dfb1f@mail.gmail.com>
2005-05-05 16:43         ` James Simmons
     [not found]           ` <9e47339105050511522f6eff30@mail.gmail.com>
2005-05-05 18:59             ` James Simmons
     [not found]               ` <9e473391050505122635f1cf@mail.gmail.com>
2005-05-05 20:43                 ` James Simmons
     [not found]                   ` <9e4733910505051402789440db@mail.gmail.com>
2005-05-05 23:47                     ` James Simmons
     [not found]                       ` <9e473391050505170161b0a38d@mail.gmail.com>
     [not found]                         ` <9e47339105050517083fadaee0@mail.gmail.com>
2005-05-06 19:08                           ` James Simmons
     [not found]                             ` <9e47339105050615097bdfcdcb@mail.gmail.com>
2005-05-11 22:46                               ` James Simmons
2005-05-12  9:14                                 ` Geert Uytterhoeven
2005-05-12 15:50                                   ` James Simmons
2005-05-12 17:38                                     ` Jon Smirl [this message]
2005-05-12 19:59                                       ` Geert Uytterhoeven
2005-05-12 20:12                                         ` Jon Smirl
2005-05-13 20:35                                           ` James Simmons
2005-05-13 20:56                                             ` Jon Smirl
2005-05-06  9:30           ` Geert Uytterhoeven
2005-05-06 19:07             ` James Simmons
2005-05-07  3:08 ` Antonino A. Daplas
     [not found]   ` <9e47339105050620312618d2b7@mail.gmail.com>
2005-05-12  0:38     ` James Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9e47339105051210385a41e54e@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@hotpop.com \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@www.infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.