From: Manuel Lauss <mano@roarinelk.homelinux.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: SM501 framebuffer driver
Date: Mon, 22 Jan 2007 07:55:20 +0000 (UTC) [thread overview]
Message-ID: <loom.20070122T084752-664@post.gmane.org> (raw)
In-Reply-To: 20070115013124.GA19486@home.fluff.org
Hi Ben,
Ben Dooks <ben-fbdev <at> fluff.org> writes:
> This is a resend of the SM501 patch, with all
> the previous comments addressed, and some more
> support for items such as blanking and display
> panning. A number of code paths are now handled
> by common blocks where possible to make the code
> easier to change.
Is there an updates patchset for the MFD part?
(I'm using the one you posted on Dec 13, 2006 to LKML)
I get a few compile errors in this driver, all
referencing missing constants:
sm501fb.c: In function `sm501fb_set_par_common':
sm501fb.c:411: error: `SM501_ADDR_FLIP' undeclared (first use in this function)
sm501fb.c:411: error: (Each undeclared identifier is reported only once
sm501fb.c:411: error: for each function it appears in.)
sm501fb.c: In function `sm501fb_set_par_geometry':
sm501fb.c:462: error: `SM501_OFF_DC_H_TOT' undeclared (first use in this
function)
sm501fb.c:469: error: `SM501_OFF_DC_H_SYNC' undeclared (first use in this
function)
sm501fb.c:476: error: `SM501_OFF_DC_V_TOT' undeclared (first use in this
function)
sm501fb.c:482: error: `SM501_OFF_DC_V_SYNC' undeclared (first use in this
function)
sm501fb.c: In function `sm501fb_pan_crt':
sm501fb.c:523: error: `SM501_DC_CRT_CONTROL_PIXEL_MASK' undeclared (first use in
this function)
sm501fb.c:529: error: `SM501_ADDR_FLIP' undeclared (first use in this function)
(and so on...)
Thanks!
--
Manuel Lauss
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-01-22 8:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 1:31 SM501 framebuffer driver Ben Dooks
2007-01-22 7:55 ` Manuel Lauss [this message]
2007-01-23 10:17 ` Ben Dooks
2007-01-23 15:13 ` Manuel Lauss
-- strict thread matches above, loose matches on Subject: below --
2006-10-06 16:11 Bill Gatliff
2006-10-06 16:26 ` Ben Dooks
2006-10-06 19:19 ` Bill Gatliff
2006-10-10 6:01 ` Andrey Volkov
2006-10-10 12:06 ` Bill Gatliff
2006-10-11 15:17 ` Clemens Koller
2006-10-06 17:25 ` Clemens Koller
2006-10-06 18:04 ` Bill Gatliff
[not found] ` <4526A37F.6040002@anagramm.de>
2006-10-06 19:03 ` Bill Gatliff
2006-10-06 18:14 ` Alex Deucher
2006-10-06 18:55 ` Ville Syrjälä
2006-10-13 12:11 ` Paul Mundt
2006-10-13 13:12 ` Clemens Koller
2006-10-13 13:18 ` Andrey Volkov
2006-10-15 17:34 ` Bill Gatliff
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=loom.20070122T084752-664@post.gmane.org \
--to=mano@roarinelk.homelinux.net \
--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).