From: Alexander Kern <alex.kern@gmx.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: adaplas@pol.net, "Arnaud FONTAINE" <arnaud.fontaine@free.fr>,
"Daniël Mantione" <daniel@deadlock.et.tudelft.nl>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"James Simmons" <jsimmons@infradead.org>,
"Nicolas Souchu" <nsouch@free.fr>,
"Ville Syrjälä" <syrjala@sci.fi>
Subject: Re: latest patch for atyfb, even more patches
Date: Sat, 16 Oct 2004 23:47:59 +0200 [thread overview]
Message-ID: <200410162347.59630.alex.kern@gmx.de> (raw)
In-Reply-To: <200410152125.55255.alex.kern@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]
Am Freitag, 15. Oktober 2004 21:25 schrieb Alexander Kern:
> Am Dienstag, 12. Oktober 2004 14:42 schrieb Antonino A. Daplas:
> > BTW, can you send me a changelog?
> >
> > Tony
>
> Alphabetical sort, please if I forgot something, add you comment.
>
> Alex Kern
> [PATCH] port Daniel Mantione 2.4 driver to 2.6
> [PATCH] add more pci_id number
> [PATCH] add accelerated imgblit
> [PATCH] revert SDRAM_MAGIC_PLL to old behaviour
> [PATCH] do a "from BIOS" initialisation only by __i386__
>
> Arnaud FONTAINE
> [PATCH atyfb] correction for 3D Rage Mobility L
>
> Geert Uytterhoeven
> [PATCH atyfb] Atari Atyfb fixes
> [PATCH atyfb] Atyfb on Mach64 GX or Atari
> [PATCH 468] m68k sparse floating point
>
> James Simmons
> [PATCH add] port to framebuffer_alloc api
>
> Nicolas Souchu
> [PATCH] I do not found a copy, but it was incorporated too
>
> Ville Syrjälä
> [PATCH] fix pan with doublescan
> [PATCH] another double scan fix
> [PATCH] disable linear aperture register access
> [PATCH] Memory type correction
> [PATCH] atyfb (2.6): Fix mmio_start
> [PATCH] atyfb (2.6): Fix mem_refresh_rate for Mobility
> [PATCH] atyfb (2.6): Add RGB565 support
> [PATCH] atyfb: Blank LCD by turning off backlight voltage
> [PATCH] atyfb: Rage LT LCD register access
> [PATCH] atyfb: vblank irq support
> [PATCH] atyfb: MTRR support
>
Hi, here is more patches to go
Our cursor API is a bit understandable, 80 % of drivers given up, and using
soft_cursor (see a comment in ffb.c#61).
Three drivers made an error and use cursor->enable insted of
info->cursor.enable.
[PATCH atyfb] fix hw cursor breakage
[PATCH g364fb] fix hw cursor breakage
[PATCH imsttfb] fix hw cursor breakage
And tdfxfb is in my mind, broken as a hell.
cut from tdfxfb_cursor function
#ifdef TDFX_HARDWARE_CURSOR
static int tdfxfb_cursor(struct fb_info *info, struct fb_cursor *cursor)
{
......
if (info->cursor.enable) { < Hey it's right
......
/* Turn the cursor on */
cursor->enable = 1;
info->cursor = *cursor; < Outch!
}
#endif
Regards Alex
[-- Attachment #2: cursor-atyfb.patch --]
[-- Type: text/x-diff, Size: 426 bytes --]
--- linux-2.6.8/drivers/video/aty/mach64_cursor.c 2004-10-15 22:25:16.000000000 +0200
+++ linux-2.6.head/drivers/video/aty/mach64_cursor.c 2004-10-16 22:57:34.434688080 +0200
@@ -198,7 +198,7 @@ int atyfb_cursor(struct fb_info *info, s
}
}
- if (cursor->enable) {
+ if (info->cursor.enable) {
wait_for_fifo(1, par);
aty_st_le32(GEN_TEST_CNTL, aty_ld_le32(GEN_TEST_CNTL, par)
| HWCURSOR_ENABLE, par);
[-- Attachment #3: cursor-g364fb.patch --]
[-- Type: text/x-diff, Size: 416 bytes --]
--- linux-2.6.8/drivers/video/g364fb.c 2004-10-15 22:19:15.000000000 +0200
+++ linux-2.6.head/drivers/video/g364fb.c 2004-10-16 23:11:33.687102320 +0200
@@ -128,7 +128,7 @@ static struct fb_ops g364fb_ops = {
int g364fb_cursor(struct fb_info *info, struct fb_cursor *cursor)
{
- switch (cursor->enable) {
+ switch (info->cursor.enable) {
case CM_ERASE:
*(unsigned int *) CTLA_REG |= CURS_TOGGLE;
break;
[-- Attachment #4: cursor-imsttfb.patch --]
[-- Type: text/x-diff, Size: 374 bytes --]
--- linux-2.6.8/drivers/video/imsttfb.c 2004-10-15 22:21:24.000000000 +0200
+++ linux-2.6.head/drivers/video/imsttfb.c 2004-10-16 23:12:28.787725752 +0200
@@ -1249,7 +1249,7 @@ imsttfb_cursor(struct fb_info *info, str
imsttfb_load_cursor_image(par, xx, yy, fgc);
}
- if (cursor->enable)
+ if (info->cursor.enable)
imstt_set_cursor(info, cursor, 1);
return 0;
}
next prev parent reply other threads:[~2004-10-16 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 22:24 latest patch for atyfb Alexander Kern
[not found] ` <200410122042.53878.adaplas@hotpop.com>
2004-10-15 19:25 ` Alexander Kern
2004-10-16 21:47 ` Alexander Kern [this message]
2004-10-16 22:20 ` latest patch for atyfb, even more patches Antonino A. Daplas
2004-10-16 0:15 ` latest patch for atyfb Ville Syrjälä
2004-10-16 17:53 ` Alexander Kern
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=200410162347.59630.alex.kern@gmx.de \
--to=alex.kern@gmx.de \
--cc=adaplas@pol.net \
--cc=arnaud.fontaine@free.fr \
--cc=daniel@deadlock.et.tudelft.nl \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=nsouch@free.fr \
--cc=syrjala@sci.fi \
/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).