All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Gothe <markus.gothe@27m.se>
To: kaka <share.kt@gmail.com>
Cc: directfb-users@directfb.org, directfb-dev@directfb.org,
	linux-mips@linux-mips.org, uclinux-dev@uclinux.org,
	linux-fbdev-users@lists.sourceforge.net
Subject: Re: Updated:Error opening framebuffer device/Unknown symbol
Date: Thu, 25 Oct 2007 17:56:30 +0200	[thread overview]
Message-ID: <4720BCAE.1030209@27m.se> (raw)
In-Reply-To: <eea8a9c90710250155h7534fdfajf7193921575e96fe@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

You cannot use libc-stuff for the kernel, use the kernel equalients...

//Markus

kaka wrote:
> Hi All,
> 
> Thanks for the overhelming responses.
> I was able to remove the problem of Unknown symbols by linking the
> proper libraries. Now the problem got reduced to the following messages.
> 
> # insmod brcmstfb.ko
> brcmstfb: Unknown symbol printf
> brcmstfb: Unknown symbol malloc
> brcmstfb: Unknown symbol free
> insmod: cannot insert `brcmstfb.ko': Unknown symbol in module (2):
> No such file or directory
> #
> 
> for the above problem i had tried to link "libgcc.a " but those
> symbols are also undefined in it also.
> RECAP:
> While running  the cross compiled directFB example on MIPS chip,*
> We tried to install the framebuffer driver(command given
> above) after creating the node fb0.
> APPROACH:
> Actually the code of frambuffer driver consists of usual kernel
> framebuffer code and properitiary graphics lib code.
> The properitiary graphics lib code is using malloc,print and free
> from <stdlib.h> and that is why those symbols are coming undefined.
> 
> Could anybody help in this regard?
> Thanks in advance.
> 
> kaka
> 
>
>
> ---------- Forwarded message ----------
> From: *kaka* < share.kt@gmail.com <mailto:share.kt@gmail.com>>
> Date: Oct 12, 2007 6:33 PM
> Subject: Error opening framebuffer device/Unknown symbol
> register_framebuffer
> To: directfb-users@directfb.org
> <mailto:directfb-users@directfb.org>, directfb-dev@directfb.org
> <mailto:directfb-dev@directfb.org>.
>
> 
>
>     * Hi All, *
>
>     * While running  the cross compiled directFB example on MIPS chip, *
>
>     *
>
>
>
>     We tried to install the framebuffer driver(command given at the
bottom) and we have already created the node fb0. *
>
>     * We are getting the following error,  *
>
>
>
>     * Can anybody help in this regard ? *
>
>     * Thanks in Advance. *
>
>     # ../../cross_directfb/simple_mips
>                                                                                                                                 

>          =======================|  DirectFB 1.0.0  |=======================
>               (c) 2001-2007  The DirectFB Organization (directfb.org
<http://directfb.org/>)
>               (c) 2000-2004  Convergence (integrated media) GmbH
>             ------------------------------------------------------------
>                                                                                                                                 

>     (*) DirectFB/Core: Single Application Core. (2007-10-05 14:17)
>     (!) Direct/Util: opening '/dev/fb0' failed
>         --> No such device or address
>     (!) DirectFB/FBDev: Error opening framebuffer device!
>     (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER
environment variable.
>     (!) DirectFB/Core: Could not initialize 'system' core!
>         --> Initialization error!
>     simple.c <96>:
>             (#) DirectFBError [DirectFBCreate (&dfb)]: Initialization
error!
>     #
>
>     * While running the following command in MIPS chip, we are getting
the following error. *
>
>     # insmod brcmstfb.ko
>     brcmstfb: Unknown symbol unregister_framebuffer
>     brcmstfb: Unknown symbol printf
>     brcmstfb: Unknown symbol malloc
>     brcmstfb: Unknown symbol fb_find_mode
>     brcmstfb: Unknown symbol fb_dealloc_cmap
>     brcmstfb: Unknown symbol fb_alloc_cmap
>     brcmstfb: Unknown symbol framebuffer_release
>     brcmstfb: Unknown symbol free
>     insmod: cannot insert `brcmstfb.ko': Unknown symbol in module (2):
No such file or directory
>     #
>     #
>
>     
>
>
>
>
> --
> Thanks & Regards,
> kaka
>
> --
> Thanks & Regards,
> kaka


- --
_______________________________________

Mr Markus Gothe
Software Engineer

Phone: +46 (0)13 21 81 20 (ext. 1046)
Fax: +46 (0)13 21 21 15
Mobile: +46 (0)73 718 72 80
Diskettgatan 11, SE-583 35 Linköping, Sweden
www.27m.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHILyr6I0XmJx2NrwRCDF2AJ9eZIGLy2mPEiUn6bz4+oX7pclzWACfQBn8
pv3s3/Hpkhhau69I7NZLCJ0=
=0zSq
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2007-10-25 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25  8:55 Updated:Error opening framebuffer device/Unknown symbol kaka
2007-10-25  9:09 ` Manuel Lauss
2007-10-25  9:14 ` [Linux-fbdev-users] " Jan-Benedict Glaw
2007-10-25 14:15 ` Shane McDonald
2007-10-25 15:56 ` Markus Gothe [this message]
2007-10-25 16:03   ` Kevin D. Kissell
2007-10-25 16:03     ` Kevin D. Kissell
2007-10-25 18:25 ` [directfb-users] " gxk

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=4720BCAE.1030209@27m.se \
    --to=markus.gothe@27m.se \
    --cc=directfb-dev@directfb.org \
    --cc=directfb-users@directfb.org \
    --cc=linux-fbdev-users@lists.sourceforge.net \
    --cc=linux-mips@linux-mips.org \
    --cc=share.kt@gmail.com \
    --cc=uclinux-dev@uclinux.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.