public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: eyal@eyal.emu.id.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-pre5: neofb.c compile failure
Date: Sat, 30 Mar 2002 02:47:42 -0500	[thread overview]
Message-ID: <20020330024742.A9076@rushmore> (raw)

> neofb.c:644: `FB_ACCEL_NEOMAGIC_NM2070' undeclared (first use in this
> function)

This is a diff based on 2.5.7 for include/linux/fb.h.
Console scrolling is 40% faster with neofb on a Toshiba
Tecra 8000 compared to vesafb. :)

My lilo.conf append for 2.4.19-pre5:
append = "video:neofb:ywrap,depth:8"
I.E. replace "vesa" with "neofb"


--- fb.h.orig	Fri Mar 29 21:34:57 2002
+++ fb.h	Fri Mar 29 21:36:40 2002
@@ -95,6 +95,18 @@
 #define FB_ACCEL_SIS_GLAMOUR    36	/* SiS 300/630/540              */
 #define FB_ACCEL_3DLABS_PERMEDIA3 37	/* 3Dlabs Permedia 3		*/
 
+
+#define FB_ACCEL_NEOMAGIC_NM2070 90	/* NeoMagic NM2070              */
+#define FB_ACCEL_NEOMAGIC_NM2090 91	/* NeoMagic NM2090              */
+#define FB_ACCEL_NEOMAGIC_NM2093 92	/* NeoMagic NM2093              */
+#define FB_ACCEL_NEOMAGIC_NM2097 93	/* NeoMagic NM2097              */
+#define FB_ACCEL_NEOMAGIC_NM2160 94	/* NeoMagic NM2160              */
+#define FB_ACCEL_NEOMAGIC_NM2200 95	/* NeoMagic NM2200              */
+#define FB_ACCEL_NEOMAGIC_NM2230 96	/* NeoMagic NM2230              */
+#define FB_ACCEL_NEOMAGIC_NM2360 97	/* NeoMagic NM2360              */
+#define FB_ACCEL_NEOMAGIC_NM2380 98	/* NeoMagic NM2380              */
+
+
 struct fb_fix_screeninfo {
 	char id[16];			/* identification string eg "TT Builtin" */
 	unsigned long smem_start;	/* Start of frame buffer mem */




             reply	other threads:[~2002-03-30  7:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-30  7:47 rwhron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-29 21:47 Linux 2.4.19-pre5 Marcelo Tosatti
2002-03-30  0:23 ` Linux 2.4.19-pre5: neofb.c compile failure Eyal Lebedinsky

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=20020330024742.A9076@rushmore \
    --to=rwhron@earthlink.net \
    --cc=eyal@eyal.emu.id.au \
    --cc=linux-kernel@vger.kernel.org \
    /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