From: Ivan Gyurdiev <ivg2@cornell.edu>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Nvidia framebuffer in 2.5
Date: Tue, 1 Oct 2002 22:11:59 -0400 [thread overview]
Message-ID: <200210012211.59573.ivg2@cornell.edu> (raw)
This stopped working many kernels ago, and I thought perhaps it's being
converted to a different API... but it hasn't been fixed yet..is it a bug?
This is 2.5.40.
=========================================
make[3]: Entering directory `/usr/src/linux-2.5.40/drivers/video/riva'
gcc -Wp,-MD,./.fbdev.o.d -D__KERNEL__ -I/usr/src/linux-2.5.40/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=athlon -I/usr/src/linux-2.5.40/arch/i386/mach-generic -nostdinc
-iwithprefix include -DKBUILD_BASENAME=fbdev -c -o fbdev.o fbdev.c
drivers/video/riva/fbdev.c: In function `riva_set_dispsw':
drivers/video/riva/fbdev.c:665: structure has no member named `type'
drivers/video/riva/fbdev.c:666: structure has no member named `type_aux'
drivers/video/riva/fbdev.c:667: structure has no member named `ypanstep'
drivers/video/riva/fbdev.c:668: structure has no member named `ywrapstep'
drivers/video/riva/fbdev.c:657: warning: unused variable `accel'
drivers/video/riva/fbdev.c: In function `rivafb_setcolreg':
drivers/video/riva/fbdev.c:1202: warning: unused variable `chip'
drivers/video/riva/fbdev.c: In function `rivafb_get_fix':
drivers/video/riva/fbdev.c:1294: structure has no member named `type'
drivers/video/riva/fbdev.c:1295: structure has no member named `type_aux'
drivers/video/riva/fbdev.c:1296: structure has no member named `visual'
drivers/video/riva/fbdev.c:1302: structure has no member named `line_length'
drivers/video/riva/fbdev.c: In function `rivafb_pan_display':
drivers/video/riva/fbdev.c:1611: structure has no member named `line_length'
drivers/video/riva/fbdev.c: At top level:
drivers/video/riva/fbdev.c:1748: unknown field `fb_get_fix' specified in
initializer
drivers/video/riva/fbdev.c:1748: warning: initialization from incompatible
pointer type
drivers/video/riva/fbdev.c:1749: unknown field `fb_get_var' specified in
initializer
drivers/video/riva/fbdev.c:1749: warning: initialization from incompatible
pointer type
drivers/video/riva/fbdev.c:732: warning: `riva_wclut' defined but not used
gcc -Wp,-MD,./.riva_hw.o.d -D__KERNEL__ -I/usr/src/linux-2.5.40/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=athlon -I/usr/src/linux-2.5.40/arch/i386/mach-generic -nostdinc
-iwithprefix include -DKBUILD_BASENAME=riva_hw -c -o riva_hw.o riva_hw.c
gcc -Wp,-MD,./.accel.o.d -D__KERNEL__ -I/usr/src/linux-2.5.40/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=athlon -I/usr/src/linux-2.5.40/arch/i386/mach-generic -nostdinc
-iwithprefix include -DKBUILD_BASENAME=accel -c -o accel.o accel.c
drivers/video/riva/accel.c: In function `fbcon_reverse_order':
drivers/video/riva/accel.c:111: warning: operation on `a' may be undefined
drivers/video/riva/accel.c: At top level:
drivers/video/riva/accel.c:56: warning: `fbcon_riva_bmove' defined but not
used
drivers/video/riva/accel.c:74: warning: `riva_clear_margins' defined but not
used
drivers/video/riva/accel.c:119: warning: `fbcon_riva_writechr' defined but not
used
ld -m elf_i386 -r -o rivafb.o fbdev.o riva_hw.o accel.o
ld: cannot open fbdev.o: No such file or directory
make[3]: *** [rivafb.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.5.40/drivers/video/riva'
make[2]: *** [riva] Error 2
make[2]: Leaving directory `/usr/src/linux-2.5.40/drivers/video'
make[1]: *** [video] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.40/drivers'
make: *** [drivers] Error 2
next reply other threads:[~2002-10-02 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 2:11 Ivan Gyurdiev [this message]
2002-10-02 8:05 ` Chris Wedgwood
2002-10-02 14:34 ` Ducrot Bruno
2002-10-02 16:58 ` Chris Wedgwood
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=200210012211.59573.ivg2@cornell.edu \
--to=ivg2@cornell.edu \
--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
all inboxes | Powered by JetHome®