From: Dirk Behme <dirk.behme@de.bosch.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: jsimmons@infradead.org, geert@linux-m68k.org
Subject: 2.6.1 fb.h patch for userland application
Date: Mon, 09 Feb 2004 11:44:43 +0100 [thread overview]
Message-ID: <4027649B.5010208@de.bosch.com> (raw)
Hello,
I had problems to use linux/fb.h from 2.6.1 to compile userland
application microwindows. I made some changes to get microwindows 0.90
to compile, please see patch below.
The include files atomic.h and spinlock.h are necessary for spinlock_t
and atomic_t. workqueue.h doesn't compile for userspace application and
doesn't seem to be necessary at all (?). u8 is undefined while compiling
for userspace, use __u8 instead.
Is this patch OK?
Dirk
--- linux/include/linux/fb.h_orig 2003-12-30 19:58:12.000000000 +0100
+++ linux/include/linux/fb.h 2004-02-04 10:11:59.000000000 +0100
@@ -2,8 +2,9 @@
#define _LINUX_FB_H
#include <linux/tty.h>
-#include <linux/workqueue.h>
+#include <linux/spinlock.h>
#include <asm/types.h>
+#include <asm/atomic.h>
#include <asm/io.h>
/* Definitions of frame buffers
*/
@@ -339,8 +340,8 @@ struct fb_pixmap {
__u32 scan_align; /* alignment per scanline
*/
__u32 flags; /* see FB_PIXMAP_*
*/
/* access methods
*/
- void (*outbuf)(u8 *dst, u8 *addr, unsigned int size);
- u8 (*inbuf) (u8 *addr);
+ void (*outbuf)(__u8 *dst, __u8 *addr, __u32 size);
+ __u8 (*inbuf) (__u8 *addr);
spinlock_t lock; /* spinlock
*/
atomic_t count;
};
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next reply other threads:[~2004-02-09 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 10:44 Dirk Behme [this message]
2004-02-09 12:33 ` 2.6.1 fb.h patch for userland application Geert Uytterhoeven
2004-02-09 17:21 ` James Simmons
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=4027649B.5010208@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).