From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH 27/41] fbdev: Advertise limitation of drawing engine
Date: Thu, 26 Apr 2007 15:17:05 +0800 [thread overview]
Message-ID: <1177571825.4685.18.camel@daplas> (raw)
In-Reply-To: <Pine.LNX.4.64.0704260836150.9880@anakin>
On Thu, 2007-04-26 at 08:38 +0200, Geert Uytterhoeven wrote:
> On Thu, 26 Apr 2007, Antonino A. Daplas wrote:
> > On Wed, 2007-04-25 at 23:23 +0200, Ondrej Zajicek wrote:
> > > On Wed, Apr 25, 2007 at 02:56:52PM +0800, Antonino A. Daplas wrote:
> > > > A few drivers are not capable of blitting rectangles of any dimension.
> > > > vga16fb can only blit 8-pixel wide rectangles, while s3fb (in tileblitting
> > > > mode) can only blit 8x16 rectangles.
> > >
> > > I have two new drivers which use tileblit. Where i can get diff of your
> > > tree (not splitted to fifty parts and mixed with mail) to be able to
> >
> > No public tree, and I don't have CVS access to fbdev-devel.
>
> That can be arranged, if you want it... ;-)
Frankly, no, I don't want the additional work of maintaining a public
tree :-). Plus, fbdev is pretty much in a stable state. so merging
patches based on Linus's or akpm's tree is not a problem.
But if people really want a public tree, I won't mind maintaining one.
Tony
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-04-26 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 6:56 [PATCH 27/41] fbdev: Advertise limitation of drawing engine Antonino A. Daplas
2007-04-25 21:23 ` Ondrej Zajicek
2007-04-25 23:10 ` Antonino A. Daplas
2007-04-26 6:38 ` Geert Uytterhoeven
2007-04-26 7:17 ` Antonino A. Daplas [this message]
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=1177571825.4685.18.camel@daplas \
--to=adaplas@gmail.com \
--cc=geert@linux-m68k.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.