linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: cfb_fillrect and friends undefined
Date: Thu, 03 Aug 2006 14:20:21 +0800	[thread overview]
Message-ID: <44D195A5.8050605@gmail.com> (raw)
In-Reply-To: <170385E48B041543AC99CCD09E325AD1AC54B4@mail.elevenonline.com.au>

Richard Wolf wrote:
> Hi,
> 
> I'm trying to write a frame buffer driver, basing it on the vfb virtual
> driver.  When I try to load the module I get an error message:
> 
> lh155ba: Unknown symbol platform_driver_unregister
> lh155ba: Unknown symbol cfb_copyarea
> lh155ba: Unknown symbol platform_device_register
> lh155ba: Unknown symbol platform_driver_register
> lh155ba: Unknown symbol platform_device_unregister
> lh155ba: Unknown symbol cfb_imageblit
> lh155ba: Unknown symbol cfb_fillrect
> 
> I can't work out what config options to enable to define these symbols.  I
> can get cfb_* to appear by selecting the vfb driver, but I don't want that
> driver, just the cfb_* functions.  Any help?

Add:

select FB_CFB_IMAGEBLIT
select FB_CFB_COPYAREA
select FB_CFB_FILLRECT

in drivers/video/Kconfig (under your driver, of course).

As for the platform_*, add #include <linux/platform_device.h>

Tony

-------------------------------------------------------------------------
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

      reply	other threads:[~2006-08-03  6:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  2:39 cfb_fillrect and friends undefined Richard Wolf
2006-08-03  6:20 ` Antonino A. Daplas [this message]

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=44D195A5.8050605@gmail.com \
    --to=adaplas@gmail.com \
    --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).