linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: David Eger <eger@havoc.gtf.org>, adaplas@pol.net
Cc: Andrew Morton <akpm@osdl.org>,
	jsimmons@pentafluge.infradead.org,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH 3/3][FBDEV]: Set capabilities flag for vesafb and vga16fb
Date: Tue, 6 Jul 2004 18:30:37 +0800	[thread overview]
Message-ID: <200407061830.37554.adaplas@hotpop.com> (raw)
In-Reply-To: <20040706053545.GA2375@havoc.gtf.org>

On Tuesday 06 July 2004 13:35, David Eger wrote:
> Thanks for getting these; I've been lazy and not gotten to them.
>

My intent was to demonstrate the PAN_REDRAW patch, and 
FBINFO_HWACCEL_YPAN must be set for that :-) And I chose
vesafb and vga16fb since they're the most commonly used drivers
in the x86 world.

> I do want FBINFO_FLAG_DEFAULT to go away though... it's now

Hmm, okay, I did not know that.

> FBINFO_DEFAULT.  I also don't see anything in vga16fb that precludes
> FBINFO_HWACCEL_XPAN, though I don't see anyone who uses that flag,
> either.  *shrug*

Well, fbcon does not use x-panning at all, so, yes, it's a useless flag, not
just for vga16fb but for all drivrers.  Userspace uses x-panning though, but 
they check xpanstep instead.

Tony




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

      reply	other threads:[~2004-07-06 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05 22:34 [PATCH 3/3][FBDEV]: Set capabilities flag for vesafb and vga16fb Antonino A. Daplas
2004-07-06  5:35 ` David Eger
2004-07-06 10:30   ` 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=200407061830.37554.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=eger@havoc.gtf.org \
    --cc=jsimmons@pentafluge.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 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).