2.5.5 NVidia driver compile fails
I get a whole bunch of warnings, then this:
nv.c: In function `nv_kern_open':
nv.c:1149: invalid operands to binary &
nv.c:1153: invalid operands to binary &nv.c: In function `nv_kern_close':
nv.c:1260: invalid operands to binary &nv.c: In function `nv_kern_mmap':
nv.c:1389: warning: passing arg 1 of `remap_page_range_Reb32c755' makes pointer from integer without a cast
nv.c:1389: incompatible type for argument 4 of remap_page_range_Reb32c755' nv.c:1389: too few arguments to function remap_page_range_Reb32c755' nv.c:1406: warning: passing arg 1 of `remap_page_range_Reb32c755' makes pointer from integer without a cast
nv.c:1406: incompatible type for argument 4 of remap_page_range_Reb32c755' nv.c:1406: too few arguments to function remap_page_range_Reb32c755' nv.c:1438: warning: passing arg 1 of `remap_page_range_Reb32c755' makes pointer from integer without a cast
nv.c:1438: incompatible type for argument 4 of remap_page_range_Reb32c755' nv.c:1438: too few arguments to function remap_page_range_Reb32c755' make[2]: *** [nv.o] Error 1
Has anyone got a working patch for the NVidia tree?
John Hughes
Quoted 3 lines · John Hughes
nv.c:1438: incompatible type for argument 4 of
remap_page_range_Reb32c755' nv.c:1438: too few arguments to functionremap_page_range_Reb32c755' make[2]: *** [nv.o] Error 1
Assuming you get lucky, and manage to fix up all the compile errors in the source you have, chances are that the same interface changes will break the binary only part too. So it'll compile, link, and likely explode as soon as you try to use it.
It's likely that only nvidia can help you here.
Same goes for any other binary only module during a devel series.
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs