From: ilya@theIlya.com
To: linux-mips@linux-mips.org
Subject: Another small compile fix
Date: Sun, 1 Jun 2003 12:31:55 -0700 [thread overview]
Message-ID: <20030601193154.GC3035@gateway.total-knowledge.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
I wonder if they ever compile FB drivers with arches where BITS_PER_LONG !=32...
Index: include/linux/fb.h
===================================================================
RCS file: /home/cvs/linux/include/linux/fb.h,v
retrieving revision 1.30
diff -u -r1.30 fb.h
--- include/linux/fb.h 1 Jun 2003 12:07:45 -0000 1.30
+++ include/linux/fb.h 1 Jun 2003 19:28:32 -0000
@@ -432,9 +432,11 @@
#define fb_readb(addr) (*(volatile u8 *) (addr))
#define fb_readw(addr) (*(volatile u16 *) (addr))
#define fb_readl(addr) (*(volatile u32 *) (addr))
+#define fb_readq(addr) (*(volatile u64 *) (addr))
#define fb_writeb(b,addr) (*(volatile u8 *) (addr) = (b))
#define fb_writew(b,addr) (*(volatile u16 *) (addr) = (b))
#define fb_writel(b,addr) (*(volatile u32 *) (addr) = (b))
+#define fb_writeq(b,addr) (*(volatile u64 *) (addr) = (b))
#define fb_memset memset
#endif
Index: drivers/video/cfbcopyarea.c
===================================================================
RCS file: /home/cvs/linux/drivers/video/cfbcopyarea.c,v
retrieving revision 1.4
diff -u -r1.4 cfbcopyarea.c
--- drivers/video/cfbcopyarea.c 1 Jun 2003 12:07:43 -0000 1.4
+++ drivers/video/cfbcopyarea.c 1 Jun 2003 19:30:55 -0000
@@ -38,7 +38,7 @@
#define BYTES_PER_LONG 4
#else
#define FB_WRITEL fb_writeq
-#define FB_READL fb_readq(x)
+#define FB_READL fb_readq
#define SHIFT_PER_LONG 6
#define BYTES_PER_LONG 8
#endif
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-06-01 19:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030601193154.GC3035@gateway.total-knowledge.com \
--to=ilya@theilya.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.