* 2.5.3-pre1 compile error
@ 2002-01-16 0:05 John Weber
0 siblings, 0 replies; 4+ messages in thread
From: John Weber @ 2002-01-16 0:05 UTC (permalink / raw)
To: linux-kernel
gcc -D__KERNEL__ -I/usr/src/linux-2.5.2/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o read_write.o read_write.c
In file included from read_write.c:10:
/usr/src/linux-2.5.2/include/linux/file.h:25: parse error before `atomic_t'
/usr/src/linux-2.5.2/include/linux/file.h:25: warning: no semicolon at
end of struct or union
/usr/src/linux-2.5.2/include/linux/file.h:36: parse error before `}'
/usr/src/linux-2.5.2/include/linux/file.h: In function `fcheck_files':
/usr/src/linux-2.5.2/include/linux/file.h:50: dereferencing pointer to
incomplete type
/usr/src/linux-2.5.2/include/linux/file.h:51: dereferencing pointer to
incomplete type
In file included from read_write.c:13:
/usr/src/linux-2.5.2/include/linux/dnotify.h: At top level:
/usr/src/linux-2.5.2/include/linux/dnotify.h:18: warning: `struct inode'
declared inside parameter list
/usr/src/linux-2.5.2/include/linux/dnotify.h:18: warning: its scope is
only this definition or declaration, which is probably not what you want.
/usr/src/linux-2.5.2/include/linux/dnotify.h:21: warning: `struct inode'
declared inside parameter list
/usr/src/linux-2.5.2/include/linux/dnotify.h: In function
`inode_dir_notify':
/usr/src/linux-2.5.2/include/linux/dnotify.h:23: dereferencing pointer
to incomplete type
/usr/src/linux-2.5.2/include/linux/dnotify.h:24: warning: passing arg 1
of `__inode_dir_notify' from incompatible pointer type
read_write.c: In function `sys_read':
read_write.c:167: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
read_write.c: In function `sys_write':
read_write.c:194: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
read_write.c: In function `do_readv_writev':
read_write.c:299: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
read_write.c: In function `sys_pread':
read_write.c:371: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
read_write.c: In function `sys_pwrite':
read_write.c:403: warning: passing arg 1 of `inode_dir_notify' from
incompatible pointer type
make[2]: *** [read_write.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.5.2/fs'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.2/fs'
make: *** [_dir_fs] Error 2
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 2.5.3-pre1 compile error
@ 2002-01-16 1:30 Dave Jones
2002-01-16 1:57 ` Alan Cox
0 siblings, 1 reply; 4+ messages in thread
From: Dave Jones @ 2002-01-16 1:30 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel
Another weirdo. Where did this come from ??
(davej@noodles:linux-2.5.3-pre1)$ rgrep isa_bus_to_virt * | wc -l
1
diff -u --recursive --new-file v2.5.2/linux/drivers/video/vesafb.c linux/drivers/video/vesafb.c
--- v2.5.2/linux/drivers/video/vesafb.c Mon Jan 14 18:25:10 2002
+++ linux/drivers/video/vesafb.c Tue Jan 15 10:56:35 2002
@@ -550,7 +550,7 @@
ypan = pmi_setpal = 0; /* not available or some DOS TSR ... */
if (ypan || pmi_setpal) {
- pmi_base = (unsigned short*)bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
+ pmi_base = (unsigned short*)isa_bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
pmi_start = (void*)((char*)pmi_base + pmi_base[1]);
pmi_pal = (void*)((char*)pmi_base + pmi_base[2]);
printk(KERN_INFO "vesafb: pmi: set display start = %p, set palette = %p\n",pmi_start,pmi_pal);
--
Dave Jones. http://www.codemonkey.org.uk
SuSE Labs.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 2.5.3-pre1 compile error
2002-01-16 1:30 2.5.3-pre1 compile error Dave Jones
@ 2002-01-16 1:57 ` Alan Cox
2002-01-16 2:43 ` David S. Miller
0 siblings, 1 reply; 4+ messages in thread
From: Alan Cox @ 2002-01-16 1:57 UTC (permalink / raw)
To: Dave Jones; +Cc: Linus Torvalds, Linux Kernel
> Another weirdo. Where did this come from ??
This looks dubious but with the right results.
> - pmi_base = (unsigned short*)bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
> + pmi_base = (unsigned short*)isa_bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
The address passed back from the BIOS is a physical address. Not a bus
address, not an ISA address. phys_to_virt I suspect is genuinely the right
thing in this unusual case.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 2.5.3-pre1 compile error
2002-01-16 1:57 ` Alan Cox
@ 2002-01-16 2:43 ` David S. Miller
0 siblings, 0 replies; 4+ messages in thread
From: David S. Miller @ 2002-01-16 2:43 UTC (permalink / raw)
To: alan; +Cc: davej, torvalds, linux-kernel
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Wed, 16 Jan 2002 01:57:30 +0000 (GMT)
This looks dubious but with the right results.
> - pmi_base = (unsigned short*)bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
> + pmi_base = (unsigned short*)isa_bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
The address passed back from the BIOS is a physical address. Not a bus
address, not an ISA address. phys_to_virt I suspect is genuinely the right
thing in this unusual case.
This slipped thru by accident, it is part of the "kill bus_to_virt"
stuff I'm working on with Jens. Oops...
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-01-16 2:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-16 1:30 2.5.3-pre1 compile error Dave Jones
2002-01-16 1:57 ` Alan Cox
2002-01-16 2:43 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-01-16 0:05 John Weber
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox