From: Zack Smith <plinius@comcast.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Optimized cfbimgblt.c
Date: Fri, 28 Jan 2005 21:15:32 -0800 [thread overview]
Message-ID: <41FB1BF4.2070108@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.56.0501282053340.23195@pentafluge.infradead.org>
I'm all for replacing my low level functions with existing
functions, since that will reduce the size of FBUI,
plus if people have already written accelerated routines
it could benefit FBUI greatly.
James Simmons wrote:
>Actually I have taken a look at your code. It's has potential for selling
>to some embedded vendor. Alot of the stuff you add is indeed missing but
>mostly can be implemented with what we already have. For example:
>
>fb_clear is really fb_fillrect with a rop of ROP_CLEAR. This is something
>I know Petr has been asking for :-) Which I want to implement.
>
>fb_vline is a rectangle with a height of 1.
>
>fb_read_point,fb_point, and fb_hline are really
>
>struct fb_pixmap {
> inbuf
> outbuf
>}
>
>We really need a way to get framebuffer data which you did with
>fb_getpixels. I plan to expand fb_imageblit to create a image from
>the framebuffer. I like to see fb_read use this.
>
>Why a copyarea2 ?
>
>
>
>>I just want to make a tangential comment, call it trivia almost,
>>but if we wanted to use my in-kernel GUI -- FBUI -- to handle
>>the graphics during startup, including the penguin image, or
>>even to handle the virtual console terminal itself or the login
>>prompt, then I expect that can be done.
>>
>>Zack Smith
>>home.comcast.net/~plinius/fbui.html
>>
>>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
>Tool for open source databases. Create drag-&-drop reports. Save time
>by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
>Download a FREE copy at http://www.intelliview.com/go/osdn_nl
>_______________________________________________
>Linux-fbdev-devel mailing list
>Linux-fbdev-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
>
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-29 2:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 20:25 Optimized cfbimgblt.c jsimmons
2005-01-25 12:58 ` Antonino A. Daplas
2005-01-26 21:07 ` James Simmons
2005-01-27 20:06 ` Zack Smith
2005-01-28 21:04 ` James Simmons
2005-01-29 5:15 ` Zack Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-19 20:59 James Simmons
2005-01-20 18:08 James Simmons
2005-01-20 22:00 ` Antonino A. Daplas
2005-01-21 0:29 ` James Simmons
2005-01-31 19:25 ` 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=41FB1BF4.2070108@comcast.net \
--to=plinius@comcast.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).